Changes between Version 1 and Version 2 of ShiftSummary


Ignore:
Timestamp:
03/12/16 14:34:21 (9 years ago)
Author:
Daniela Dorner
Comment:

added tools that I know of and wishlist that came spontaneously to my mind

Legend:

Unmodified
Added
Removed
Modified

  • ShiftSummary

    v1 v2  
    1 Lets collect here tow lists:
     1Lets collect here two lists:
    22
    3  * tools (be it needed or already written) useful for a shift summary.
    4  * things you want to see in a shift summary.
     3== tools (be it needed or already written) useful for a shift summary.
    54
    6 ---
     5* occurrence and frequency of fad-losses (maybe even statistics on boards/fads?)
     6* occurrence of 27s problem
     7* lidar visible in data?
     8* some tools recently done by Thomas:
     9 * http://www.fact-project.org/run_db/test6.php
     10 * http://www.fact-project.org/run_db/test.php
     11 * http://www.fact-project.org/run_db/test2.php
     12 * http://www.fact-project.org/run_db/test4.php
     13 * http://www.fact-project.org/run_db/test5.php
     14* https://www.fact-project.org/dch/quality.php
     15* https://www.fact-project.org/dch/ratescans.php
     16* tool that evaluates how often which limits are reached (maybe not needed for shift summary, but I think useful for this whole automation business)
     17* tool for data check (could be also used for defining limits) https://fact-project.org/datacheck/dch.php
     18* https://www.fact-project.org/sandbox/AllSkyCloudDetection/
     19* ...
     20
     21== things you want to see in a shift summary.
     22
     23* weather during the night? which runs affected by clouds? calima? haze? humidity?
     24* any rate problems during the night? too high rate? too low rate? / is rate as expected? (correlation with zd and nsb needed)
     25* any lidar problem?
     26* were there runs during which the lid was closed but was not supposed to
     27* any problems during QLA processing?
     28* occurrence of 27s problem?
     29* possible car flashes?
     30* not about content directly but about concept of display: I want to have an overview on one glance showing for each system/item fine/not-fine or green/red and then clicking on it gives me more details (maybe even displaying only things that went wrong is enough)
     31* were data taken as planned? if not what were the reasons?
     32* ...
     33
     34== other stuff important / needed / useful to go for robotic operation
     35
     36I know, it is not exactly the right place, but as these points just came to my mind and we discussed few others yesterday, I put it here - we can move it somewhere else later
     37
     38* orbit mode (helpful for automatic scheduling to improve homogeneity in data)
     39* automatic scheduling of ratescan (avoid copy&paste errors of shifters)
     40* redundancy in shifter-calling program