WeraDesk Web Interface Documentation - Script Control

The actual control parameters are saved in /home/wera/etc/WeraDesk.tmp and the files /home/wera/public_html/WeraDesk.html and /home/wera/public_html/Wstatus.shtml are modified automatically by Proc_WeraDesk. Please do not manually edit WeraDesk.html or Wstatus.shtml, as Proc_WeraDesk may not be able to process them any more. A template of working files WeraDesk.html and Wstatus.shtml can be found at /home/wera/weradesk/ . Copy these files to /home/wera/public_html/ in case of problems and fill in or modify the required fields with a web browser.

To configure complicated schedule lists of mixed acquisition modes and use WeraDesk for this, go through the following procedure:

Stop any automatic cycles, i.e. the status window should show 'Disabled' in the lower right corner.
Configure a single measurenent, e.g. Single Acquisition, Calibration, FM raw Acquisition. Fill out all fields correctly, especially the field RX Offset for calibration measurements; Cont. Acqu. Start Time and Cycle Repetition Time can be ignored for single measurenents. Click Submit to start the configured measurement immediately. You will get a corresponding parameter list at /home/wera/etc/WeraDesk.tmp .
Wait for the measurement to finish and check if the measured data are ok. If not, go back to step 2.
run /home/wera/WeraDesk/Proc_WeraDesk -i -f/home/wera/weractrl/sort_data.cpy to generate an extended Header at sort_data.cpy .
Repeat steps 2, 3, and 4 until extended Headers for all required measurement modes are generated (at different names, e.g. sort_data.cpy, cal_data.cpy, raw_data.cpy)
Finally create a crontab file as indicated below, name e.g. cron_script and install it with the command '> crontab cron_script'. You should not name the crontab file cron_hawaii as mkcron will re-install it.

0,10,20,30,40,50,0 0,1 * * * /home/wera/weractrl/stm /home/wera/weractrl/sort_data.cpy /home/wera/weractrl/cron_script s > /home/wera/weractrl/cron_script.log
10,20,30,40,50 2 * * * /home/wera/weractrl/stm /home/wera/weractrl/sort_data.cpy /home/wera/weractrl/cron_script s > /home/wera/weractrl/cron_script.log
0,10,20,30,40,50,0 3,4 * * * /home/wera/weractrl/stm /home/wera/weractrl/sort_data.cpy /home/wera/weractrl/cron_script s > /home/wera/weractrl/cron_script.log
10,20,30,40,50 5 * * * /home/wera/weractrl/stm /home/wera/weractrl/sort_data.cpy /home/wera/weractrl/cron_script s > /home/wera/weractrl/cron_script.log
0,10,20,30,40,50,0 6,7 * * * /home/wera/weractrl/stm /home/wera/weractrl/sort_data.cpy /home/wera/weractrl/cron_script s > /home/wera/weractrl/cron_script.log
10,20,30,40,50 8 * * * /home/wera/weractrl/stm /home/wera/weractrl/sort_data.cpy /home/wera/weractrl/cron_script s > /home/wera/weractrl/cron_script.log
0,10,20,30,40,50,0 9,10 * * * /home/wera/weractrl/stm /home/wera/weractrl/sort_data.cpy /home/wera/weractrl/cron_script s > /home/wera/weractrl/cron_script.log
10,20,30,40,50 11 * * * /home/wera/weractrl/stm /home/wera/weractrl/sort_data.cpy /home/wera/weractrl/cron_script s > /home/wera/weractrl/cron_script.log
0,10,20,30,40,50,0 12,13 * * * /home/wera/weractrl/stm /home/wera/weractrl/sort_data.cpy /home/wera/weractrl/cron_script s > /home/wera/weractrl/cron_script.log
10,20,30,40,50 14 * * * /home/wera/weractrl/stm /home/wera/weractrl/sort_data.cpy /home/wera/weractrl/cron_script s > /home/wera/weractrl/cron_script.log
0,10,20,30,40,50,0 15,16 * * * /home/wera/weractrl/stm /home/wera/weractrl/sort_data.cpy /home/wera/weractrl/cron_script s > /home/wera/weractrl/cron_script.log
10,20,30,40,50 17 * * * /home/wera/weractrl/stm /home/wera/weractrl/sort_data.cpy /home/wera/weractrl/cron_script s > /home/wera/weractrl/cron_script.log
0,10,20,30,40,50,0 18,19 * * * /home/wera/weractrl/stm /home/wera/weractrl/sort_data.cpy /home/wera/weractrl/cron_script s > /home/wera/weractrl/cron_script.log
10,20,30,40,50 20 * * * /home/wera/weractrl/stm /home/wera/weractrl/sort_data.cpy /home/wera/weractrl/cron_script s > /home/wera/weractrl/cron_script.log
0,10,20,30,40,50,0 21,22 * * * /home/wera/weractrl/stm /home/wera/weractrl/sort_data.cpy /home/wera/weractrl/cron_script s > /home/wera/weractrl/cron_script.log
10,20,30,40,50 23 * * * /home/wera/weractrl/stm /home/wera/weractrl/sort_data.cpy /home/wera/weractrl/cron_script s > /home/wera/weractrl/cron_script.log
0 2,5,8,11,14,17,20,23 * * * /home/wera/weractrl/stm /home/wera/weractrl/cal_data.cpy /home/wera/weractrl/cron_script s > /home/wera/weractrl/cron_script.log

The above example schedules normal radar runs every 10 minutes and switches to one calibration cycle at the beginning of every 3 hours. Note, that with this manually installed crontab file, the WeraDesk Status page will only show the left side of the status line correctly. The right side will continue to show 'Disabled' (because you did not start the crontab through WeraDesk) and the rest of the fields will show the last measurement mode you configured. Do not start any measurements from WeraDesk until you remove the crontab file again ('> crontab -r') or ensure that the measurement started from WeraDesk does not overlap with the timeslots defined by crontab.

You can also edit /home/wera/etc/WeraDesk.tmp manually (look at the instructions) and run /home/wera/public_html/cgi-bin/Proc_WeraDesk on that modified file.

Another (more complicated) possibility is to write a program, that creates the extended Header data structure at /home/wera/weradesk/ctrl_data.cpy and calls mkcron afterwards.

BACK

Comments to: gurgel@ifm.uni-hamburg.de (Klaus-Werner Gurgel)