wiki:DatatakingLimits

Version 8 (modified by dneise, 9 years ago) ( diff )

adding content (without modification) from logbook and DataTakingMainPage

Back to DataTakingMainPage

Datataking Limits

These are instructions copied here from the DataTakingMainPage (Section DataTaking third point)

  • Monitor the system and in special the currents
    • limits for the currents are defined in the DatatakingLimits
    • if the limits for the currents are exceeded you have to stop datataking:
    • stop the script (dimctrl --stop from a bash)
    • stop Trigger (MCP/STOP or FTM_CONTROL/STOP_TRIGGER
    • ramp down the voltage (BIAS_CONTROL/SET_ZERO_VOLTAGE)
    • close open files (FAD_CONTROL/CLOSE_OPEN_FILES)
    • adapt your schedule (edit ~/operation/scripts/schedule.js) and update the schedule (dimctrl --quit --cmd ".js scripts/updateSchedule.js") Note, that only entries which are schedules for *now* or the future are transferred to the database. All previous entries stay like they are.
    • you can write also your own schedule file and transfer its content to the database by given the filepath to the command: (dimctrl --quit --cmd ".js scripts/updateSchedule.js file=<!pathToScheduleFile>")
  • Be aware of all other DatatakingLimits

These are the Datataking Limits from our myBB logbook The original text said:

when you reach the Datataking Limits stop datataking!

Limits for running the System

value max action additional information
Currents
median current per pixel in camera: 90 uA stop script, ramp down voltage displayed in smartfact (mainpage, line 'GAPD')
maximum current in a single pixel: 110 uA stop script, ramp down voltage the crazy pixels are excluded from this limit
Temperature
temperature difference: 7° C monitor the temperatures carefully _difference between sensor compartment and outside temperature_
temperature difference: 15° C stop data taking _difference between sensor compartment and outside temperature_
temperature in container : 40° C do not observe when the temperature in the container is above 40 deg
Drive system
Zenith angle: ~75° data with higher zenith do not make much sense
Zenith angle: ~88° stop data taking on this source, look for a source with smaller zd
Wind
Wind speed exceeds 50km/h significantly or in regular intervals bring telescope to parking position and wait for better wind situations
Weather
Clouds no stars visible in allsky camera in pointing direction stop datataking, you may continue tracking the source or observe another source in case stars are visible in that direction
Rain it is raining stop script, close camera we need rain sensor to identify rain clearly
clouded mirrors/water on mirrors or light pulser do not observe, wait until water is gone you may check with IR camera
Humidity - check general weather condition, especially if it is raining high humidity (there is a warning at 98%) alone is not a reason to stop

This was the original content of this page, before additional contant was added.

  • switch off voltage
    • BIAS_CONTROL/SET_ZERO_VOLTAGE
  • wait a few minutes, so that the camera can cool down
  • track another region and try again datataking (you can first test which currents you will get, by following steps):
    • FEEDBACK/START_CURRENT_CONTROL 0.0
    • BIAS_CONTROL/SET_GLOBAL_DAC 1
    • this will ramp up the voltage, so that you can check the currents
  • if it is raining
    • switch off voltage
    • close lid
    • park telescope
Note: See TracWiki for help on using the wiki.