From: kaike pan
Subject: Re: [SDSS3-infrastructure 1889] Re: 2.5m obslog 20091104 (MJD 55140)
Date: Thu, 5 Nov 2009 14:54:17 -0700
Yes, right now. There are so many info scrolls by the log window.
Some times, it is hard to
catch all info. I second Steph's point, it would be much nicer if we
can have the info in a
static place in the GUI. I guess for loadCartridge command, the info
we need is:
plateid, cartridgeID, coordinates of the field, and which fibers are
automatically enabled
Show only true ones are enough (assumed all other fibers are
disabled), like:
gprobes="(2=True)","(4=True)","(6=True)",,"(8=true)","(10=true)"
  -kaike
On Nov 5, 2009, at 12:32 PM, stephanie snedden wrote:
> I think the problem is that the info scrolls by so fast that some
> people never really realized it was there. Once this info is in a
> static place in the GUI, life will be better.
>
> Steph
> On Nov 5, 2009, at 12:18 PM, paul harding wrote:
>
>> Kaike,
>> The guider loadCartridge command has always shown the enabled fibers.
>> I would include the example of what is reported in the log window but
>> platedb appears not to be working at present.
>>
>> 19:16:32 8 guider loadCartridge cartridge=4
>> 19:16:32 .sop 0 sop d text="boss alive"
>> 19:16:32 .hub 0 cmds d CmdIn="APO.harding","guider","loadCartridge
>> cartridge=4"
>> 19:16:32 .hub 0 cmds d
>> CmdQueued=311133,1257448626.31,"APO.harding",8,"guider",
>> 35,"loadCartridge cartridge=4"
>> 19:16:32 .hub 0 cmds d
>> CmdIn="APO.harding.guider","platedb","loadCartridge cartridge=4
>> pointing=A"
>> 19:16:32 .hub 0 cmds d
>> CmdQueued=311134,1257448626.38,"APO.harding.guider",640,"platedb",
>> 541,"loadCartridge cartridge=4 pointing=A"
>> 19:16:32 APO.harding.guider 640 platedb f text="command failed:
>> InvalidRequestError(\"Can't reconnect until invalid transaction is
>> rolled back\",) at /home/sdss3/products/Linux64/sqlalchemy/0.5.5/
>> lib/python/sqlalchemy/engine/base.py:576"
>> 19:16:32 .hub 0 cmds d CmdDone=311134
>> 19:16:32 APO.harding 8 guider f text="Failed to lookup plate
>> corresponding to 4/A"
>>
>> Paul
>>
>>
>> On Nov 5, 2009, at 12:22 PM, kaike pan wrote:
>>
>>> Hi Robert and Paul,
>>>
>>> Is it possible for loadingCartridge command to show which guiding
>>> fibers are
>>> enable? I think this will be useful to us (yes, guider status can
>>> give us
>>> the info. But we don't have to use the command for the info if
>>> loadingCartridge
>>> does so, because loadCartridge is a "must" step for an observation).
>>>
>>> -kaike
>>>
>>>
>>>
>>> On Nov 5, 2009, at 10:01 AM, paul harding wrote:
>>>
>>>> I think this is a case of history becoming precedent.
>>>>
>>>> In the past marvels plates were mostly designed with
>>>> pointing A with even guide fiber numbers
>>>> pointing B with odd guide fibers numbers
>>>>
>>>> While this was convenient  for the operators it was never meant
>>>> to be a rule.
>>>> There is no reason why any plate pointing could not have any
>>>> subset of guide fibers assigned.
>>>> The odd even assignment is not possible on preselection plates,
>>>> nor will it be possible when the
>>>> marvels cartridges are upgraded in the future with new guide
>>>> fibers.
>>>>
>>>> As RHL says  the guider loadCartridge command shows which guide
>>>> fibers are assigned to guide stars
>>>> for that pointing and thus enabled. Observers should note which
>>>> fibers are initially enabled when loading a cartridge.
>>>>
>>>> The guider status command shows the current state of enabled and
>>>> disabled fibers, it reflects the changes
>>>> applied by the operators with the enable and disable commands to
>>>> the original state when the cartridge was loaded.
>>>>
>>>> Fibers that are disabled when the cartridge is loaded should not
>>>> be enabled.
>>>>
>>>> Paul
>>>>
>>>>
>>>>
>>>> On Nov 5, 2009, at 11:09 AM, Robert Lupton the Good wrote:
>>>>
>>>>>> Another piece of info. According to plate design
>>>>>> team, that odd fibers for A pointing, even for B pointing
>>>>>> will not apply for newest designed plates.
>>>>>
>>>>> The code doesn't use Even/Odd, it looks in the plPlugMap file
>>>>> to see which guide fibres are in use.  At least, I think it
>>>>> does.  The loadCartridge command will report which fibres are
>>>>> enabled.
>>>>>
>>>>> 					R
>>>>>
>>>>>
>>>>> DSS DSS DSS DSS DSS  Digital Sky Survey DSS DSS DSS DSS DSS DSS
>>>>> DSS *** The information posted to SDSS mailing lists is
>>>>> proprietary ***
>>>>> DSS  This is message 4859 in the sdss-25mlog archive, URL
>>>>> DSS         http://www.astro.princeton.edu:81/sdss-25mlog/msg.
>>>>> 4859.html
>>>>> DSS  The index is at http://www.astro.princeton.edu:81/
>>>>> sdss-25mlog/INDEX.html
>>>>> DSS  To join/leave the list, go to
>>>>> DSS         http://www.astro.princeton.edu:81/cgi-bin/
>>>>> mailinglists.pl/show_subscription?list=sdss-25mlog
>>>>> DSS  To post a message, mail it to sdss-25mlog@astro.princeton.edu
>>>>> DSS
>>>>> DSS DSS DSS DSS DSS DSS DSS DSS DSS DSS DSS DSS DSS DSS DSS DSS
>>>>
>>
>> _______________________________________________
>> Message 1889 of sdss3-infrastructure -
>> sdss3-infrastructure@sdss3.org
>> https://sdss3.org/mailman/listinfo/sdss3-infrastructure
>
>