Warnings are printed in cyan text and usually indicate that a result appears to be different than expected. Some warnings can lead to downstream errors, but these are rare.
If you see a warning that is not shown here, please file a bug report to the SCUBA-2 data reduction mailing list: scuba2dr@phas.ubc.ca
Image has no maximum
Image s20120509_00013_450_back has no significant maximum
- Cause: The source is too faint to be detected in the map. If this is a calibrator, this message will usually be accompanied by an error stating that the source was too weak to calculate an FCF.
- Action: None.
No pointing source
Unable to locate a point source to determine pointing offsets
- Cause: The pipeline could not locate a source bright enough to point on. While there are multiple reasons that this message may appear, it is almost always due to the source being too faint. Common at 450 um when pointing on blazars.
- Action: Choose a brighter source to point on.
No focus source
Unable to locate a significant maximum - cube will not be adjusted
- Cause: As above, the pipeline failed to find a source at the central SMU position has failed because the source is too faint. Derivation of best-fit SMU position will probably fail.
- Action: Choose a brighter source to focus on.
No source detected
Unable to locate a point source to determine beam size
- Cause: As above, except that the pipeline was attempting to determine the beam size, which is only attempted for calibrators and/or pointing sources.
- Action: None.
No JCMTSTATE
Unable to read JCMTSTATE.TCS_TR_SYS from input file
No good bolometers
Skipping display of focal-plane mosaic - no good bolometers
Nosuitable fastramp
Unable to retrieve a suitable fastramp: using the internal solution. Noise results may not be reliable.
- Cause: The pipeline was unable to retrieve a dark fastramp to include in processing the current dark noise data. This may happen on the first observation of the night, but should otherwise not appear.
- Action: None required, but if not the first observation of the night then something may have gone wrong with the pipeline or the index files written by the pipeline may have been removed. In this case, the warning should disappear after the next SETUP.
Too many samples requested
Requested number of samples exceeds number to be processed - using available data (1724 samples)
- Cause: The final file in a noise observation is usually shorter than the others and so the pipeline just uses the data it has when calculating the average power spectrum. Depending on how short this file is, the noise observations may not be reliable. Should never be seen in the QL pipeline.
- Action: None.