Test Measurements with Closed Lid

Since 17.2.2015, there is a new measurement type available to facilitate the measurements with closed lid. This new type can be scheduled normally via ​https://www.fact-project.org/schedule/ or schedule.js

Name of task: CUSTOM
Options to be provided: zd, az, biason, time, threshold

Example for schedule.js:

 { date:"2015-02-17 22:30 UTC", measurements:
     [
      { task:'custom', zd:101, az:0, time:3600, threshold:600, biason:false}
     ]
 },

Example for website:

Remark: be aware that the scheduling website so far doesn't check the options for consistency

To stop such a measurement:

• update schedule with new measurement you want to do
• send MCP/STOP

Test Measurements with Closed Lid [Old Documentation]

as I was asked already several times how to do these measurements, I put here some information on how to do it

goal of such measurements

record events with closed lid to study what type of events occur in that case

bias on or off

the bias might be switched on or off for these measurements

bias on: probably muon events (they look different depending on the zd, also the rate changes)
bias off: only electronics noise triggering

settings you probably want to change in this test

• sky position (different zd)
• bias on/off
• threshold
• number of events

how to do such a measurement

sky position

in case you want to do it not in park position:

in drivectrl:
MOVE_TO <zd> <az>
(you just need to position the telescope, tracking is not needed)
in case you want to go to zenith, I recommend something like 2° as directly zenith might be difficult for a real telescope ;)

lid

make sure that the lid is closed

bias [only needed for measurements with bias voltage]

in case feedback is not yet calibrated:
in feedback:
CALIBRATE
wait until it is calibrated

in feedback
START 1.1

in biasctrl
SET_GLOBAL_DAC 1
the feedback system should now ramp the voltage automatically to the needed values

configure run

in mcp:
START <timemax> <nummax> <runtype>
e.g. MCP/START -1 100 custom (will take a run of 100 events; run type custom is needed here; with runtype data it seemed not to work)

set trigger settings

in dimctrl:
RATE_CONTROL/STOP

in ftmctrl:
STOP_TRIGGER
ENABLE_TRIGGER yes
SET_TIME_MARKER_DELAY 123
SET_THRESHOLD -1 <threshold>
e.g. SET_THRESHOLD -1 400 (setting the threshold to 400 DAC counts
START_TRIGGER

in fadctrl:
wait until run is finished and file is closed

you may look at the events after few minutes (when it's transferred from newdaq to daq) on ​https://www.fact-project.org/viewer/

stop a measurement

in case you want to abort a measurement, eg when the weather improves:

in ftmctrl:
STOP_TRIGGER

in mcp
STOP

in fadctrl:
CLOSE_OPEN_FILES