Online FILLM Data Archive System Observing Guides & Tools |
1 - IntroductionOnline filling of VLA data is available at the AOC. Online (or realtime) FILLM is very similar to the more familiar offline FILLM. The main difference is that offline FILLM reads from a tape drive, whereas online FILLM receives data from disk. Depending on the workstation, one or more tape drive numbers are reserved for online use; at AIPS startup a list of all available tape drives - including the online pseudodrives are listed. Set INTAPE to a number listed as being reserved for online data filling, and type MOUNT. If there is no realtime FILLM tape device listed at startup, ask one of the AIPS support people to help you. Before starting FILLM, make sure you run the correct version by typing: version 'online'. 2 - Interactive controlThe user can determine interactively whether new data should be appended to existing files, or be put in newly created files. This is regulated by the first element of the hidden adverb APARM. Hidden means that APARM can only be specified using the TELL mechanism during the execution of the task: it will not show up in INPUTS FILLM, but it will in SHOW FILLM. Both on and offline FILLM start with the option to append data to newly created files (or older files, if DOCONCAT=1), whenever possible. This behavior can now be changed interactively using TELL FILLM according to the following table:
In the previous table, the listings under procedure are short. AIPS procedures which execute the TELL command and give it the proper OPTELL and APARM(1). Perhaps the most useful option is break. This closes the file when the current scan is finished, creates a new file, but after this appends further new data to this new file. The closed file is ready to be viewed and analyzed by AIPS software. This might well become the standard way of running online FILLM: let FILLM append until the user tells FILLM to close the file and create a new one. This new file will receive all the new data until the users tell FILLM again to break. 3 - Ending FILLMThere are three ways to end FILLM. abort is instantaneous, and will probably leave the output files in a corrupted state. The other two possibilities properly close the FILLM output: stop takes as long as the TELL command takes to be recognized, at the most 1 - 2 minutes. quit allows FILLM to finish the current scan first, which may take much longer. Finally, FILLM will end automatically under certain conditions, described in the following section. 4 - VLAOBS and subarraysFILLM may be started ahead of time, before the proposal code of interest has begun. FILLM's starting and finishing is governed by the adverbs VLAOBS - specifying the program code for the observation to be filled - and CPARM(6) (subarray number) as listed in the following table:
The first case, VLAOBS non-blank, CPARM(6) = 0, is the recommended mode of running online FILLM: the user does not have to know about the actual subarray, and FILLM exits automatically. There is one caveat: under some circumstances, after program code VLAOBS has executed, there may not be another program starting in the same subarray for a long time. In that case FILLM does not finish automatically, and the user will have to stop FILLM by hand. Make sure to enter the correct program code: if you specified proposal code AV65 in the observe file, FILLM will look in vain for e.g. VLAOBS='AV065'. 5 - Example
6 - Common problems and their causesProblem: On starting FILLM, you receive the following message: FILLM1: ZTPOPN: NO SUCH LOGICAL DEVICE = AMT02: FILLM1: TAPIO: ERROR 3 OPENING FILE Solution: you have not mounted a tape drive. Find out a correct tape number and do a MOUNT. Problem: On starting FILLM, you receive the following message: FILLM1: ZTPWAT: ERROR 3 FOR LUN = 32 IBUFF = 1 TO TAPE FILLM1: ZERROR: IN ZTPWA2 ERRNO = 5 (I/O error) FILLM1: this usually means PARITY ERROR Solution: You are running regular FILLM. Set the AIPS version to ONLINE and restart FILLM Problem: While running FILLM, commands like stop and break are not recognized. Solution: Do a RESTORE 0 and try again. Content reviewed on: 16-October-2006
Page maintained by Jeff Goldin |