Difference between revisions of "Adaptive bandpass filtering"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
| − | + | [[Category: Adaptive bandpass filtering]] | |
| − | + | [[Category: Resolution]] | |
| − | + | [[Category: Multireference alignment]] | |
| + | The "golden standard" methodology is a widespread method to drive the alignment process avoiding overfitting and providing an accepted estimation of the attained [[resolution]]. | ||
| + | |||
| + | It bases on splitting the original data set into two halves that | ||
| + | |||
| + | |||
| + | Operationally, an ABF project is just a multireference project that | ||
| + | * doesn't [[swap particles]] between references, and | ||
| + | * and that adjust the lowpass filter parameters at each iteration. | ||
==Parameters in an ABF project== | ==Parameters in an ABF project== | ||
==Creating an ABF project in dcp== | ==Creating an ABF project in dcp== | ||
| + | In general, you would design a '''single reference''' project. Then you would derive the | ||
==Creating an ABF project in the command line== | ==Creating an ABF project in the command line== | ||
Revision as of 12:55, 14 April 2016
The "golden standard" methodology is a widespread method to drive the alignment process avoiding overfitting and providing an accepted estimation of the attained resolution.
It bases on splitting the original data set into two halves that
Operationally, an ABF project is just a multireference project that
- doesn't swap particles between references, and
- and that adjust the lowpass filter parameters at each iteration.
Parameters in an ABF project
Creating an ABF project in dcp
In general, you would design a single reference project. Then you would derive the
