-
Notifications
You must be signed in to change notification settings - Fork 0
4_Troubleshooting
The following sections list the solutions to the most common doubts and problems encountered by users, including indications on how to deal with present bugs or inefficiencies in the code.
PROBLEM:
- Files are not correctly reorganized by “separate”
Is your dataset properly organised? The procedure considers a strict folder/file tree for the input material. You need to create a parent folder, named as you wish, containing all the day-based folders - the ones named YYYYMMDD - you want to reduce. Each of those day-based folders must keep the original inner SCAN-SUBSCAN structure, i.e. they must contain the scan-based subfolder that in turn contain the subscans (FITS files).
The code actually searches for folders, inside the parent one, that match with the ‘2*’ string. Thus, if you don’t want to stick to the original YYYYMMDD naming, you can change it while complying with this requirement.
PROBLEM:
- dataflagging does not find any file to be flagged
Is your dataset properly organised? Have you selected the correct input folder? When using dataflagging, you need to pick a day-based folder as the input choice, then the procedure will browse each of the scan-based subfolders.
PROBLEM:
- dataflagging shows black windows where data plots should appear
This happens when previously-run programs inside IDL leave some pending display operations. Reset your session (with .full) and re-compile and re-run dataflagging.
PROBLEM:
- dataflagging has erased a previously written checkfile
Beware: when dataflagging finds that a scan-based folder already contains a checkfile, it asks whether you wish to keep it or you prefer to start over. Carefully read the question: by answering "YES", you indicate you want to keep those flags and go on appending new ones for the so-far-unflagged data (if any). By answering "NO", you decide to start over, thus rewriting the checkfile from scratch.