Date: Sat, 14 Feb 2009 22:18:15 -1000 From: Bill Golisch To: Tony Denault Cc: operators Subject: [Fwd: Re: cross-quarter tcs3 change requests] Hi Tony, I just noticed that these requests do not appear on your tcs3 home page. what is the current status of these requests from November? Bill -------- Original Message -------- Subject: Re: cross-quarter tcs3 change requests Date: Sat, 01 Nov 2008 03:48:21 -1000 From: Bill Golisch Reply-To: Tony Denault To: operators , Alan Tokunaga References: <48F1C8E1.2090102@duke> <48F43C8A.30402@duke> <4909623B.1070608@duke> <49096298.5060201@duke> TCS3 Change Request Form ==================================================================== Date: 10/31/08 Requestor: golisch (approved by griep, sears) ---------------------------------------------------------------------- 1. Description of problem: (ITEM #1) t3remote shutter vignette countdown only works when lower shutter is down. 2. Requested change: also need it when lower shutter is up and telescope is near 1.125 or 4 airmass. 3. Priority: high 4. Response: Fixed in v090219. ---------------------------------------------------------------------- 1. Description of problem: (ITEM #2) t3remote BeamOS paddle is awkward to use especially for large values. multiple paddles (offset/Base, offset/UserOS, offset/BeamOS, ptmap) are confusing and a source of error if the wrong paddle is used . 2. Requested change: replace BeamOS paddle with thumbwheels +XXX.X +XXX.X like next object ns.rate (keeping User OS paddle). this would let us set up a new beamswitch in advance and hit send later like old thumbwheels. 3. Priority: medium 4. Response: Previous communication indicate that this type of widget not desire as observers can set beam offset ( Strong objection from 1 TO, I think this would be OK). GUI changes not clearly specified. .. Further discussion needed. BeamOS can be replace with 2 spin button and a "Set BeamOS" button? Or are you asking for another tab? ---------------------------------------------------------------------- 1. Description of problem: (ITEM #3) mcc1 command line slew requires much more typing than old tcs command. 2. Requested change: add short command line slew request i.e. 123456.78 -3456.7 S 3. Priority: medium 4. Response: Your example has dec "-3456.7", is that -34:56:00.7 or -00:34:56.7, or a typo? adding a shorter version of next, ie "n 123456.78 -123456.7". Will default to FK5 J2000 (or ICRT). Otherwise use t3remote's next tab. What is "123.4"? What is "1234" ? What is "123456789.9"? Need to talk about the rule that the number follow. ---------------------------------------------------------------------- 1. Description of problem: (ITEM #4) t3remote ptmap spiral does not work if mcc1 "JoySt=spiral" is set 2. Requested change: t3remote should ignore mcc1 joystick setting. Remote observers need to be able to change rate and width on t3remote spiral. 3. Priority: medium 4. Response: Test march 3,2008 in lab; Everything looks ok to me (tony). ---------------------------------------------------------------------- 1. Description of problem: (ITEM #5) all track rate values are not shown on mcc1 . 2. Requested change: show TOTAL track rate, default sidereal rate, non-sidereal rate, pointing rate Hide never-used scan rate, time, duration to make room (maybe on mcc pointing window) 3. Priority: medium 4. Response: Scan rate are part of the Offset type, need to stay on MCC. This scan option was added per request of the TO so don't call it "never-used". Proper motion could be removed ( as it is added in to get the Mean RA & DEC). Then there is the non-sidereal rate which is in the celestial coordinate system, and the pt.rate with in the observed coordinates system... shouldn't add those 2 together. ---------------------------------------------------------------------- 1. Description of problem: (ITEM #6) some ephemerides only give an hour angle rate -15.1234 instead of a separate non-sidereal RA rate -0.0823 = 15.0411-15.1234 2. Requested change: we need to be able to enter HA rate in addition to non-sidereal rate. we already have one set of thumbwheels on mcc1 for the rates ,and 2 buttons to select which rates: ns.rate or pt.rate. we just need one other button to use the thumbwheel values for HA rate. 3. Priority: medium 4. Response: Sorry, Do the math and find the 'nonsidereal rate'. Hour angle rates should be caculated.. is the Geocentric Apparent? Topocentric? Refraction or Not? ---------------------------------------------------------------------- 1. Description of problem: (ITEM #7) t3display constantly highlights "Beamswitch A" in green or "Beamswitch B" in yellow. 2. Requested change: not needed since A or B label and shading of arcsecond values already indicates state. if a third redundant indication is needed just highlight single letter A or B like on mcc1 servo mode track window. 3. Priority: low 4. Response: I like it... sorry. ---------------------------------------------------------------------- 1. Description of problem: (ITEM #8) t3display uses a slightly fainter font for Epoch/CS ... line and Proper Motion ... line. 2. Requested change: use same font throughout. 3. Priority: low 4. Response: The black only has 2 fonts and differ by size; Maybe this is a Monitor issue? ---------------------------------------------------------------------- 1. Description of problem: (ITEM #9) t3display CS "fk5" label is confusing since it appears right next to a object's coordinates even though object may not be a star from the fk5 catalog in starcat. 2. Requested change: just show epoch (i.e. "2000") not CS to agree with common practice and avoid confusion. 3. Priority: low 4. Response: CS of FK5 means the RA and Dec is in the FK5 Celestial Reference frame, not what catalog it came from. CS mean Coordinate System. ----------------------------------------------------------------------