:: 350um @Instrument: SHARC-2 Specify that the 350um filter was used (default). This adjuts conversion factors, tau scaling relations for calculating in-band line-of sight opacitites, and beam sizes (see 'sharc2/default.cfg'). @See: 'jansky', 'tau.', 'beam'. :: 450um @Instrument: SHARC-2, SCUBA-2 Use if the 450um filter was used to observe with SHARC-2, or to specify 450um imaging with SCUBA-2 @See: '350um' and '850um' :: 850um @Instrument: SHARC-2, SCUBA-2 Specify that data was taken at 850um with SHARC-2, or to reduce the data from the 850um array of SCUBA-2. @See: '350um' and '450um' :: accel @Alias -> 'correlated.accel-mag' @Advanced Can be used to enable acceleration response decorrrelation, or to set options for it. @See: 'correlated.' for available options. :: aclip=X @Advanced Clip data when the telescope acceleration is above X arcsec/s^2. Heavy accelerations can put mechanical energy into the detector system, changing the shape of the primary, thereby generating bright signals from the varying illumination of the bright atmosphere. Clipping data when there is danger of this happening is a good idea. @See: 'accel' for possible modeling of these signals) :: alias. @Advanced Use to define convenient shorthands for yourself. Aliases are literal substitutions. Thus: alias.altaz system=horizontal can specify 'altaz' to serve as a shorthand for the key/value pair 'system=horizontal'. Conditional can also be aliased. E.g.: alias.final iteration.[last] Defines 'final' as a shorthand for 'iteration.[last]'. Thus: final:smooth=9.0 is understood as being iteration.[last] smooth=9.0 (The colon provides an alternative to a white-space to separate the condition from the statement, which is also command-line friendly). @See: 'altaz', 'final' :: altaz @Alias -> 'system=horizontal' Shorthand for reducing in Alt/Az cordinates. @See: 'system' and 'horizontal'. :: amps @Alias -> 'correlated.amps' @Instrument: LABOCA @Advanced Decorrelate on amplifier boards, or set options for it. @See: 'correlated.' for details on brached options. :: analyzer= @Instrument: PolKa @Since: 2.04 Specify that the analyzer grid position that was used for taking the data. Specifying the analyzer is important for recovering the polarization information. The must be either 'H' or 'V' corresponding to the two positions. As of 2011, the analyzer position should be correctly recorded in the data file, and therefore automatically detected. You can still use 'analyzer' to override the recorded setting. :: analyzer.h=X @Instrument: PolKa @Expert @Since: 2.11 Set the H analyzer angle (in degrees). @See: 'analyzer.v' :: analyzer.h.phase=X @Instrument: PolKa @Expert @Since: 2.11 Set the relative phase (degrees) of the total-power modulation for waveplate phase reconstruction with the H analyzer. These phases can be measured using 'waveplate.tpchar' when the waveplate data is normally present. @See: 'waveplate.tpchannel', 'waveplate.tpharmonic' 'waveplate.tpchar', 'analyzer.v.phase' :: analyzer.v=X @Instrument: PolKa @Expert @Since: 2.11 Set the V analyzer angle (in degrees). @See: 'analyzer.h' :: analyzer.v.phase=X @Instrument: PolKa @Expert @Since: 2.11 Set the relative phase (degrees) of the total-power modulation for waveplate phase reconstruction with the V analyzer. These phases can be measured using 'waveplate.tpchar' when the waveplate data is normally present. @See: 'waveplate.tpchannel', 'waveplate.tpharmonic' 'waveplate.tpchar', 'analyzer.h.phase' :: array @Alias -> 'correlated.obs-channels' @Advanced Decorrelate on all the radiation-sensitive channels of the instrument, or set options for it. @See: 'correlated.' for details on brached options. :: azimuth @Alias -> 'correlated.telescope-x' @Instrument: GISMO @Advanced Remove signals, which are correlated to the azymuth movement of the telescope (e.g. superconducting detector arrays sensitive to Earth's magnetic field.), @See: 'correlated.' for details on brached options. :: beam=X @Advanced Set the instrument beam to X arcseconds. @See: 'resolution' :: beammap Effectively the same as 'source.type=beammap', which is invoked by a condition, not an alias because aliasing would interfere with the similarly named 'beammap.process' and 'beammap.writemaps' options. Used for reducing beam map data. Instead of making a single map from all pixels, separate maps are created for each pixel (Note, this can chew up some memory if you have a lot of pixels). At the end of the reduction CRUSH determines the actual pixel offsets in the focal plane. @See: 'source.type', 'map', 'skydip', 'grid' :: beammap.process @Advanced Specify that beam-maps should undergo the same post-processing steps (e.g. smoothing, clipping filtering, etc.) that are used for regular map-making. When the option is not set, beam-maps are used in their raw maximum-likelihood forms. @See: 'beammap', 'beammap.writemaps' :: beammap.writemaps Beam maps normally only produce the pixel position information. Use this option if you want CRUSH to write individual pixel maps as well, so you can peek at these yourself. @See: 'beammap', beammap.process' :: blacklist[=] Similar to 'forget', except it will not set options even if they are then specified at a later time. This is useful for altogether removing settings from the configuration. @Since: 2.01-4 Without an argument, the command will produce the list of all blacklisted settings on the console. @See: 'whitelist', 'forget', 'recall', 'remove', 'replace' :: blank=X @Expert Skip data from modeling over points that have a source flux exceeding the signal-to-noise level X. This may be useful in reducing the filtering effect around bright peaks. @See: 'clip'. :: blind= @Expert Specify a list of blind pixels. Use data indeces (e.g. backend indeces for APEX) and ranges, in a comma- separated form. E.g.: blind 46,70-72,84 Blind channels may be used by some instruments to estimate instrumental signals, such as temperature fluctuations (LABOCA). Channels are normally numbered from 1 (i.e. not C-style!) @See: 'flag'. :: block=NX,NY @Instrument: SHARC-2, SCUBA-2 @Expert Specify a correlated block size for higher order sky-noise removal, as two integer pixel numbers (rows and columns) separated by a comma or 'x'. E.g.: block=4x6 will decorrelate signals on blocks that are 4 columns wide and 6 rows tall (i.e. there will be 16 such blocks on the 32x12 SHARC-2 array). @See: 'blocks' :: blocks @Alias -> correlated.blocks @instrument: SHARC-2, SCUBA-2 @Advanced Decorrelate on rectangular block regions of the array, as a way to remove higher order sky-noise. As such, it can be used together with, or instead of 'gradients'. @See: 'gradients', 'correlated.' :: boxes @Alias -> correlated.boxes @Instrument: LABOCA @Advanced Decorrelate on electronic boxes, or set options for it. @See: 'correlated.', 'cables', 'squids' :: bright Use for bright sources (S/N > ~1000). This setting entirely bypasses all filtering to produce a very faithful map. The drawback is more noise, but that should not be an issue for such a bright guy :-) Will invoke 'bright.cfg'. @See: 'config', 'faint', 'deep' :: cables @Alias -> correlated.cables @Instrument: LABOCA, ASZCA @Advanced Decorrelate channels whose signals are running on the same cables, and which are therefore subject to the same pickups (electromagnetic or microphonic). @See: 'correlated.', 'boxes' :: center @Deprecated: 2.00-b4 @See: 'pointing' :: chopped Used for specifying a chopped data reduction. Can be set manually or automatically (via 'detect.chopped') based on the data itself. The key may trigger conditional statements and extra decorrelation steps. @See: 'detect.chopped', 'correlated..trigger' :: chopper @Alias -> correlated.chopper-x @Instrument: SHARC-2 @Advanced Remove signals that are correlated with chopper movement. The moving secondary mirror changes the telescope illumination, thus producing strong signals when observing under a bright atmosphere. To first order, such signals are linear with chopper displacement. Since most telescopes chop in the horizontal 'x' direction only, the 'chopper' keyword is aliased to decorrelation on motion in that direction. When a 2D chopper is used, you should decorrelate in both the 'x' and 'y' directions. @See: 'decorrelate.', 'detect.chopped' :: clip=X @Expert In early generations of the source map, force map pixels with flux below signal-to-noise level X to zero. This may help getting lesser baselines, and filtering artefacts around the brighter peaks. Often used together with 'blank' in the intermediate iterations. @See: 'blank', 'iteration.[?]' :: conditions[=] @Since: 2.01-4 Check conditional settings in the configuration Used without the pattern, it lists all conditionals under the current configuration tree. An optional pattern can be used to restrict the list to those conditions only, which start with the specified pattern. E.g.: > crush [...] -condition=despike Will lists all conditions that depend on one of the despike settings ('despike', 'despike2', or 'despike3') Due to the configuration hierarchy, the listing can also be produces for subtrees. E.g.: > crush [...] -date.conditions will list the conditions residing under the 'date' subtree (i.e. conditions originally specified as 'date.[...]'). @See: 'poll', 'blacklist' :: config= Load the configuration file filename. The file is looked for in the locations in the following order: 1. ./ 2. .// 3. ~/.crush2/ 4. ~/.crush2// Whenever a matching file is found its contents are parsed. Because of the ordering, it is convenient to create overriding configurations. Thus instrument specific settings can be used to override common defaults, and user specific settings placed in '~/.crush2' can override the distribution defaults. Whenever a configuration is parsed, there is a note of it on the console output so that one always knows which files were read and in what order. E.g. when using > crush laboca 12066 the following configuration files will be loaded in order (provided they exist): {$CRUSH}/default.cfg {$CRUSH}/laboca/default.cfg ~/.crush2/default.cfg ~/.crush2/laboca/default.cfg Each successively loaded file may override the options set before it. When a matching configuration file is not found in any of the standard locations (above), CRUSH will make one last attempt to interpret the argument as a standard pathname. This allows users to store and invoke custom configurations anywhere on the file system. @See: 'bright', 'faint', 'deep' :: convert @Instrument: SCUBA-2 @Since: 2.01-3 @Advanced Just convert all the SDF files to FITS, then exit. Batch conversion is useful if you are going to reduce the same dataset many times over (e.g. to optimize the reduction settings). You will need the 'ndf2fits' option to be configured and working, before batch conversions can be used. The resulting FITS files are written to the path defined by 'outpath', or 'datapath' (in the above order, depending on which is defined). @See: 'ndf2fits', 'outpath', 'datapath' :: correlated. Remove the correlated noise term accross the entire array. The stands for the name of the modality on which decorrelation is performed. E.g. 'obs-channels', 'gradients', 'squids' (ASZCA, GISMO or SABOCA), or 'rows' (SHARC-2). This is an effective way of dealing with most atmospheric, and instrumental signals, such as sky noise, ground pickup, temperature fluctuations, electromagnetic or microphonic pickups. The decorrelation of each modality can be further controlled by a number of subkeys (see below). The given decorrelation step must also appear in the pipeline 'ordering' before it can be used. @See: 'modality', 'ordering' :: correlated..gainrange=min:max @Expert Specify a range of acceptable gains to the given correlated signal , relative to the average gain response of the correlated mode. Channels that exhibit responses outside of this range will be appropriately flagged in the reduction, and ignored in the modeling steps until the flag is revised and cleared in another decorrelation step. @See: 'division..gainflag', 'correlated..signed' :: correlated..nofield @Expert @since: 2.02 Allows to decouple the gains of the correlated mode from the gain fields stored under the channel (which are initialized from the file specified by 'pixeldata'). @See: 'pixeldata', 'source.fixedgains' :: correlated..nogains @Advanced Disable the solving of gains (i.e. channel responses) to the correlated signal . :: correlated..nosignals @Expert Disable the solving for correlated signal , whose value stays fixed afterwards. :: correlated..phases @Expert @Since: 2.02 Decorrelated the phase data (e.g. for chopped photometry scans) together with the fast samples. The same gains are used as for the usual decorrelation on the fast samples. :: correlated..phasegains @Expert @Since: 2.04 Determine gains from the phase data, rather than from the correlated fast samples. You can also set this globally for all correlated modalities/modes using the 'phasegains' keyword. @See: 'phasegains' :: correlated..resolution=X @Advanced Set the time resolution (in seconds) for the decorrelation of . When dealing with 1/f-type signals, you probably want to set this to the 1/f knee time-scale or below if you want optimal sensitivities. Else, you may want to try larger values if you want to recover more large-scale emission and you aren't too worried about the loss of sensitivity. @See: 'extended' :: correlated..signed @Expert By default gain responses are allowed to be bidirectional, and flagging affects only those channels or pixels, whose absolute gain values fall outside of the specified range. When 'signed' is set, then gains are flagged with the signs also taken into account. I.e., under 'signed', 'gainrange' of '0.3:3.0' would flag pixels with a gain of -0.8, whereas the default behaviour is to tolerate them. @See: 'correlated..gainrange', 'correlated..nogains' :: correlated..span @Expert @Since: 2.02 Make the gains of the correlated modality span scans instead of integrations (subscans). You can also set this option for all correlated modalities at once using the 'gains.span' key. @See: 'gains.span', 'correlated..phases' :: correlated..trigger= @Expert You can specify a configuration key that is to serve as a trigger for activation the decorrelation of . This is used, for example to activate the decorrelation of chopper signals, if and when the 'chopped' keyword is specified. E.g.: chopper.trigger=chopped @See: 'chopper', 'chopped' :: correlated.* @Advanced You can use wildcards '*' to set options for all decorrelation steps at once. E.g.: correlated.*.resolution 1.0 Sets the time-resolution of all currently defined decorrelation branches (and modalities) to 1 second. @See: 'correlated.', 'resolution' :: dataname.end= @Instrument: GISMO @Expert @Since: 2.05 Allows specifying the naming convention of merged GISMO FITS files. E.g., the correct (and default) setting for runs 1--4 is: dataname.end GISO-IRAM-condensed.fits To accomodate different naming conventions, the option can take a comma sparated list of possible endings, which are tried in order until a suitable match is found inside the scan directory. @See: 'datapath', 'object', 'date' :: datapath= Start looking for raw data in directory . Some instruments may also interpret it as a root directory in which data may reside some specific hierarchy. E.g. in / for APEX bolometers. Thus, if an APEX instrument defines: datapath /homes/data project T-79.F-0002-2007 then crush will try to find data first in '/homes/data', then in '/homes/data/T-79.F-0002-2007' This provides a convenient way for accessing hierarchically stored data. See the instrument- specific notes for details. :: dataunit= @Advanced Specify the units, in which the data are stored. Typically, 'counts' or 'V', or any of their common multiples, such as 'mV', 'uV' or 'pcount' are accepted. The conversion from data units to jansky-based units is set via the 'jansky' option, while the choise of units in the data reduction is set by 'unit'. @See: 'unit', 'jansky' :: date=YYYY-MM-DD @Instrument: GISMO Specify the date of observation for GISMO data, which can be used along with 'object' to help locate scan data using scans numbers (and ranges). The date must be given in the specified format, identical to the one appearing in the standard IRAM scan IDs. @See: 'object', 'read' :: date.[...] @Advanced A way to set date specific conditional statements. Inside the square brackets one can specify a date range in YYYY-MM-DD format, separated by a colon ':' or hyphen(s) '-'. Wildcards '*' are also accepted to specify open ranges. E.g.: date.[2009.12.10--*] instrument.gain=-1000.0 Can be used to specify an inverted thousand-fold instrumental gain starting from Dec 10, 2009. @See: 'mjd', 'serial' :: deep Use for very faint sources which are not at all detected in single scans, or if you think there is too much residual noise (baselines) in your map to your liking. This setting results in the most agressive filtering. Will load the configuration from 'deep.cfg'. The output map is optimally filtered (smoothed) for point sources. @See: 'config', 'bright', 'faint' :: dejump @Since: 2.12 @Expert Allows identifying places in the data stream where detectors jump together (esp. SQUIDs under a transient B-field fluctuation) by the perceived increase in residual detector noise. Sub-settings are 'level' and 'minlength' @See: 'dejump.level', 'dejump.minlength', 'despike' ::dejump.level=X @Since: 2.12 @Expert The relative noise level at which jumps are identified. The value should be strictly greater than 1, with 2.0 being a safe starting point. Change with extreme caution, if at all. @See: 'dejump' ::dejump.minlength=X @Since:2.12 @Expert The minimum length (in seconds) of a coincident detector jump that is kept alive in the data. Jumps longer than this threshold will be re-levelled, wheareas shorter jumps will be flagged out entirely. @See: 'dejump' :: despike Use despiking. CRUSH allows the use of up to three different despiking steps, each configurable on its own, to specify a despiking method, S/N level and flagging criteria. See the various despiking options below: :: despike2 @Advanced A second round of despiking. @See: despike :: despike3 @Advanced A third round of despiking. @See: despike :: despike.flagcount=N @Expert Tolerate (w/o pixel flagging) up to N spikes up in each pixel. :: despike.flagfraction=X @Expert Tolerate (w/o pixel flagging) spikes up to fraction X of the scan frames in each channel. :: despike.framespikes=N @Expert Tolerate up to N spikes per frame. :: despike.level=X @Advanced Despike at an S/N level of X. :: despike.method= @Advanced CRUSH offers a choice of despiking methods to choose from. Each of these have their own pros and cons, and may produce different results and side- effects in different environments. The following methods are currently available: neighbours Despike only by comparing neighbouring samples of data from the same channel. absolute Flag data that deviates by the specified S/N level. gradual Like 'absolute' but proceeds more cautiously, removing only a fraction of most offending spikes at each turn. features Look for spikes wider than just a sigle sample. The 'width' subkey (below) the timescale, up to which spikes sought. All methods will flag pixels and frames if these have too many spikes. The flagging of spiky channels and frames is controlled by the 'flagcount, 'flagfraction' and 'framespikes' subkeys. @See: 'despike.flagcount', 'despike.flagfraction', 'despike.framespikes', 'despike.level', 'despike.width' :: despike.width=X @Expert When despiking using the 'features' method, spikes up to X second in width will be sought. :: detect.chopped @Advanced Try determine from the data itself if the chopper was used, and set the 'chopped' flag accordingly. This can be used to trigger the actication of specific reduction steps for chopped data. @See: 'correlated..trigger' :: division.= @Expert Specify a new pixel division from a list of pixel groups, separated by commas. For example, if the pixel groups 'my-pixels-1' and 'my-pixels-2' were defined (via 'group.') then the line division.my-division my-pixels-1,my-pixels-2 creates a division from these two groups. For every division created this way, CRUSH will also create a correlated modality with the same name. @See: 'correlated.', group. :: division..id= @Expert Specify a designated ID for the pixel division . This short ID will be printed on the console output, whenever the decorrelation step on the modality is performed in the reduction. @See: 'correlated.' :: division..gainfield= @Expert You can also specify the name of an existing JAVA double field inside the pixel class of the given instrument to serve the gains for the decorrelation of . Unless 'correlated..nogains' is also specified, these gains will be determined and overwriten each time the decorrelation takes place. @See: 'correlated..nogains' :: division..gainflag=N @Expert Specify a gain flagging pattern to use when flagging outlying gains in the decorrelation step of . Gain flags are normally one bit in a 4-byte integer, and can be specified using octal ('0' prefix) or hexadecimal ('0x' prefix) numbers, and regular integers. You should be careful not to interfere with existing flags, many of which may be hardcoded in the JAVA source. Use with extreme caution, if you must... @See: 'correlated..gainrange' :: downsample=X @Advanced Downsample the data by a factor of N. At times the raw data is sampled at unnecessarily high frequencies. By donwsampling, you can ease the memory requirement and speed up the reduction. You can also set the value to 'auto' (default), in which case an optimal downsampling rate is determined based on the typical scanning speeds, s.t. the loss of information will be insignificant due to unintended smearing of the data. :: drifts=X @Advanced Filter low frequencies below the characteristic timescale of X seconds. An effective way of dealing with 1/f noise. You can also use 'auto' to determine the filtering timescales automatically, based on 'sourcesize', scanning speeds, and instrument 'stability' time-scales. @Version: 2.12 As of version 2.12, the value 'max' is also accepted producing results identical to that of 'offsets'. @See: 'sourcesize', 'stability', 'offsets :: drifts.method= @Advanced Choose the method, with which drifts are removed. The choice is between 'blocks' or 'fft'. The former estimates and removes drifts from the timestreams in consecutive time windows (i.e. blocks) of data. This is very fast, and scales linearly with data size. The 'fft' method implements a spectral lowpass filter, with the same characteristic timescale as the other method. It is slower, and its computation requirement scales with N log N. :: ecliptic @Alias -> system=ecliptic Reduce using ecliptic coordinates (for mapping). @See: 'system', 'altaz', 'equatorial' :: elevation-response @Instrument: SHARC-2 @Expert Load and use an lookup table for the elevation dependent forward efficiency of the telecscope. The table is an ASCII file, as specified by Darren Dowell, and is available from the SHARC-2 web-site. CRUSH contains copies of the available tables and is configured to use them as needed. :: epoch=X @Instrument: GISMO Normally the coordinate epoch, in which the equatorial source coordinates are expressed, is stored in the data. However, for GISMO runs 1 and 2, this information was handled incorrectly. This option provides the means to correct that. The value can specify a year (e.g. 1950.0, or 2000.0), or a proper epoch designation (e.g. B1950, or J2000). IRAM uses J2000 for static sources and the current epoch for solar system objects. :: equatorial @Alias -> system=equatorial Reduce using equatorial coordinates (for mapping). @See: 'system', 'altaz' :: estimator= @Advanced 'median' or 'maximum-likelihood' estimators to use in deriving signal models. 'median' estimators are less sensitive to the presence of bright sources in the data, therefore it is the default for when 'bright' is specified (see 'bright.cfg'), and for some instruments (e.g. GISMO). When medians are used, the corresponding models are reported on the console output in []'s... (see the Console Output section of the README). @See: 'gains.estimator', 'weighting.method' :: exposureclip=X @Advanced Flag (clip) map pixels whose relative time coverage is less than the specified value X. This is helpful for discarding the underexposed noisy edges of the map. @See: 'noiseclip', 'clip' :: excessload=X @Instrument: SHARC-2 @Expert SHARC-2 can determine a line-of-sight opacity based on the total-power response of its detectors. However, for this to work well, all sources of optical loading on the detectors must be understood. The load curves (see 'response') were determined at one time only, and therefore this flag provides the means to specify a different optical loading environment from then, as an excess optical load (in Kelvins). @See: 'response', 'tau.' :: extended Try to better preserve extended structures. This setting can be used alone or in combination with a brightness options. The fainter settings the more difficult it is to recover extended emission. For bright structures recovery up to FOV (or beyond!) should be possible, while for faint structures ~1/4 FOV to ~FOV scales are maximally obtainable (see more on this in the README). @See: 'sourcesize', 'bright', 'faint', 'deep' :: faint Use with faint sources (S/N < ~30) when the source is faint but still visible in a single scan. This setting applies some more aggressive filtering of the timestreams, and extended structures. It invokes 'faint.cfg'. @See: 'bright', 'deep' :: fazo @Instrument: SHARC-2, GISMO An alternative to 'center' for providing pointing corrections. As opposed to 'center', which specifies incremental corrections, this option takes an absolute AZ pointing offset (i.e. FAZO at the CSO) which should have been the correct one (as opposed to the value used by the antenna computer during the observations). @See: 'fzao', 'center' :: febe @Instrument: APEX @Expert Defines the frontend-backend combination to use. E.g. for LABOCA, this would be set to 'LABOCA-ABBA'. :: filter @Since: 2.10 @Advanced Activate spectral filtering of time-streams. The filter components are set by 'filter.ordering' and can be configured activated separately. @See: 'filter.ordering', 'filter.hwp', 'filter.motion', 'filter.kill', 'filter.whiten' :: filter.hwp @Instrument: PolKa @Advanced @Since: 2.11 Use FFT filtering to get rid of the total-power modulation by the half-waveplate rotation. Can be used together with, or instead of, 'purify'. The advantage of the FFT filtering is that it works even if the waveplate data is not entirely accurate (i.e. jittery). However, if the waveplate phase is fully known, then 'purify' should be the prefered method for rejecting the unwanted total-power modulation. The number of harmonics (over the rotation frequency) is controlled by the 'harmonics' subkey. @See: 'filter.hwp.harmonics', 'waveplate.jitter' 'purify', 'waveplate.frequency' :: filter.hwp.harmonics @Instrument: PolKa @Expert @Since: 2.11 Specify how many harmonics of the waveplate rotation frequency to use in the half-waveplate filter. @See: 'filter.hwp' :: filter.kill @Since: 2.10 @Expert Allows completely quenching certain frequencies in the time-stream data. To activate, both this option and the 'filter' umbrella option must be set. The bands of the kill-filter are set by 'filter.kill.bands'. @See: 'filter', 'filter.kill.bands' :: filter.kill.bands= @Since: 2.10 @Expert Provide a comman-separated list of frequency ranges (in Hz) that are to be quenched by the kill-filter. E.g.: filter.kill.bands 0.35--0.37, 9.8-10.2 @See: 'filter', 'filter.kill' :: filter.motion @Since: 2.10 @Advanced The (typically) periodic motion of the scanning can induce vibrations in the telescope and instrument. Since these signals will be in synch with the scanning motion they will produce definite mapping artefacts (e.g. broad peaks or bowls in the map center, or ridges near the map edges). The motion filter lets you spectrally filter those frequencies where most of the scanning motion is concentrated. To activate, both this option and the 'filter' umbrella option must be set. The identification of rejected motion frequencies is controlled by the 's2n', 'above', and 'range' sub-keys @See: 'filter', 'filter.motion.s2n', 'filter.motion.above', 'filter.motion.range' :: filter.motion.above=X @Since: 2.10 @Expert The fraction, relative to the peak spectral component of the scanning motion, above which to filter motion. E.g.: filter.motion.above 0.1 will identify component that have amplited at least 10% of the main component. @See: 'filter.motion', 'filter.motion.s2n', 'filter.motion.range' :: filter.motion.range=min:max @Since: 2.10 @Expert Set the frequency range (Hz) in which the motion filter operates. @See: 'filter.motion', 'filter.motion.above', 'filter.motion.s2n' :: filter.motion.s2n=X @Since: 2.10 @Expert The minimum significance of the motion spectral component to be considered for filtering. @See: 'filter.motion', 'filter.motion.above', 'filter.motion.range' :: filter.ordering= @Since: 2.10 @Expert A comma-separated list of spectral filters, in the order they are to be applied. E.g., the default is: filter.ordering motion, kill, whiten applies first the motion filter, then kills specified spectral bands, and finally applies noise whitening on the remainder. Each of the components can be controlled and activated separately with the appropriate subkeys of 'filter' with the same names. @See: 'filter.motion', 'filter.whiten', 'filter.kill' :: filter.whiten @Since: 2.10 @Was: 'whiten' @Advanced Use noise whitening algorithm. White noise assures that the noise in the map is independent pixel-to-pixel. Otherwise noise may be correlated on spacific scales. Whitening is also useful to get rid of any signals (still) unmodelled by the other reduction steps. It should always be a last resort only. The modeling of signals is generally preferred. To activate, both this option and the 'filter' umbrella option must be set. @See: 'filter', 'whiten', 'filter.whiten.below', 'filter.whiten.level', 'filter.whiten.minchannels' 'filter.whiten.proberange' :: filter.whiten.below @Since: 2.10 @Was: 'whiten.below' @Expert By default the whitening filter only supresses excessive noise, but will leave those spectral components untouched, where the spectral power is deficient. Setting this option allows the boosting of such components to the white level, thus achieving true noise whitening, which is necessary to obtain maps without instrinsic spacial correlations. @See: 'filter.whiten', 'filter.whiten.below.max' :: filter.whiten.below.max=X @Since: 2.10 @Expert The maximum boosting of spectral power that may be applied when whitening frequencies with a deficiency of signal below the white level. The option acts as a safety pin, making sure that whitening does not enhance spectral bands insanely, when 'filter.whiten.below' is enabled. @See: 'filter.whiten.below' :: filter.whiten.level=X @Since: 2.10 @Was: 'whiten.level' @Advanced Specify the noise whitening level at X times the average (median) spectral noise level. Spectral channels that have noise in excess of the critical level will be approproately filtered to bring them back in line. Values clearly above 1 are recommended. Typically values around 1.5--2.0 are useful without overfiltering. @See: 'filter.whiten' :: filter.whiten.minchannels=N @Since: 2.10 @Was: 'whiten.minchannels' @Expert Make sure that at least N channels are used for estimating the white noise levels, even if the specified probe range is smaller or falls outside of the available spectrum. In such cases, CRUSH will automatically expand the requested range to include at least N spectral channels, or as many as possible if the spectral range itself is too small. @See: 'filter.whiten', 'filter.whiten.proberange' :: filter.whiten.proberange=from:to @Since: 2.10 @Was: 'whiten.proberange' @Expert Specify the spectral range (in Hz), in which to measure the white-noise level before whitening. It is best to use the truly flat part of the available spectral range, with no 1/f, resonances or lopass roloff are present. Wildcards '*' can be used for specifying open ranges. @See: 'filter.whiten', 'filter.whiten.minchannels' :: final:key=value @Alias -> iteration.[last] When used on the command line, a ':' can be used as a sepatation between the abbreviated condition and its statement. E.g.: > crush [...] -final:smooth=beam to specify beam smoothing in the last iteration. :: flag= Specify a list of backend channels that ought to be ignored for the successively read scans. Can use pixel numbers (i.e. APEX backend indexes) and ranges. E.g.: flag 5-10,12,33-37 Indeces normally start at 1 (i.e. not C-style!). @See: 'noslim', 'blind' :: flips @Alias -> correlated.flips @Instrument: GISMO @Since: 2.12 @Advanced This modality allows decorrelating SQUID mux signals with inverted current directions on every other pair of channels. Seems to work well on the SQUID level fluctuations seen in April 2012, esp. when used together with 'mux' decorrelation. @See: 'mux' :: forget=... Forget the priorly set values for the listed options as if they were never defined. E.g. forget=outpath will unset the 'outpath' option. You can specify more than one options as a comma-separated list. E.g. forget=outpath,project Will unset both the 'outpath' and 'project' options. Forgotten values may be 'recall'-ed. Additionally, 'forget' can be used to clear all conditionals or all blacklisted settings, if the argument list contains the values 'conditions' or 'blacklist', respectively. @See: 'recall', 'blacklist', 'remove' :: frames=- @Advanced Read only frames - from the data. Maybe useful for quick peeks at the data without processing the full scan, or when a part of the data is corrupted. :: fzao @Instrument: SHARC-2, GISMO Specify a zenith pointing offset. @See: 'fazo' :: gain=X @Expert Specify an instrument gain of X from the detector stage (or fixed signal stage) to the readout. Many instruments may automatically determine the relevant gain based on their data headers. For others, the gains may have to be adjusted by hand, especially if they are changing. Upon reading the scans, CRUSH will divide all data by the specified value, to bring all scans to a comparable signal level. Conversions to 'jansky' are referenced to such gain-scaled data. @See: 'jansky', 'dataunit', 'scale' :: gainnoise @Expert Add noise to the initial gains. There isn't much use for this option, other than it allows to check the robustness of the reduction on the initial gain assumption. Since gains are usually measured in the reduction itself, typical reductions should not depend a lot on the intitial gain values. @See: 'uniform' :: gains @Advanced Solve for pixel gains based on their response to the correlated noise (above). If not specified, then all decorrelation steps will proceed without gain solution. A model-by-model control is offered by the 'correlated..nogains' option. @See: 'gains.estimator', 'correlated..nogains' :: gains.estimator= @Advanced Specify the type of estimator ('median' or 'maximum-likelihood') to be used for estimating pixel gains to correlated signals. @See: 'estimator', 'correlated.' :: gains.span @Expert @Since: 2.02 Derive gains for all correlated modalities for entire scans, rather than separately for each integration (subscan). Most scans contain just one integration, and multiple integrations are often merged into one upon reading. However, for chopped photometry observations, the nod phases remain in separate subscans, and this option makes the gains apply to all nod phases in a scan, rather than separate gains for each nod phase. Alternatively, the gain spans can be controlled individually, per modality, via the 'correlated..span' keys. @See: 'correlated..span', 'phases' :: galactic @Alias -> system=galactic Reduce using new galactic coordinates (for mapping). @See: 'system', 'equatorial', 'altaz' :: gradients @Alias -> correlated.gradients @Advanced Shorthand for the decorrelation of gradients accross the detector array. Such gradients can occue as a result of spatial sky-noise, or as temperature variation across the detectors. @See: 'correlated.', 'blocks' :: grid=X set the map pixelization to X arcsec. Pixelization smaller than 2/5 beam is recommended. The default is ~1/5 beam pixelization. :: group.= @Expert Specify a list of channels, by index, that belong to a group with name . The list can contain comma separated list of indeces (starting with 1) and ranges. E.g.: group.my-group 10-20,45,50-60 defines a group named 'my-group' from the specified channels. @See: 'division' :: he3= @Instrument: LABOCA @Advanced Correct time-streams for He3 temperature fluctuations. specifies the source of the He3 data, which can be 'thermistor' or 'blinds'. The use of blind bolometers is quicker and preferred, unless you specifically wish to use the 'thermistors'. :: he3.gains @Instrument: LABOCA @Expert Specifies that rather than correcting for temperature fluctuations, the thermistor and bolometer data should be used to calculate appropriate temperature gains. This option should only be used on skydip scans with the shutter closed (i.e. only temperature signals without sky). Additionally 'forget=source' should be used to disable source modeling for such data. :: he3.maxrms=X @Instrument: LABOCA @Expert Define the maximum RMS temperature variation (Kelvin) over the duration of a scan. When a scan has variation larger than this limit, it will be dropped from the reduction. :: horizontal @Alias -> system=horizontal Reduce in horizontal coordinates (for mapping). This is often useful for determining pointing offsets or for beam mapping. @See: 'system', 'center', 'beammap', 'fazo', 'fzao' :: id.[] @Instrument: GISMO @Advanced @Since: 2.12-b1 Set conditions based on IRAM Scan ID ranges (of format 'YYYY-MM-DD.nnn'. Asterix ('*') denotes an open-ended range as usual. The lower bound is inclusive, but the upper bound is not. E.g.: id.[2012-04-11.132:2012-04-12.23] jansky 32.8 id.[2012-04-14.25:*] janky 28.6 Sets different conversion factors (counts/Jy) for the two id ranges. Note, that the first range does not include scan 23 taken on 2012-04-12 itself. The second line shown an open-ended range starting with scan 25 on 2012-04-14. @See: 'mjd.[]', 'serial.[]', 'date.[]' :: indexing @Expert Allows the use of data indexing to speed up coordinate calculations for mapping. Without indexing the map coordinates are calculated at each mapping step. This can be slow because of the complexity of the spherical projections, which often require several complex math evaluations. With indexing enabled, the calculations are performed only once, and the relevant data is stored for reuse. However, the storage of indexes more or less doubles the memory requirement of CRUSH. Thus, 'indexing' may be disabled for very large reductions. Alternatively, one may control the amount of memory such indexes may use, via the 'indexing.saturation' option. @See: 'indexing.saturation', 'grid' :: indexing.saturation=X @Expert Specify the maximum fraction X of the total available memory that can be filled before indexing is automatically disabled. Given a typically 20% overhead during reduction, values below 0.8 are recommended to avoid overflows. @See: 'indexing' :: invert Invert signals. This setting may be useful in creating custom jackknifes, where the user wishes to retain control over which scans are inverted. @See: 'gain', 'scale', 'jackknife' :: iteration.[N] Use as a condition to delay settings until the Nth iteration. E.g. iteration.[3] smooth halfbeam or > crush [...] -iteration.[3]smooth=halfbeam [...] to specify half-beam smoothing starting from the 3rd iteration. @See: 'iteration.[?]' :: iteration.[last] Specify settings that should be interpreted only at the beginning of the last iteration. @See: 'iteration.[?]' :: iteration.[last-N] Activate settings N iterations before the last one. E.g. iteration.[last-2] forget=clip Disables clipping two iterations before the last one. @See: 'iteration.[?]' :: iteration.[X%] Activate settings as a percentage X of the total number of iterations (as set by 'rounds'). E.g. iteration.[50%] forget clip can be used to disable the S/N clipping of the source map half way through the reduction. @See: 'iteration.[?]' :: iteration.[?] Apply settings at the beginning of specific iterations. Because of the flexible syntax, the same iteration can be referred to in different ways. Consider a reduction with 10 rounds. Then, iteration.[5] smooth 5.0 iteration.[50%] smooth 10.0 iteration.[last-5] smooth beam can all be used to define what happens in the 5th iteration. CRUSH will parse these conditionals in the above order: first the explicit iteration settings then those relative to the reduction length, and finally the settings relative to the end of the reduction. Thus, in the above example the beam smoothing will always override the other two settings. @See: 'iteration.[N]', 'iteration.[X%]', 'iteration.[last]', 'iteration.[last-N]' :: jackknife Jackkniving is a useful technique to produce accurate noise maps from large datasets. When the option is used the scan signals are randomly inverted, s.t. the source signals in large datasets will tend to cancel out, leaving one with pure noise maps. The sign inversion is truly random, s.t. repeated runs with the 'jackknife' flag will produce a different jackknife every time. If you want more control over which scans are inverted, consider using the 'invert' flag instead. @See: 'invert', 'scramble', 'jackknife.frames', 'jackknife.channels', 'jackknife.alternate' :: jackknife.alternate @Advanced @Since: 2.05 Rather than randomly inverting scans for a jackknife, this option will invert every other scan. This may be preferred for small datasets, because it leads to better cancellation of the source signals, especially with an even number of scans, chronologically listed. To have the desired effect, use instead of 'jackknife', rather than together with it (otherwise, the ordered inversion will simply compound the random method of the standard 'jackknife'). @See: 'jackknife' :: jackknife.channels @Expert @Since: 2.04 Jackknife channels, such that they are randomly inverted for the source model. Beware, however, that channel-wise jackknives aren't as representative of the true noise as the regular scanwise 'jackknife' is, because they will reject spatial correlations and instrumental channel-to-channel correlations. @See: 'jackknife', 'jackknife.frames', 'scramble' :: jackknife.frames @Expert @Since: 2.04 Jackknife frames, such that they are randomly inverted for the source model. Beware, however, that frame jackknives aren't as representative of the true noise as the regular scanwise 'jackknife' is, because they will reject temporal correlations. @See: 'jackknife', 'jackknife.channels', 'scramble' :: jansky=X Specify the calibration factor from data units to Jy. @See: 'dataunit', 'gain', 'jansky.inverse'. :: jansky.inverse When used, the 'jansky' definition is inverted to mean Jy to data unit. This used to be the old definition used in crush-1.xx and minicrush. @See: 'jansky' :: log @Advanced @Since: 2.03 Log the scans after the reduction. (Similar logging is available without reducing at all via the 'obslog' key). You can control what quantities are logged and in what format via the 'log.format' key. Please refer to the README for details on how the logging works and what you many log and how. @See: 'obslog', 'log.file', 'log.format', 'log.conflict' :: log.conflict= @Expert @Since:2.03 Since log files are locked to their format, a changing for format without specifying a new log file will cause a conflict. Use this key to determine how such conflicts are resolved. The following values are permitted: overwrite Delete the previous log file, and create a new one with the same name using the new format. version Try find an alternative version of the log file (with .1, .2 ... extension attached to the file name) in the new format, or create a new such version. The default behaviour is to assume versioning, in order to preserve prior logs. @See: 'log.file' :: log.file= @Advanced @Since:2.03 Set the file to which reductions will be logged. You can use the usual path specifications of CRUSH, including shorthands (such as '~') and environment variables (such as {$HOME}). The actual log file used may be a sub-version of the specified file (with .1, .2 ... extension added) if the conflict policy set by 'log.conflict' is to use versioning. @See: 'log', 'log.format', 'log.conflict' :: log.format= @Expert @Since: 2.03 Specify the format of the log file. You can control what quantities are logged and how they should appear. Please refer to the README for more details on the available options @See: 'log', 'log.file', 'log.format' :: maitau.fallback= @Instrument: SHARC-2 @Advanced Define which tau value to use in case the MaiTau lookup fails. The possible values are: direct Calculate tau from the total-power loading of the detectors 225GHz Use the 225GHz tipper value. 350um Use the 350um tipper value. pwv Use precipitable water vapor. sharc2 Use the value specified by tau.sharc2 Other than the 'direct' flag, the values may be specified with the corresponding tau settings. @See: 'maitau.server', 'tau.225GHz', 'tau.350um', 'tau.sharc2' :: maitau.server=IP @Instrument: SHARC-2 @Expert Specify the MaiTau server to use, either as an IP address, or server name. This should probably be set to 'agn.caltech.edu', or to the equivalent 'fangorn.submm.caltech.edu'. MaiTau is a server-based lookup of the CSO opacities, based on dailly polynomial fits to the measured 225GHz and 350um tipper data. The polynomials smooth out short-term fluctuations and measurement errors, providing a smoothly varying function of tau with time. When using MaiTau, CRUSH will try use the 350um fit, and then the 225GHz fit (if available), from which it calculates an appropriate in-band zenith tau value. @See: 'tau..a', 'tau..b' :: mappingfraction=X @Advanced Specify a minimum fraction of pixels in the array that have to remain unflagged for creating a map from the scan. If too many pixels are flagged in the reduction, it may be a sign of bigger problems, questioning the reliability of the scan data. It is best to skip over problematic scans in order to minimize their impact on the mapping. @See: 'mappingpixels' :: mappingpixels=N @Advanced Specify a minimum number of pixel, which have to be unflagged by the reduction in order for the scan to contribute to the mapping step @See: 'mappingfraction' :: map.size=X,Y @Advanced Explicitly set the size of the mapped are, centered on the source to and X by Y arcseconds rectangle. Normally, the map size is automatically calculated to contain all of the data. One may want to restrict mapping to smaller regions (outside of which, there should be no bright sinals). The letter 'x' may also be used instead of the comma to separate the dimensions. E.g.: map.size=300x200 will restrict mapping to a 300" by 200" are (in the chosen coordinate system of the mapping), centered on the nominal source coordinates. @See: 'system' :: mjd.[...] @Advanced Specify settings that are conditionally activated if and when the MJD of the scan falls within the specified range inside the square brackets. Wildcards '*' can be used to indicate open ended ranges. E.g.: mjd.[*-54230.25] jansky=5.0 specifies that up until 6:00 UT on 10.05.2007, the conversion factor of 5.0 data units per Jy should be used. @See: 'date.[...]', 'serial.[...]' :: mux @Alias -> decorrelate.mux @Instrument: SHARC-2, GISMO, SCUBA-2 @Advanced Decorrelate on MUXes, or set options for it. @See: 'decorrelate.' :: name= Specify the output image file name, relative to the directory specified by 'outpath'. When not given minicrush will chose a file name based on the source name and scan number(s), which is either ..fits or .-.fits For mapping. Other source model types (e.g. skydips or beam maps) may have different default naming conventions. @See: 'outpath' :: ndf2fits= @Instrument: SCUBA-2 @Since: 2.01-1 SCUBA-2 data is released in a proprietary SDF format, which is not well documented for direct use. Instead, the StarLink software suite provides utilities for manipulating such files. Among these it provides a conversion utility 'ndf2fits' that can translate SDF files into FITS files readable by CRUSH. You can do the conversion yourself using the 'proexts' option. Or, you can let CRUSH convert the input files on-the- fly, as necessary. This option serves to specify the full path to the ndf2fits utility, including the executable name. E.g.: ndf2fits=/usr/local/starlink/convert/ndf2fits Clearly, you will need a functional installation of the Starlink software or, at minimumm it conversion package, for this option to work. :: noiseclip=X Flag (clip) map pixel with a noise level that is more than X times higher than the deepest covered parts of the map. @See: 'exposureclip', 'clip' :: nogaps[=JSharc] @Instrument: SHARC-2 @Advanced Terminate the reading of the data at the first gap. During the early SHARC-2 runs when JSharc was used for the acquisition of the data, there was an occasional damaging timing bug resultuing from the wraparound of an internal buffer. The bug manifested in a sudden jump in the timestamps, making it relatively easy to diagnose if this happened during the scan. The optional argument 'JSharc' restricts the gap termination to data obtained using 'JSharc' alone (default). :: noresistors @Instrument: LABOCA @Expert Do not use the resistor channels in the decorrelation of electrinic signals, such as 'boxes', 'cables' and 'amps'. In LABOCA several of the readout channels are connected not to light-sensitive detectors, but to fixed resistors. While these are not sensitive to radiation or temperature the channels will still be subject to electronic pickup. Therefore, the default is to use these channels when decorrelating signals, which are thought to originate within the electronics. This option can be used to overrride this behavior, and restrict all decorrelation steps to detector channels only. @See: 'boxes', 'cables', 'amps' :: noslim @Expert After reading the scans, CRUSH will discard data from from channels flagged with a harware problem (any bit in 0xFF), to free up memory, and to speed up the reduction. This option overrides this behaviour, and retains all channels for the reduction, whether these are used or not. :: object= @Instrument: GISMO Can be used to help locate GISMO data with scan numbers when used together with the 'datapath' and 'date' options. E.g.: > crush [...] -datapath=. -object=Mars \ -date=2010-04-15 12-14 Will reduce Mars scans 12 to 14 from Apr 15, 2010. The object name is case-sensitive! @See: 'datapath', 'date' :: object.[...] @Since:2.05 @Advanced Allows you to set conditionals based on object names. All source names that begin with the specified string (case insensitive!) will satisfy the condition. Thus, the SHARC-2 setting: object.[PNT_] point will automatically perform a pointing fit (see 'point' option) at the end of the reduction for all sources whose catalog names begin with 'PNT_', such as 'PNT_3C345'. @See: 'point' :: obslog @Advanced @Since: 2.03 Log the scans immediately after reading, and without reducing them at all. (Similar logging is available post reduction via the 'log' key). Please refer to the README for details on how the logging works and what you may log and how. @See: 'log', 'obslog.file', 'obslog.format', 'obslog.conflict' :: obslog.conflict= @Expert @Since:2.03 Since log files are locked to their format, a changing for format without specifying a new log file will cause a conflict. Use this key to determine how such conflicts are resolved. Please refer to 'log.conflict' for details. @See: 'log.conflict', 'obslog.file' :: obslog.file= @Advanced @Since:2.03 Set the file to which scans will be logged. Refer to 'log.file' for details. @See: 'log.file', 'obslog.format', 'obslog.conflict' :: obslog.format= @Expert @Since: 2.03 Specify the format of the obslog file. You can control what quantities are logged and how they should appear. Please refer to the README for more details on the available options @See: 'obslog', 'obslog.file', 'obslog.format' :: offsets @Advanced Remove the residual DC offsets from the bolometer signals (ignored when 'drifts' below is also specified.) @See: 'drifts' :: ordering=a,b,c @Advanced Specify the order of pipeline elements as a comma separated list of keys. @See: 'offsets', 'drifts', 'weighting', 'despike' 'source', 'decorrelate.', 'whiten', 'time-weighting' :: outpath= Specify the output path, where all CRUSH output will be written (including maps etc.). Path names follow the usual rules (See 'Basic Configuration' section in the README), and can use '~' to refer to the home directories or to environment variables in {} brackets with a $ sign. E.g. outpath={$HOME}/images in UNIX specifies the 'images' subdirectory inside a user's home. :: pcenter=row,col @Instrument: SHARC-2, GISMO @Advanced Defines the pointing center used, in terms of the instrument pixel row and colum coordinates. Pixel 1,1 designates the top-left corner of the array in horizontal (AZ/EL) or equivalent Nasmyth coordinates. Columns increase to the right, while row numbers increase downward. Thus, the center of the SHARC-2 array is 6.5,16.5, while the center of GISMO is 8.5,4.5. The 'pcenter' option is not used if the pixel positions are loaded from an RCP data file, instead of being calculated (since a rectangular grid can no longer be assumed). @See: 'rcp', 'rcenter', 'pixelsize', 'rotate' :: phases @Expert @Since: 2.02 Decorrelate also the phase data (e.g. for chopped observations) for all correlated modes. Alternatively phase decorrelation can be turned on individually for modalities using the 'correlated..phases' options. @See: 'correlated..phases', 'gains.span' :: phases.estimator= @Expert @Since: 2.04 Allows to override the global estimator setting for the phases (e.g. chopper phases). The can be either 'median' or 'maximum-likelihood' all other values default to 'maximum-likelihood'. When not set the global 'estimator' setting will be used for the phases also. @See: 'estimator' :: phasegains @Expert @Since: 2.04 Use the information in the phases to calculate gains for all correlated modes. (The default is to use the fast samples for calculating gains). Alternatively you can set this property separately for each correlated modality. @See: 'correlated..phasegains' :: pins @Alias -> correlated.pins @Instrument: GISMO, SCUBA-2 @Advanced Decorrelate on readout address lines (across the MUXes) or set options for it. @See: 'decorrelate.', 'pins.group', 'mux' :: pins.group=N @Instrument: GISMO @Expert Based on the 'pins' alias for GISMO, it defines a grouping of N neighbouring address lines. For each MUX, there are 32 address lines, which are read out sequentially in the time-domain multiplexing scheme. Thus, pins.group=4 will group the address lines 1-4, 5-8, ..., 29-32 together across all MUXes, thus increasing the number of channels in each group. The decorrelation of address lines using the 'pins' option will take place on these groups. @See: 'pins', 'mux' :: pixeldata= @Expert Specifies a pixel data file, providing initial gains, weights and flags for the detectors, and possible other information as well depending on the specific instrument. Such files can be produced via the 'write.pixeldata' option (in addition to which you may want to specify 'forget=pixeldata' s.t. flags are determined without prior bias). @See: 'gainnoise', 'uniform', 'flag', 'blind' :: pixelsize=X,Y @Instrument: SHARC-2, GISMO, P-ArTeMiS @Expert Specify the size of rectangular pixels in a grid. This is used for calculating pixel positions on a rectangular grid. The information is ignored when positions are loaded from an RCP data file (as a regular grid can no nonger be assumed). @See: 'rcp', 'pcenter', 'rcenter' :: planetary @Since: 2.11 Specify, explicitly, that the object is moving in the celestial frame (such as solar system objects, like planets, asteroids, comets and moons). This way, data will be properly aligned on the coordinates of the first scan. If the data headers are correctly set up (and interpreted by crush) moving objects can be auto detected. This option is there, in case, things do not work as expected (e.g. if you notice that your solar system object smears or moves across the image with the default reduction. Currently, the option forces equatorial coordinates. @See: 'system' :: point @Since: 2.00-b4 This is a convenience key for triggering settings for reducing pointing scans. Currently, it invokes 'iteration.[last] pointing=suggest', i.e. suggesting pointing corrections in the last iteration. @See: 'pointing', 'pointing.method', 'fazo', 'fzao' :: pointing= @Since: 2.00-b4 Specify pointing corrections, or the way these should be derived. The following values are accepted: x,y Specify relative pointing offsets as comma-separated valutes (in arcseconds) in the system of the telescope mount. I.e., these should be horizontal offsets for ground-based telescopes with an Alt/AZ mount. Some instruments may allow more ways to specify pointing corrections (E.g. 'fazo' and 'fzao' for SHARC-2). suggest Suggest pointing offsets (at the end of the reduction) from the scan itself. This is only suitable when reducing compact pointing sources with sufficient S/N to be clearly visible in single scans. @See: 'point', 'fazo', 'fzao' :: pointing.exposureclip=X @Since: 2.04 @Expert Clip away the underexposed part of the map, below a relative exposure X times the most exposed part of the map. The option works similar to the 'exposureclip' option, but applies only to the map used for deriving the pointing internally. @See: 'exposureclip' :: pointing.method= @Since: 2.00-b4 @Expert Specify the method used for obtaining positions of pointing sources. Currently 'centroid' (default) and 'peak' are supported. This option also controls how pixel position information (RCP) is calculated for 'beammap' reductions. @See: 'point', 'beammap' :: pointing.model= @Advanced @Instrument: GISMO @Since: 2.04 Use a pointing model to derive and apply pointing corrections automatically. The argument is the name of the file containing the pointing constants. The file is simply an ASCII file, with separate lines containing the pointing constants and their incremental values. E.g., the pointing model file derived for 2011 Apr 13 contains the entries: P4 = 22.54 P5 = 17.17 P9 = -11.56 P10 = -38.59 P11 = 2.60 You can still apply a incremental offset on top of this model, using the 'pointing' key the usual way. By default, the pointing model contains aggregated constants, which are compared to the telescope model to calculate appropriate corrections. However, it is also possible to supply incremental constants if the 'pointing.model.incremental' option is also set. @See: 'pointing', 'pointing.model.incremental' 'pointing.model.static', 'pointing.table' :: pointing.model.incremental @Instrument: GISMO @Since: 2.04-2 @Advanced Specify the the pointing model supplied via 'pointing model is an incremental model on top of whatever model was used during the observations. @See: 'pointing.model' :: pointing.model.static @Instrument: GISMO @Since: 2.04-2 @Expert Use the static terms only of the supplied pointing model. By default the GISMO model can have time variant coefficients defined also. When this option is set, the time variability will be ignored, and only the static values are used. @See: 'pointing.model' :: pointing.significance=X @Since: 2.00-0 @Expert Set the significance (S/N) level required for pointing sources to provide a valid pointing result. If the option is not set, a value of 5.0 is assumed. :: pointing.table= @Advanced @Instrumment: GISMO @Since: 2.04 Use a pointing table (obtained via the 'log' option) to derive residual pointing corrections, on top of the pointing model. You can still use 'pointing' to add yet another increment. For the residual correction to work, the log file must contain the columns 'id', 'AZ', 'EL', 'pnt.X', 'pnt.Y', 'src.peak', 'src.dpeak', and 'src.FWHM'. The routine will weight pointing data by distance to source, and by distance in time of observation. When using this option, you should make sure to remove or comment out any entries with unreliable pointing results. @See: 'pointing', 'pointing.model' :: pol @Alias --> 'source.polar' @Since: 2.10 :: poll[=] Whenever unsure what options are set at any given stage, you can poll the settings. Without an additional argument it will list all currently defined setting to the standard output. When an argument is specified it will list the configuration settings that start with the specified string. E.g. > crush [...] -poll=despike will list all despiking options (e.g. all settings under the 'despike', 'despike2', and 'despike3' branches) that have been defined prior to the invokation of the '-poll' command. Due to the hierarchical nature of the configurations you can also selectively poll settings under subtrees of the configuration. E.g.: > crush [...] -source.poll Will lists all source model related settings stored under the 'source' subtree. @See: 'conditions', 'blacklist' :: positions.smooth=X @Expert Specify that the telescope encoder data should be smoothed with a time window X seconds wide, in order to minimize the effects on encoder noise on the calculation of scanning speeds and accelerations, based on which data may be discarded, and optimal downsampling rates are determined. @See: 'aclip', 'vclip', 'downsample' :: project= @Instrument: APEX Some instruments (e.g. APEX bolometers) may require a project ID to be set in order to locate scans by serial number. Use capitalized form when defining APEX projects. E.g., project T-79.F-0002-2007 :: projection= Choose a map projection to use. The following projections are supported: SIN -- Slant Orthographic TAN -- Gnomonic ZEA -- Zenithal Equal Area SFL -- Sanson-Flamsteed MER -- Mercator CAR -- Plate-Carree AIT -- Hammer-Aitoff GLS -- Radio (aka Global Sinusoidal) @See: 'system', 'grid', 'mapsize' :: purify @Instrument: PolKa @Advanced @Since: 2.11 Really a generic option for getting rid of unwanted signals before the mapping step. The exact action may be different from one instrument to another. For now, only PolKa uses this option for removing the total- power modulation before producing the Q and U maps. The method uses a template of the modulation as a function of the phase. It should work perfectly, if the waveplate angles are accurately known. However, FFT filtering (via 'filter.hwp') is more suited for uncertainties in the waveplate angles. @See: 'filter.hwp' :: radec @Alias -> system=equatorial Reduce using equatorial coordinates (for mapping). (Default) @See: 'system', 'altaz' :: range=min:max @Expert @Since: 2.03 Set the acceptable range of data (in the units it is stored). Values outside of thi range will be flagged, and pixels that are consistent offenders will be removed from the reduction (as set by 'range.flagfraction'). @See: 'dataunit', 'range.flagfraction', 'range.auto' :: range.auto @Expert @Instrument: LABOCA @Since: 2.03 Set the ADC range automatically using the actual backend gain setting @See: 'range' :: range.flagfraction=X @Expert @Since: 2.03 Specify the maximum fraction of samples for which a channel can be out of range (as set by 'range') before that channel is flagged and removed from the reduction. @See: 'range' :: rcenter=dX,dY @Instrument: SHARC-2 @Expert Specify a rotation center, in the coordinate system of the array (AZ,EL or Nasmyth coordinates). Works similarly to 'pcenter' @See: 'pcenter' :: rcp= @Advanced Use the RCP file from . The usual rules of path specification apply (see the 'Basic Configuration' section of the README.). The file should conform to the standard IRAM or APEX RCP specs containing the information in ASCII columns. RCP files can be produced by the 'beammap' option, from scans, which move a bright point source over all pixels. For rectangular arrays, pixel positions can also be calculated on a regular grid using 'pixelsize' and 'pcenter' @See: 'beammap', 'pixelsize', 'pcenter' :: rcp.center=x,y @Advanced Define the center RCP position at x,y in arcseconds. Centering takes place immediately after the parsing of RCP data. @See: 'rcp' :: rcp.gains @Advanced Calculate coupling efficiencies using gains from the RCP files. Otherwise uniform coupling is assumed with sky noise gains from the 'pixeldata' file. @See: 'rcp' :: rcp.rotate=X @Advanced Rotate the RCP positions by X degrees (counter clockwise). Rotations take place after centering (if specified). @See: 'rcp' :: rcp.zoom=X @Advanced Zoom (rescale) the RCP position data by the scaling factor X. Rescaling takes place after the centering (if defined). @See: 'rcp' :: read= Read the scans in the list. The list can be a comma, or space-separated list of arguments, which can be contain the following types of arguments: Read the scan data from , which can be either a fully specified path, or relative to 'datapath'. N Read scan number N. May need additional options such as 'project' (APEX) or 'date' and 'object' (GISMO) to be set in order to locate the data in a filesystem hierarchy. from-to A hyphen '-' separated range of scan numbers (inclusive). Same considerations apply as above. In all cases, the 'read' key can be omitted on the command line, where it suffices to list the arguments with white spaces, without any option key. E.g.: > crush [...] myscan.fits 11564 12067-12071 @See: 'datapath', @APEX:'project', @GISMO:'date', @GISMO:'object' :: recall=