[lsst-dm-stack-users] Possible Summer 2013 bug report

[Chris Walter]

Dear Robyn and Paul,

Thank you for your answer.  Yes, that explains it.  I can confirm that if I use the v6_2 of the stack demo it works.  I will try to build the newer version from source.  

BTW, I have a small suggestion for the demo script.  I looked carefully at the output between detected-sources.txt and detected-sources.txt.expected. They agree in the first significant digits but there are disagreements in the last ones for many entries.  Of course this isn't surprising but it might be a good idea to print them with a fixed width.  As it is, a 'diff' or 'sdiff' reports differences on most lines and the lines are long enough that it isn't so easy to understand how they are different.  This might mislead people to think that the results are incorrect.

-Chris

On Aug 5, 2013, at 11:15 AM, Robyn Allsman <robyn.allsman at gmail.com> wrote:

> Hello Chris,
> 
> It looks as though the binary distribution release (May 17== v6_2) is out of sync with the source distribution release (June 20 == v7_2) mentioned in the Installing/Summer2013 document. The demo you extracted from source is matched to a later version of  the source stack (it was updated due to a schema change in the v7_2 Release).
> 
> In order to re-sync  the demo code with your binary release,  follow the instructions in:
>        https://dev.lsstcorp.org/trac/wiki/Installing/Winter2013#RunningaDemo
> It's  just a matter of changing the Release version from v7_2 to v6_2.
> 
> If you immediately want to locally use a v7_2 release, you need to install the full source distribution as described in the
> InstallingSummer2013 document.
> 
> Thank you for exposing this problem. This is both a documentation and a usability failure which will get fixed.  Until a new set of binaries is built, I will annotate the Installing/Summer2012 document to reflect reality.
> 
> I have opened Ticket  2982 on this issue requesting the generation of a set of binaries for v7_2.  
> 
> Robyn
> 
> 
> On Sun, Aug 4, 2013 at 12:33 PM, Chris Walter <chris.walter at duke.edu> wrote:
> Dear All,
> 
> I am a DESC member trying to get started with the DM stack.  I'm using a Scientific Linux 6.4 system.
> 
> I installed the Summer2013 binary release and am trying to run the lsst_dm_stack_demo-7.2 to verify it works properly.  It is crashing in the last step.  I determined the problem is actually in running the export-results script (processCcdSdss.py is running without error).
> 
> I did a 'lsst-distrib update' to make sure I had the latest version.  Running the export-result script alone you can see the following output I have included in this message.
> 
> I hope this is helpful.
> 
> -Chris
> 
> Chris Walter
> Duke University
> 
> ================================================================================
> 
> login1:lsst_dm_stack_demo-7.2.0.0 $ ./bin/export-results output > ! detected-sources.txt
> CameraMapper: Loading registry registry from output/_parent/registry.sqlite3
> Traceback (most recent call last):
>   File "./bin/export-results", line 71, in <module>
>     v = srcs.get(col)
>   File "/var/phy/project/lsst/Summer_2013/Linux64/afw/6.2.1.0+2/python/lsst/afw/table/tableLib.py", line 6993, in get
>     return self[k]
>   File "/var/phy/project/lsst/Summer_2013/Linux64/afw/6.2.1.0+2/python/lsst/afw/table/tableLib.py", line 6927, in __getitem__
>     return self.columns[k]
>   File "/var/phy/project/lsst/Summer_2013/Linux64/afw/6.2.1.0+2/python/lsst/afw/table/tableLib.py", line 2229, in __getitem__
>     return self[self.schema.find(args[0]).key]
>   File "/var/phy/project/lsst/Summer_2013/Linux64/afw/6.2.1.0+2/python/lsst/afw/table/tableLib.py", line 790, in find
>     raise KeyError("Field '%s' not found in Schema." % k)
> KeyError: "Field 'correctfluxes.apcorr' not found in Schema."
> 
> 
> 
> 
> _______________________________________________
> lsst-dm-stack-users mailing list
> lsst-dm-stack-users at lsstcorp.org
> http://listserv.lsstcorp.org/mailman/listinfo/lsst-dm-stack-users
>