Meeting goals 1- react on comments on memo 293 comment list available, not complete yet. telecon review is on thursday may 4 2- settle some important questions, see email by Steve Scott (mainly real-time control and data acquisition, pipeline) 3- move towards more detailed requirement lists, to be formalized into use cases (start 3rd week of may in Garching) ------------------------------------------------------------------------------- Comments to memo 293 -------------------- - received from 70% of reviewers - numbered list ordered by relevant sections and page numbers (some dummy comment numbers) - I understand I need to reply to all before Thursday ... - General comments: . not yet enough detailed . lack global view, consistency . clarify what is needed and what is wanted or desired (priorities) . dynamic scheduling should be the default . sub-arrays not clearly defined and their operation clearly described - Real time: . should be OO . no time specific scripts prior to scheduling . allow for survey work (no GUI for these ?) - Proposal submission . only one electronic form for ph 1 . simulator basic for ph 2 - Dyn. Scheduling . fast scientific feed back from pipeline questioned - Operator Interface (mostly operational questions) --------------------------------------------------------------------------- --------------------------------------------------------------------------- some terminology: ----------------- - dump: basic integration time of correlator - Integration: basic written unit ; nothing changes except phase switching and tracking - observation/subscan: a set of integrations while the antennas follow an elemental pattern across the source + frequency switch, nutator switch ? - scan: a set of observations with a common goal: e.g. pointing scan, focus scan, atmospheric amplitude calibration scan, ... - observation block: a set of scans constituting an uninterruptible scheduling unit ? - observing session: a set of observation blocks constituting an uninterrupted scheduling unit, in the same project. - table: the hierarchical set of parameters that define the current observation: . source name , coordinates . pointing constants . pattern . correlator setup . LO frequencies . switching description . data reduction to be done for each observation ... - interactive commands can be used to specify table parameters for the next observation, start the next observation, cancel the current observation, ... - an observing script is used to define the sequence of observations, with loops, conditional tests using environmental parameters (weather, pipeline results, current scheduling status, ...) - a gui interface is used to prepare a script from a template, with astronomer input (fixed table parameters, range of values for table parameters, algorithms used for variable parameters, ...) - or the gui does it directly without the script (TBD), but anyway is able to produce a script. ------------------------------------------------------------------------------- Sub-arrays: - three levels in hardware: o system sub-arrays: independently controlled LO's (4 maximum) o correlator sub-arrays: independent setup modes, integration times (16 max) o antenna sub-arrays: independent pointing directions - does it make sense to have all three levels available in software ? Probably yes, e.g. baseline meas. (100GHz) / ALMA \ single dish (nut.sub.) \ / project A (340GHz) \ scanning antennas interf. poin / \ pointed antennas Need to refine terminology ? ------------------------------------------------------------------------------- Use Cases for Script commands ? 1-Define Antennas . All Available . All with given Features (Config, Receiver X Available, ... . Number of Antennas . Antenna List 2-Set Pointing Model Parameters Parameters are : zeros for encoders, collimations, inclinations of axes, refraction constant, ... Some may be read either automatically from hardware or manually set (like inclinations from inclinometers, refreaction from weather data ...) Some may be set from the pipeline (collimations). For these we do it explicitely here (`value' being obtained from a distributed variable). . Set parameter to value . Set parameter to auto mode (read from hardware or compute from hardware readings) . Get parameters from data base . Save parameter in data base (??) 3- Preset Antenna Position . ID (fetch from catalog) . EQUATORIAL ECLIPTIC GALACTIC EQUATORIAL_OF_DATE HORIZONTAL (restrict) . epoch . $\lambda$ . $\beta$ . $\lambda'$ (proper motion at epoch) . $\beta'$ . velocity . reference system For sol.sys. objects: give geocentric (E-M barycentric ?) coords, and rate of changes valid for a period of time (that is , already interpolated). needed: list and description of effects to be included in calculation 4- Define Tracking Pattern Give an arc of circle or a sequence of them. . system . start coordinates 0 r . angular velocity 2*pi*r/t . direction pi/2 . direction derivative 2*pi/t . duration t Is this enough ? (OK for spiral and circles at constant velocity) 5- Define Frequency Setup Many crosschecks needed here ... . frequency LO1 . frequency LO2 4 values . number of subbands n{1-8} . sideband of subband i {USB, LSB} . frequency width of subband i {2, 1, 0.5, 0.25} . polarization products of subband i {4, 2, XX, YY} . number of channels of subband i {64-max} max number of channels depend on above info. 6- Define Integration . time . switching mode .. 7- Define Processing . script to execute 8- Start observation 9- Abort observation 10 -Exit Session -------------------------------------------------------------------------------