Contents<\/p>
- 1<\/span> jcmtObs Gui<\/a><\/li>
- 2<\/span> JCMT Observation Console<\/a><\/li>
- 3<\/span> Queue Monitor<\/a><\/li>
- 4<\/span> OMP Obslog<\/a><\/li>
- 5<\/span> Telescope Status<\/a><\/li>
- 6<\/span> JCMT Enviromon<\/a><\/li>
- 7<\/span> JCMT Query Tool<\/a><\/li><\/ul><\/div>\n\n
jcmtObs Gui<\/span><\/h3>\n
(Command line: “jcmtObs”)<\/em><\/p>\n
‘Observer up’ launches the observing software. From this gui you should then go ahead and run ‘observer up’ from the observer station. ‘Observer up’ can also be launched from a terminal with:
\n% observer_up<\/p>\nIf there is more than one observer at the telescope, only one of them should run observer_up.<\/p>\n
![\"jcmtObs](\"http:\/\/www.eaobservatory.org\/jcmt\/wp-content\/uploads\/sites\/2\/2015\/03\/jcmtObs.png\")
<\/a>At the end of the night the software should be run down with the ‘observer down’ button and<\/i> by clicking the ‘exit’ button.<\/p>\nJCMT Observation Console<\/span><\/h3>\n
Two of these windows will appear – one each for SCUBA-2 and ACSIS. These display the progress and summary of the observation currently being executed.<\/p>\n
![\"observer-up1\"](\"http:\/\/www.eaobservatory.org\/jcmt\/wp-content\/uploads\/sites\/2\/2015\/03\/observer-up1.png\")
<\/a><\/p>\nQueue Monitor<\/span><\/h3>\n
The queue monitor shows what has been sent to the queue. This lists the observations in the order they have been sent and reports their duration.<\/p>\n
![\"observer-up2\"](\"http:\/\/www.eaobservatory.org\/jcmt\/wp-content\/uploads\/sites\/2\/2015\/03\/observer-up2.png\")
<\/a><\/p>\nOMP Obslog<\/span><\/h3>\n
(Command line: “ompobslog”)<\/em><\/p>\n
You will be prompted for you OMP User ID. This should be pre-registered with the JAC. If you do not have one, contact your support astronomer.<\/p>\n
![\"observer-up3\"](\"http:\/\/www.eaobservatory.org\/jcmt\/wp-content\/uploads\/sites\/2\/2015\/03\/observer-up3.png\")
<\/a><\/p>\nThe Obslog screen will then appear. This is a summary of all the observations for a given night. Observations appear in the this list once they have been processed by the summit pipeline; for large maps this can sometimes lead to a delay between the end of observation and its appearance in this list.<\/p>\n
![\"observer-up4\"](\"http:\/\/www.eaobservatory.org\/jcmt\/wp-content\/uploads\/sites\/2\/2015\/03\/observer-up4.png\")
<\/a><\/p>\nYou can attach a comment to a particular observation by double clicking on it. The following screen will appear. This should be used to highlight anything of note for that observation (e.g. dramatic weather change, fault, look strange in the summit reduction). Never select the ‘bad’, ‘junk’ or ‘rejected’ options, these are used by JAC staff retroactively.<\/p>\n
![\"observer-up5\"](\"http:\/\/www.eaobservatory.org\/jcmt\/wp-content\/uploads\/sites\/2\/2015\/03\/observer-up5.png\")
<\/a><\/p>\nTelescope Status<\/span><\/h3>\n
This window gives a summary of the parameters associated with the telescope. You can see the times and coordinates continually changing as the telescope tracks a source.<\/p>\n
![\"observer-up6\"](\"http:\/\/www.eaobservatory.org\/jcmt\/wp-content\/uploads\/sites\/2\/2015\/03\/observer-up6.png\")
<\/a><\/p>\nNote: PAZ and PEL are the difference between the demanded and the actual azimuth and elevation. the telescope has trouble following the SCUBA-2 scan patterns at high elevations so you may see intermittent large values. If the telescope is stuck it will display ongoing high values.<\/p>\n
<\/p>\n
If this window for some reason does not come up please inform the TSS and you can restart by running tcsmon in any terminal (not in sc2dr5)<\/p>\n
% tcsmon<\/pre>\n
JCMT Enviromon<\/span><\/h3>\n
(Command line: “enviromon”)<\/em><\/p>\n
This small window gives a summary of the current environmental conditions. It reports both the CSO opacity and the JCMT WVM (Water Vapour Monitor radiometer) opacity. These are usually in good agreement but occasional problems with one or the other will lead to a discrepancy. Your TSS will know which number is more reliable on a given night. Historically, the CSO tau is used to define the weather bands at the JCMT.<\/p>\n
![\"observer-up7\"](\"http:\/\/www.eaobservatory.org\/jcmt\/wp-content\/uploads\/sites\/2\/2015\/03\/observer-up7.png\")
<\/a><\/p>\nJCMT Query Tool<\/span><\/h3>\n
(Command line: “jcmtqt -scenario”)<\/em><\/p>\n
The query tool is used to control flexible observing. the opacity and time are automatically updated; you then enter your country, instrument(s) and semester then run a search. This will return all active projects that are available now that match the current constraints. Available projects will be listed in order of priority. The far-left column shows the project priority as set by the TAG, while internal priorities within a given project may have been set in the MSBs. Otherwise it will list them in order of source availability.<\/p>\n
Any of the fields can be altered (or input) and the search refreshed. This is includes the time and opacity which can be changed to anticipate changing sky conditions later in the night. To return to the default values click the grey ‘Set Default’ box – this will however retain the country, instrument and semester selections.<\/p>\n
Note: if you hover your mouse pointer over the tau value it will tell you the source of the measurement (WVM or CSO).<\/p>\n
![\"\"](\"https:\/\/www.eaobservatory.org\/jcmt\/wp-content\/uploads\/sites\/2\/2018\/02\/observer_up8.png\")
<\/a><\/p>\nMenu options allow the user to edit the columns that are displayed at the bottom of the window. Under the ‘View’ menu you can select ‘Columns’ and deselect any that you do not wish to appear.<\/p>\n
The example below illustrates editing the ‘Constraints’ options. This should be used for reference only, your TSS will know when it is suitable to remove any of these constraints.<\/p>\n
Note that the search button will flash amber as a warning if some (but not all) constraints are disabled. It will flash red if all constraints are disabled.<\/p>\n
![\"\"](\"https:\/\/www.eaobservatory.org\/jcmt\/wp-content\/uploads\/sites\/2\/2018\/02\/observer_up9.png\")
<\/a><\/p>\nYou can view details of an MSB with the ‘Fetch MSB’ button.
\n1. Highlight the MSB you want to display.
\n2. Click the ‘Fetch MSB’ button.
\n3. The MSB information will open in a new tab.<\/p>\n![\"\"](\"https:\/\/www.eaobservatory.org\/jcmt\/wp-content\/uploads\/sites\/2\/2018\/02\/observer_up10.png\")
<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"To run up the observer software you will select ‘observer up’ button from the ‘jcmtObs’ window. This window can be brought up by clicking the icon on your desktop or launched from a terminal with: % jcmtObs jcmtObs Gui (Command line: “jcmtObs”) ‘Observer up’ launches the observing software. From this\u2026 Continue reading<\/a><\/p>\n","protected":false},"author":5,"featured_media":0,"parent":106,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":[],"_links":{"self":[{"href":"https:\/\/www.eaobservatory.org\/jcmt\/wp-json\/wp\/v2\/pages\/2394"}],"collection":[{"href":"https:\/\/www.eaobservatory.org\/jcmt\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/www.eaobservatory.org\/jcmt\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/www.eaobservatory.org\/jcmt\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/www.eaobservatory.org\/jcmt\/wp-json\/wp\/v2\/comments?post=2394"}],"version-history":[{"count":23,"href":"https:\/\/www.eaobservatory.org\/jcmt\/wp-json\/wp\/v2\/pages\/2394\/revisions"}],"predecessor-version":[{"id":10035,"href":"https:\/\/www.eaobservatory.org\/jcmt\/wp-json\/wp\/v2\/pages\/2394\/revisions\/10035"}],"up":[{"embeddable":true,"href":"https:\/\/www.eaobservatory.org\/jcmt\/wp-json\/wp\/v2\/pages\/106"}],"wp:attachment":[{"href":"https:\/\/www.eaobservatory.org\/jcmt\/wp-json\/wp\/v2\/media?parent=2394"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
- 2<\/span> JCMT Observation Console<\/a><\/li>