id
int64 0
5.38k
| issuekey
stringlengths 4
16
| created
stringlengths 19
19
| title
stringlengths 5
252
| description
stringlengths 1
1.39M
| storypoint
float64 0
100
|
|---|---|---|---|---|---|
1,099 |
DM-5568
|
03/18/2016 14:41:59
|
CCB review of LCR-603 (LSE-74)
|
Review LCR-603, "LSE-74 document revision"
| 2 |
1,100 |
DM-5580
|
03/21/2016 01:48:20
|
Docgen draft from EA content for LSE-140
|
Create a docgen from the LSE-140 content in Enterprise Architect.
| 2 |
1,101 |
DM-5582
|
03/21/2016 08:10:03
|
Support LCR-385
|
Support getting LCR-385 against LSE-78 through the CCB.
| 3 |
1,102 |
DM-5585
|
03/22/2016 08:52:17
|
SQuaRE Communication and Publication Platforms Document and Presentation - Clone
|
This is a clone of DM-5581 tracking [~frossie]'s SPs
| 5 |
1,103 |
DM-5586
|
03/22/2016 09:28:44
|
Fix obs_decam butler level
|
There is a bug in {{obs_decam/policy/DecamMapper.paf}}, causing some butler features for the "visit" level or above working incorrectly. The {{hdu}} key is irrelevant for the visit level or above, but wasn't included in the policy file. Because of this bug, the {{DemoTask}} in {{ctrl_pool}} (ctrlPoolDemo.py) runs incorrectly with DECam data. It incorrectly treats dataRef with different {{hdu}}s as they are from different visits, hence reads each ccd image multiple times (61 times for one visit with 61 hdu). Instead, each ccd image should be read once. Besides fixing the policy file, I also added an optional test that only runs if {{testdata_decam}} is set up. The part with level="visit" in the test fails without the ticket changes in the policy. (p.s. The raw data file in {{testdata_decam}} is modified and has only 2 hdus.)
| 3 |
1,104 |
DM-5590
|
03/22/2016 14:13:55
|
Fix afw build issues with recent clang
|
{{afw}} fails to build with recent versions of clang: {code} include/lsst/afw/image/MaskedImage.h:553:65: error: '_loc' is a protected member of 'lsst::afw::image::MaskedImage<unsigned short, unsigned short, float>::MaskedImageLocatorBase<boost::gil::memory_based_2d_locator<boost::gil::memory_based_step_iterator<boost::gil::pixel<unsigned short, boost::gil::layout<boost::mpl::vector1<boost::gil::gray_color_t>, boost::mpl::range_c<int, 0, 1> > > *> >, boost::gil::memory_based_2d_locator<boost::gil::memory_based_step_iterator<boost::gil::pixel<unsigned short, boost::gil::layout<boost::mpl::vector1<boost::gil::gray_color_t>, boost::mpl::range_c<int, 0, 1> > > *> >, boost::gil::memory_based_2d_locator<boost::gil::memory_based_step_iterator<boost::gil::pixel<float, boost::gil::layout<boost::mpl::vector1<boost::gil::gray_color_t>, boost::mpl::range_c<int, 0, 1> > > *> >, Reference>' const_VarianceLocator(iter._loc.template get<2>()) {code} and issues with statistics.i so far, more errors may turn up as these are cleared. These problems are apparent with {{Apple LLVM version 7.3.0 (clang-703.0.29)}} (as shipped with the latest release of XCode, hence this now becoming an issue) and {{clang version 3.8.0 (branches/release_38 262722)}} (a recent release from LLVM; note that Apple uses its own versioning scheme). {{clang version 3.7.1 (tags/RELEASE_371/final)}} is not affected.
| 1 |
1,105 |
DM-5591
|
03/22/2016 16:45:54
|
Archive in a box v1 (F16)
|
Several times we were asked a question about Firefly: Great software. How could I use it for my data now? This epic capture the preparation work in Firefly for its final version of "Archive in a box". The work is also needed to improve the user experience in using Firefly. 8/1/2017 Future related work will be captured in stories of epic DM-10853.
| 40 |
1,106 |
DM-5593
|
03/23/2016 12:55:36
|
fix issue where butler repository search returns list for single item
|
Backwards compatible behavior is that when butler returns a single item, it is NOT in a list. A recent change (when the Repository class was added) broke this behavior. Change it back so that if an operation in repository would return a list with a single item, it pulls it from the list. Note this is only related to the case where a repository's parentJoin field is set to 'outer' and since no one is using this yet (they should not be, anyway) then the point is moot.
| 1 |
1,107 |
DM-5594
|
03/23/2016 14:32:28
|
Fix qserv service timeout issue
|
After Qserv services have been running over ~couple of days, new queries fail and can also lead to a crash. Investigate and implement a solution.
| 5 |
1,108 |
DM-5595
|
03/23/2016 20:31:14
|
daf_persistence build failure on OSX
|
I see the following build failure in {{daf_persistence}} on OSX 10.11: {code} c++ -o python/lsst/daf/persistence/_persistenceLib.so -bundle -F/ -undefined suppress -flat_namespace -headerpad_max_install_names python/lsst/daf/persistence/persistenceLib_wrap.os -Llib -L/private/tmp/ssd/swinbank/shared_stack/DarwinX86/mariadbclient/10.1.11-2-gd04d8b7/lib -L/private/tmp/ssd/swinbank/shared_stack/DarwinX86/pex_policy/2016_01.0+4/lib -L/private/tmp/ssd/swinbank/shared_stack/DarwinX86/pex_logging/2016_01.0+4/lib -L/private/tmp/ssd/swinbank/shared_stack/DarwinX86/daf_base/2016_01.0+4/lib -L/private/tmp/ssd/swinbank/shared_stack/DarwinX86/utils/2016_01.0+4/lib -L/private/tmp/ssd/swinbank/shared_stack/DarwinX86/pex_exceptions/2016_01.0+3/lib -L/private/tmp/ssd/swinbank/shared_stack/DarwinX86/base/2016_01.0+3/lib -L/private/tmp/ssd/swinbank/shared_stack/DarwinX86/boost/1.59.lsst5/lib -L/tmp/ssd/swinbank/shared_stack/DarwinX86/miniconda2/3.19.0.lsst4/lib/python2.7/config -ldaf_persistence -lboost_serialization -lmysqlclient_r -lpex_policy -lpex_logging -lboost_filesystem -lboost_system -ldaf_base -lutils -lpex_exceptions -lbase -lboost_regex -lpthread -ldl -lpython2.7 ld: file not found: libz.1.dylib for architecture x86_64 clang: error: linker command failed with exit code 1 (use -v to see invocation) scons: *** [python/lsst/daf/persistence/_persistenceLib.so] Error 1 scons: building terminated because of errors. {code} This happens with the current master ({{3484020}} at time of writing), but also with a recent weekly ({{3878625}}).
| 1 |
1,109 |
DM-5607
|
03/24/2016 11:35:18
|
check & correct comparison operators in daf_persistence and daf_butlerUtils
|
per comments in DM-5593, an incorrect comparison operator was found, that used {{is}} instead of {{==}} in a string comparison (e.g. {{var is 'left'}} which is incorrect, it should be {{var == 'left'}}. This needs to be corrected in {{Repository}} (see DM-5593 for details), and the rest of daf_persistence and daf_butlerUtils should be checked for correct use of is vs. ==.
| 1 |
1,110 |
DM-5633
|
03/24/2016 16:22:00
|
Add data products and config in obs_decam for multi-band processing
|
Add necessary data products and default config in order to run forcedPhotCcd, coaddDriverTask, and multiBandDriverTask with DECam data.
| 3 |
1,111 |
DM-5635
|
03/25/2016 07:14:37
|
not flagged NaN in sdssCentroid
|
In some rare cases base_SdssCentroid_x(y)Sigma can be NaN while base_SdssCentroid_flag is False
| 1 |
1,112 |
DM-5641
|
03/26/2016 20:31:53
|
finish up afw.table to astropy.table view support
|
At an LSST/AstroPy summit hack session, we've put together a functional system for viewing afw.table objects as astropy.table objects on branch u/jbosch/astropy-tables of afw and https://github.com/astropy/astropy/pull/4740. Before merging, we should add support for "object" columns for subclasses to hold e.g. Footprints in SourceCatalog, and add some documentation. We may also want to add a convenience method to return an astropy.table.Table directly.
| 1 |
1,113 |
DM-5643
|
03/26/2016 20:40:39
|
add method to convert Property[Set,List] to nested dict
|
In interfacing with AstroPy it'd be useful to easily convert PropertySet and PropertyList to nested dict and OrderedDict (respectively), converting elements with multiple values to lists in the process.
| 2 |
1,114 |
DM-5659
|
03/30/2016 21:58:47
|
multiple dialog are not working well together
|
When several dialogs are up together. The most recently click one should be one top. When table are in the dialogs such a fits header view. The scroll bars will go over other dialogs. This needs some though and work. Another thing- when a message dialog is show because of a dialog error. It should center on the dialog. Update- I don't think I will do the error centering now. I am going to leave that and see if it is a real problem.
| 3 |
1,115 |
DM-5660
|
03/31/2016 00:20:57
|
Add motivated model fits to validate_drp photometric and astrometric scatter/repeatability analysis and plots
|
Implement well-motivated theoretical fits to the astrometric and photometric performance measurements based on derivations from LSST Overview paper. http://arxiv.org/pdf/0805.2366v4.pdf Photometric errors described by Eq. 5 sigma_rand^2 = (0.039 - gamma) * x + gamma * x^2 [mag^2] where x = 10^(0.4*(m-m_5)) Eq. 4 sigma_1^2 = sigma_sys^2 + sigma_rand^2 Astrometric Errors error = C * theta / SNR Based on helpful comments from [~zivezic] {quote} I think eq. 5 from the overview paper (with gamma = 0.039 and m5 = 24.35; the former I assumed and the latter I got from the value of your analytic fit that gives err=0.2 mag) would be a much better fit than the adopted function for mag < 21 (and it is derived from first principles). Actually, if you fit for the systematic term (eq. 4) and gamma and m5, it would be a nice check whether there is any “weird” behavior in analyzed data (and you get the limiting depth, m5, even if you don’t go all the way to the faint end). Similarly, for the astrometric random errors, we’d expect error = C * theta / SNR, where theta is the seeing (or a fit parameter), SNR is the photometric SNR (i.e. 1/err in mag), and C ~ 1 (empirically, and 0.6 for the idealized maximum likelihood solution and gaussian seeing). {quote}
| 5 |
1,116 |
DM-5663
|
03/31/2016 10:49:33
|
Config override fixes needed due to new star selector
|
As of DM-5532 a few config files need updating to not refer to star selector config fields as registries (not ones run by our normal CI, which is how I missed this).
| 2 |
1,117 |
DM-5664
|
03/31/2016 11:40:20
|
Delete or document and test config/psfex.py
|
The file {{config/psfex.py}} has no documentation and is bit rotting. If you feel it should be kept then please document it and add a simple unit test that loads it and runs data using it. If it is not needed, then please get rid of it.
| 1 |
1,118 |
DM-5675
|
03/31/2016 13:33:30
|
Cannot enable shapeHSM because RegistryField fails validation
|
When running ci_hsc after setting-up the meas_extensions_shapeHSM, meas_extensions_photometryKron and dependencies using setup -v -r . in the respective cloned folders, I get {code} Cannot enable shapeHSM (RegistryField 'calibrate.detectAndMeasure.measurement.plugins' failed validation: Unknown key 'ext_shapeHSM_HsmMoments' in Registry/ConfigChoiceField For more information read the Field definition at: File "/home/vish/code/lsst/lsstsw/stack/Linux64/pex_config/2016_01.0+3/python/lsst/pex/config/registry.py", line 179, in __init__ ConfigChoiceField.__init__(self, doc, types, default, optional, multi) And the Config definition at: File "/home/vish/code/lsst/lsstsw/stack/Linux64/meas_base/2016_01.0-13-g779ee14/python/lsst/meas/base/sfm.py", line 109, in <module> class SingleFrameMeasurementConfig(BaseMeasurementConfig): ): disabling HSM shape measurements {code} Find out why this is happening and find a fix
| 0.5 |
1,119 |
DM-5681
|
03/31/2016 14:08:24
|
Provide single-visit processing capability as required by HSC
|
In DM-3368, we provided a means of running multiple processCcd tasks across an exposure, but without performing global calibration etc as provided by HSC's ProcessExposureTask. Please augment this with whatever additional capability is required to enable HSC data release processing.
| 2 |
1,120 |
DM-5686
|
03/31/2016 17:41:18
|
Accommodate pixel padding when unpersisting reference catalog matches
|
The reference object loader in {{meas_algorithm}}'s *loadReferenceObjects.py* grows the bbox by the config parameter pixelMargin: doc = "Padding to add to 4 all edges of the bounding box (pixels)" . This is set to 50 by default but is not reflected by the radius parameter set in the metadata, so some matches may reside outside the circle searched within this radius. This increase needs to be reflected in the radius set in the metadata fed into {{joinMatchListWithCatalog()}}.
| 2 |
1,121 |
DM-5689
|
03/31/2016 21:31:00
|
Table needs to fire another action when data completely loaded
|
When the data for a table is completely loaded fire another action such as TABLE_NEW_LOADED_DONE. This way the xyplots and the image overlays know to go fetch the data. 4/22/2026 from the pull request: added new action TABLE_NEW_LOADED to table; fired when table is completely loaded. added table error handling. fix active table not updating after an active tab is removed.
| 2 |
1,122 |
DM-5694
|
04/01/2016 12:11:29
|
Run StarFast simulated images through diffim
|
Determine the metadata and dependencies needed to fully process two images simulated with StarFast through diffim.
| 2 |
1,123 |
DM-5695
|
04/01/2016 12:23:32
|
Implement simple 1D DCR correction on simulated data
|
Nate Lust wrote a simple DCR correction recipe that runs in 1D in an ipython notebook. This ticket is to re-write the notebook in python modules that can be run on StarFast simulated images prior to image differencing. For this ticket, the simulated images will be 2D, but DCR will be purely along the x or y pixel grid, allowing columns or rows of pixels to be treated separately in 1D.
| 8 |
1,124 |
DM-5702
|
04/01/2016 15:40:55
|
Create a new model in AST/GWCS to represent a complex distortion
|
Using lessons learned from DM-5701, create a more complex distortion model that cannot be represented from the basic models in GWCS or AST. A good example for this might be a rapidly varying sinusoidal tree-ring-like function that is not well represented by the standard polynomial basis functions. This will test our ability to extend each framework with new models that have not yet been decided on. Once completed, we could plug this back into the composite model in DM-5701.
| 8 |
1,125 |
DM-5703
|
04/01/2016 15:54:41
|
Evaluate performance of AST/GWCS over a range of numbers of pixels
|
Once we have a composite distortion model from DM-5701, evaluate the performance of AST and GWCS over a range of numbers of pixels, likely from ~100 through full-CCD (4k^2). As part of this process, we will try to determine whether there is a way to efficiently warp images/postage stamps using python-only models in GWCS and whether bottlenecks could be worked around via optimizations in cython.
| 8 |
1,126 |
DM-5720
|
04/05/2016 11:47:24
|
JIRA fixes
|
This tracks SPs spent on JIRA requests.
| 2 |
1,127 |
DM-5723
|
04/05/2016 18:34:56
|
make sure table can be resized properly
|
Test table to make sure it can be resized under a variety of layout.
| 2 |
1,128 |
DM-5726
|
04/05/2016 22:19:00
|
attend the weekly meeting with UIUC camera team (May 2016)
|
Tatiana will attend the weekly meeting. Xiuqin and Gregory also attends when needed.
| 2 |
1,129 |
DM-5729
|
04/06/2016 10:24:38
|
Config.loadFromStream suppresses NameError
|
Within a config override file being executed via {{Config.load}} or {{Config.loadFromStream}}, using a variable that hasn't been defined results in a {{NameError}} exception, but this is silently suppressed and the user has no idea the following overrides have not been executed.
| 0.5 |
1,130 |
DM-5734
|
04/06/2016 17:55:09
|
Fix the issues in the server side and the client side introduced by FitsHeaderViewer 's work
|
* The testing data "table_data.tbl" in the testing tree was accidentally moved. It should be added back so that IpactTableTest.java can run. * The request in JsontableUtil was mistakenly moved out from the tableModel by the the line * {code} * if (request != null && request.getMeta().keySet().size()>1) { tableModel.put("request", toJsonTableRequest(request)); } {code}. The meta can be null but the request is not null, the request should be put into the TableModel.
| 1 |
1,131 |
DM-5748
|
04/07/2016 17:12:10
|
Upgrade mpi4py to latest upstream
|
[mpi4py|https://bitbucket.org/mpi4py/] version 2.0 was released in October 2015 with a number of changes. We should upgrade. When upgrading, we should check whether it contains a proper fix for DM-5409 and, if not, file a bug report upstream. This issue should not be addressed until we have proper test coverage on code which uses mpi4py (DM-3845).
| 1 |
1,132 |
DM-5756
|
04/11/2016 10:04:49
|
Update Scons to v2.5.0
|
Scons 2.5.0 came out over the weekend. There were many fixes to the dependency determination code. The next version of Scons is intended to be 3.0 which will be the first version to support Python 3. Since we fully intend to switch to Python 3.0 in the summer it is prudent for us to ensuer that 2.5.0 works fine before switching to 3.0.0 so that we do not get confused as to why there is breakage in jumping straight to 3.0.0.
| 2 |
1,133 |
DM-5757
|
04/11/2016 10:34:47
|
FitsHeader's resize and sorting
|
DM-4494 has merged to the dev. However, there are still two issues remained: * Resize the popup with tabs does not work * Sorting is depending on the BasicTable's sorting
| 1 |
1,134 |
DM-5760
|
04/11/2016 11:42:23
|
XYPlot needs to be expandable
|
Make XYPlot expandable
| 2 |
1,135 |
DM-5763
|
04/11/2016 12:27:25
|
XYPlot: decimation options
|
User needs to be able to control number of bins and bin size.
| 3 |
1,136 |
DM-5765
|
04/11/2016 12:47:49
|
Remove unneeded imports in SConstruct
|
There's an outstanding pull request from an external contributor (Miguel de Val-Borro) [here|https://github.com/lsst/sconsUtils/pull/9] that makes some minor improvements to sconsUtils by cleaning up the imports. Somebody should review and (if appropriate) merge it. (Or, at least, reply to our community!)
| 1 |
1,137 |
DM-5767
|
04/11/2016 14:45:35
|
Create custom basic coaddition code
|
Create script to do the following: * Takes a list of DECam exposure numbers * for each CCD, loads the corresponding calexps * creates a naive pixel-by-pixel coadd of the underlying images * Possibly either ANDs or ORs the masks (though perhaps not necessary) * Either sums the expusure time info from the headers, or averages them, depending on whether the images were normalised to exposure times or not * write the corresponding images out as coadded fits
| 1 |
1,138 |
DM-5769
|
04/11/2016 15:00:27
|
Write spot visualisation snippets
|
Write some snippets to aide in the processing and visualisation of the CBP data/analysis. Essentially, write some helper functions that you can throw sections of images at to help look at the shape of the CBP spots, as ds9 isn't great ideal this. Some nice features would be: A function that takes a list of images or arrays, and plots them side-by-side, which provides some intelligent options for the stretches, and optionally stretches each image as is best for it, or ties them all to be the same. This would be as 2D colour plots. A function that takes part of an image and displays it as a colour-graded surface. A function that takes part of an image and displays it as a 3D bar-chart (as in ROOT, but without using ROOT because there is already enough evil in the world)
| 2 |
1,139 |
DM-5770
|
04/11/2016 15:05:01
|
Investigate image processing for feature enhancement
|
Whilst looking at an individual spot from the CBP on DECam I noticed a weird feature, and upon further investigation, several more, though these were very hard to see. This ticket is to investigate what image processing techniques will make these hard-to-see features pop out so that they can be examined more closely.
| 2 |
1,140 |
DM-5771
|
04/11/2016 15:12:09
|
Update config files
|
DM-46921 and DM-5348 changed ProcessCcd to the point where past config files are no longer valid as stuff has moved a lot (see https://community.lsst.org/t/backward-incompatible-changes-to-processccdtask-and-subtasks/581) This ticket is to go through past configs and create a new config file to reproduce the reductions done, or at least make something sensible come out the end of processCcd
| 2 |
1,141 |
DM-5773
|
04/11/2016 17:38:58
|
Firefly API plan and decision
|
We need a plan for all the Firefly APIs development in the new React/Redux based JS framework, including JS API and Python API. - Backward compatibility - Syntax format for JS API - Syntax format for Python API - Schedule - convert the existing API first - list of new ones to be added, when
| 2 |
1,142 |
DM-5775
|
04/12/2016 10:59:09
|
Change the TabPanel.jsx and TabPanel.css's properties to allow its children can be resizable
|
When an outside container is resizable (using css properties: resize: 'both', overflow: 'auto'...), in order for the child inside the container to be resizable, the child has to specify its height and width properties using percentage format (height: 90%, width:100%). When the TabPanel is used, the table is put on TabPanel. The table needs to access the size information of the outside container, ie,, the grandparent's width and height. The TabPanel has to pass the height and width to its child component. Without specifying the height and width in the TabPanel, by default, the auto is used. When the width (height) is auto, it allows to use the child's width (height). However, the child replies on the parent to provide such information. When this circular relations occur, the default size of the child is used. That is why the table component forever has 75px when it was put in the TabPanel. To be able to resize with the outside (root) contains all the ancestors of the component have to specify the width and height explicitly.
| 0.5 |
1,143 |
DM-5782
|
04/14/2016 07:36:52
|
Include obs_cfht, obs_decam in lsst-dev shared stack
|
The shared stack on {{lsst-dev}} provided in DM-5435 does not contain the {{obs_cfht}} or {{obs_decam}} camera packages. Please add them.
| 1 |
1,144 |
DM-5784
|
04/14/2016 10:02:50
|
Port region serializer and data structures from GWT
|
The region serializer in: firefly/src/firefly/java/edu/caltech/ipac/util * RegionFactory.java Region container data structures files in : firefly/src/firefly/java/edu/caltech/ipac/util/dd * ContainsOptions.java * Global.java * RegionFileElement.java * RegParseException.java * Region.java * RegionAnnulus.java * RegionBox.java * RegionBoxAnnulus.java * RegionCsys.java * RegionDimension.java * RegionEllipse.java * RegionEllipseAnnulus.java * RegionFont.java * RegionLines.java * RegionOptions.java * RegionPoint.java * RegionText.java * RegionValue.java Note - do not port CoordException, there are other ways to do this.
| 8 |
1,145 |
DM-5791
|
04/15/2016 17:17:44
|
Why is doSelectUnresolved an argument?
|
The {{run}} method in the {{PhotoCalTask}} has an argument that selects whether to use the extendedness parameter to select objects for photometric calibration. This is a good idea, but it should be configurable, I think.
| 1 |
1,146 |
DM-5793
|
04/16/2016 10:08:34
|
FITS Visualizer porting: Convert Mask support
|
* convert the make support from GWT * Make a temporary dialog to control it * Add python/JS API supporty
| 8 |
1,147 |
DM-5794
|
04/16/2016 10:19:00
|
Image Visualizer: Support image and drawing layer subgrouping
|
This will give user finer control of turning on/off the catalog overlays on one image, a group of images, or all the displayed images.
| 8 |
1,148 |
DM-5797
|
04/18/2016 14:50:56
|
Using 'CONSTANT' for background subtraction fails
|
Running processCcd (on a DECam file) with the following in the config file: {code} config.charImage.repair.cosmicray.background.algorithm='AKIMA_SPLINE' config.charImage.background.algorithm='CONSTANT' config.charImage.detectAndMeasure.detection.tempLocalBackground.algorithm='CONSTANT' config.charImage.detectAndMeasure.detection.background.algorithm='CONSTANT' config.calibrate.detectAndMeasure.detection.tempLocalBackground.algorithm='CONSTANT' config.calibrate.detectAndMeasure.detection.background.algorithm='CONSTANT' {code} fails, and throws the following: {code} Traceback (most recent call last): File "/home/mfisherlevine/lsst/pipe_tasks/bin/processCcd.py", line 25, in <module> ProcessCcdTask.parseAndRun() File "/ssd/lsstsw/stack/Linux64/pipe_base/2016_01.0-6-g7751869+8/python/lsst/pipe/base/cmdLineTask.py", line 450, in parseAndRun resultList = taskRunner.run(parsedCmd) File "/ssd/lsstsw/stack/Linux64/pipe_base/2016_01.0-6-g7751869+8/python/lsst/pipe/base/cmdLineTask.py", line 199, in run resultList = mapFunc(self, targetList) File "/ssd/lsstsw/stack/Linux64/pipe_base/2016_01.0-6-g7751869+8/python/lsst/pipe/base/cmdLineTask.py", line 324, in __call__ result = task.run(dataRef, **kwargs) File "/ssd/lsstsw/stack/Linux64/pipe_base/2016_01.0-6-g7751869+8/python/lsst/pipe/base/timer.py", line 118, in wrapper res = func(self, *args, **keyArgs) File "/home/mfisherlevine/lsst/pipe_tasks/python/lsst/pipe/tasks/processCcd.py", line 170, in run doUnpersist = False, File "/ssd/lsstsw/stack/Linux64/pipe_base/2016_01.0-6-g7751869+8/python/lsst/pipe/base/timer.py", line 118, in wrapper res = func(self, *args, **keyArgs) File "/home/mfisherlevine/lsst/pipe_tasks/python/lsst/pipe/tasks/characterizeImage.py", line 298, in run background = background, File "/ssd/lsstsw/stack/Linux64/pipe_base/2016_01.0-6-g7751869+8/python/lsst/pipe/base/timer.py", line 118, in wrapper res = func(self, *args, **keyArgs) File "/home/mfisherlevine/lsst/pipe_tasks/python/lsst/pipe/tasks/characterizeImage.py", line 356, in characterize image -= estBg.getImageF() File "/home/mfisherlevine/lsst/afw/python/lsst/afw/math/mathLib.py", line 5788, in getImageF return _mathLib.Background_getImageF(self, *args) lsst.pex.exceptions.wrappers.InvalidParameterError: File "src/math/Interpolate.cc", line 61, in std::pair<std::vector<double>, std::vector<double> > lsst::afw::math::{anonymous}::recenter(const std::vector<double>&, const std::vector<double>&) You must provide at least 1 point {0} File "src/math/BackgroundMI.cc", line 196, in void lsst::afw::math::BackgroundMI::_setGridColumns(lsst::afw::math::Interpolate::Style, lsst::afw::math::UndersampleStyle, int, const std::vector<int>&) const setting _gridcolumns {1} lsst::pex::exceptions::InvalidParameterError: 'You must provide at least 1 point {0}; setting _gridcolumns {1} {code}
| 2 |
1,149 |
DM-5799
|
04/18/2016 16:03:06
|
Asinh stretch algorithm corerction
|
in DM-2634, the Asinh stretch algorithm was implemented, but the behavior was not quite right. We need to figure out the issue and make it right. One possibility is that the understanding the relationship of zero point and black point, maximum point and white point.
| 8 |
1,150 |
DM-5803
|
04/19/2016 12:35:20
|
fetchUrl is not handling post requests correctly.
|
Parameters are not sent to the server when requests are posted via fetchUrl.
| 2 |
1,151 |
DM-5810
|
04/19/2016 18:23:32
|
Update imageDifferenceTask to cast template ids and use ObjectSizeStarSelector
|
A couple recent changes to the stack break imageDifferenceTask. Requires updates to only a few lines. While I'm updating it to reflect the star selector API, I'm also changing the default star selector from SecondMoment to ObjectSizeStarSelector (which I learned today is what the stack has been using by default for a while).
| 1 |
1,152 |
DM-5816
|
04/19/2016 19:13:00
|
Investigate behavior of Firefly and stretches for images with negative pixel values
|
Based on a discussion in the Tea Time HipChat room today, this is a "note to ourselves" to take a look at the behavior of Firefly when visualizing images with negative flux values. This is important for difference imaging and is therefore highly relevant to both LSST and ZTF (if ZTF difference images become visible through Firefly at some point). The behavior of the asinh stretch, in particular, should be looked at.
| 2 |
1,153 |
DM-5819
|
04/20/2016 07:57:09
|
Incorporate Price suggestions to make `validate_drp` faster
|
Increase the loading and processing speed of {{validate_drp}} following suggestions by [~price] 1. Don't read in footprints Pass {{flags=lsst.afw.table.SOURCE_IO_NO_FOOTPRINTS}} to {{butler.get}} 2. Work on speed of calculation of RMS and other expensive quantities. Current suggestions: a. {{calcRmsDistances}} b. {{multiMatch}} c. {{matchVisitComputeDistance}} d. Consider boolean indexing in {{afw}}'s {{multiMatch.py}} {code} objById = {record.get(self.objectKey): record for record in self.reference} to: objById = dict(zip(self.reference[self.objectKey], self.reference)) {code} Note that while this ticket will involve work to reduce the memory footprint of the processing, it will not cover work to re-architect things to enable efficient processing beyond the memory on one node.
| 2 |
1,154 |
DM-5821
|
04/20/2016 18:32:03
|
Intermittent fault building ci_hsc through Jenkins
|
Occasionally (see e.g. [here|https://ci.lsst.codes/job/stack-os-matrix/label=centos-7/10437//console] and [here|https://ci.lsst.codes/job/stack-os-matrix/label=centos-6/9594//console]) the {{ci_hsc}} job in Jenkins fails, reporting: {code} RuntimeError: dictionary changed size during iteration {code} The fault seems to be intermittent. Please fix it.
| 3 |
1,155 |
DM-5822
|
04/21/2016 08:46:25
|
Afw fails unit test for convolve depending on compiler optimisation level
|
On OSX 10.11.4 with Apple LLVM version 7.3.0 (clang-703.0.29) afw fails {{test/convolve.py}} with the following error when either {{-O0}} or {{-O1}} is enabled but works fine for {{-O2}} and {{-O3}}. {code:bash} tests/convolve.py .....FF/Users/pschella/Development/lsst/code/afw/python/lsst/afw/image/testUtils.py:283: RuntimeWarning: invalid value encountered in isnan nan0 = np.isnan(filledArr0) /Users/pschella/Development/lsst/lsstsw/miniconda/lib/python2.7/site-packages/numpy/lib/ufunclike.py:113: RuntimeWarning: invalid value encountered in isinf nx.logical_and(nx.isinf(x), ~nx.signbit(x), y) /Users/pschella/Development/lsst/lsstsw/miniconda/lib/python2.7/site-packages/numpy/lib/ufunclike.py:176: RuntimeWarning: invalid value encountered in isinf nx.logical_and(nx.isinf(x), nx.signbit(x), y) F.F... ====================================================================== FAIL: testSpatiallyVaryingAnalyticConvolve (__main__.ConvolveTestCase) Test in-place convolution with a spatially varying AnalyticKernel ---------------------------------------------------------------------- Traceback (most recent call last): File "tests/convolve.py", line 437, in testSpatiallyVaryingAnalyticConvolve rtol = rtol) File "tests/convolve.py", line 290, in runStdTest self.runBasicConvolveEdgeTest(kernel, kernelDescr) File "tests/convolve.py", line 317, in runBasicConvolveEdgeTest doVariance = True, rtol=0, atol=0, msg=msg) File "/Users/pschella/Development/lsst/code/afw/python/lsst/afw/image/testUtils.py", line 201, in assertMaskedImagesNearlyEqual testCase.fail("%s: %s" % (msg, "; ".join(errStrList))) AssertionError: basicConvolve(MaskedImage, kernel=Spatially Varying Gaussian Analytic Kernel using brute force) wrote to edge pixels: image planes differ: maxDiff=1.09176e+38 at position (73, 18); value=-1.09176e+38 vs. 2825.0; NaNs differ ====================================================================== FAIL: testSpatiallyVaryingDeltaFunctionLinearCombination (__main__.ConvolveTestCase) Test convolution with a spatially varying LinearCombinationKernel of delta function basis kernels. ---------------------------------------------------------------------- Traceback (most recent call last): File "tests/convolve.py", line 556, in testSpatiallyVaryingDeltaFunctionLinearCombination rtol = rtol) File "tests/convolve.py", line 290, in runStdTest self.runBasicConvolveEdgeTest(kernel, kernelDescr) File "tests/convolve.py", line 317, in runBasicConvolveEdgeTest doVariance = True, rtol=0, atol=0, msg=msg) File "/Users/pschella/Development/lsst/code/afw/python/lsst/afw/image/testUtils.py", line 201, in assertMaskedImagesNearlyEqual testCase.fail("%s: %s" % (msg, "; ".join(errStrList))) AssertionError: basicConvolve(MaskedImage, kernel=Spatially varying LinearCombinationKernel of delta function kernels using brute force) wrote to edge pixels: image planes differ: maxDiff=9.06659e+36 at position (75, 29); value=9.06659e+36 vs. 2865.0 ====================================================================== FAIL: testSpatiallyVaryingGaussianLinerCombination (__main__.ConvolveTestCase) Test convolution with a spatially varying LinearCombinationKernel of two Gaussian basis kernels. ---------------------------------------------------------------------- Traceback (most recent call last): File "tests/convolve.py", line 523, in testSpatiallyVaryingGaussianLinerCombination rtol = rtol) File "tests/convolve.py", line 290, in runStdTest self.runBasicConvolveEdgeTest(kernel, kernelDescr) File "tests/convolve.py", line 317, in runBasicConvolveEdgeTest doVariance = True, rtol=0, atol=0, msg=msg) File "/Users/pschella/Development/lsst/code/afw/python/lsst/afw/image/testUtils.py", line 201, in assertMaskedImagesNearlyEqual testCase.fail("%s: %s" % (msg, "; ".join(errStrList))) AssertionError: basicConvolve(MaskedImage, kernel=Spatially Varying Gaussian Analytic Kernel with 3 basis kernels convolved using brute force) wrote to edge pixels: image planes differ: maxDiff=1.22472e+38 at position (74, 3); value=-1.22472e+38 vs. 2878.0; NaNs differ ====================================================================== FAIL: testTicket873 (__main__.ConvolveTestCase) Demonstrate ticket 873: convolution of a MaskedImage with a spatially varying ---------------------------------------------------------------------- Traceback (most recent call last): File "tests/convolve.py", line 623, in testTicket873 rtol = rtol) File "tests/convolve.py", line 290, in runStdTest self.runBasicConvolveEdgeTest(kernel, kernelDescr) File "tests/convolve.py", line 317, in runBasicConvolveEdgeTest doVariance = True, rtol=0, atol=0, msg=msg) File "/Users/pschella/Development/lsst/code/afw/python/lsst/afw/image/testUtils.py", line 201, in assertMaskedImagesNearlyEqual testCase.fail("%s: %s" % (msg, "; ".join(errStrList))) AssertionError: basicConvolve(MaskedImage, kernel=Spatially varying LinearCombinationKernel of basis kernels with low covariance, using brute force) wrote to edge pixels: image planes differ: maxDiff=3.19374e+38 at position (1, 46); value=3.19374e+38 vs. 2774.0 ---------------------------------------------------------------------- Ran 13 tests in 43.252s FAILED (failures=4) The following tests failed: /Users/pschella/Development/lsst/code/afw/tests/.tests/convolve.py.failed 1 tests failed scons: *** [checkTestStatus] Error 1 scons: building terminated because of errors. {code}
| 2 |
1,156 |
DM-5823
|
04/21/2016 09:28:12
|
ECL_B1950 coordinate was not defined correctly
|
The CoordSys.js defined ECL_B1950 incorrectly. When I was testing WebGrid, the grid lines for Ecliptic B1950 were not right. Looked further, it was caused by wrong equinox value in its definition.
| 0.5 |
1,157 |
DM-5829
|
04/22/2016 11:11:53
|
Create outline of Level 3 ConOps
|
Create an outline of the sections of the Level 3 ConOps document
| 2 |
1,158 |
DM-5830
|
04/22/2016 11:13:57
|
Level 3 requirements flowdown
|
Document the flowdown of Level 3-related requirements from SRD, LSR, OSS, and DMSR.
| 3 |
1,159 |
DM-5832
|
04/22/2016 11:25:22
|
LSE-140 post-CCB implementation
|
Following CCB approval of LSE-140, perform minor document work required for full implementation (application of standard cover page, change log, etc.).
| 2 |
1,160 |
DM-5835
|
04/22/2016 12:18:01
|
Prepare a draft of the SUIT deployment timeline
|
Prepare a draft schedule, with some detail for 2016-2017, for deployments of the SUIT into (test) production, including the datasets that will be served.
| 2 |
1,161 |
DM-5837
|
04/22/2016 13:14:07
|
Document pipe_drivers
|
Please provide a minimal level of documentation for {{pipe_drivers}}, to include: * A {{doc}} directory with the usual content so that docstrings get generated by Doxygen; * A package overview; * All docstrings should be appropriate for parsing by Doxygen (ie, should start with {{"""!}} where necessary).
| 2 |
1,162 |
DM-5838
|
04/22/2016 17:04:44
|
3-color image label change
|
When generating 3-color image, the label for the image display should 'Project 3-color', i.e. WISE 3-color, 2MASS 3-color ...
| 0 |
1,163 |
DM-5839
|
04/23/2016 13:35:17
|
horizon console interface broken
|
It appears that at some point in the last few months the horizon console interface has stopped working. I am still able to access the console log output via the API/CLI.
| 1 |
1,164 |
DM-5840
|
04/23/2016 13:53:05
|
instance limit low vs available cores
|
The LSST project is currently at 81/100 instances but there are over 200 cores unused. Is it possible to increase the instance limit or are we being encouraged to use large instance flavors?
| 1 |
1,165 |
DM-5841
|
04/23/2016 14:19:56
|
unable to list nebula lsst project users
|
Currently, [with some difficulty] it is possible to discover the {{user_id}} that created an instance (might be possible for other resources as well) but it is not possible to map this back to a username / person. This can make it difficult to 'self police' instances. The administrative API endpoints are not publicly accessible and I doubt any end user has the appropriate permission.
| 1 |
1,166 |
DM-5847
|
04/25/2016 15:00:23
|
libxml build issue with mpich on OS X
|
On OS X with Xcode installed {{mpich}} fails to build because it can not locate the libxml include files: {code} CC topology-xml-libxml.lo topology-xml-libxml.c:17:10: fatal error: 'libxml/parser.h' file not found #include <libxml/parser.h> ^ 1 error generated. {code} with {{pkg-config}} 0.29.1 installed. The problem is that {{configure}} determines that {{libxml-2.0}} is available and is installed into {{/usr}} with a CFLAGS of {{-I/usr/include/libxml2}}. {{configure}} does not itself test whether those parameters are reasonable. With Xcode there are no files installed into {{/usr/include}} and {{clang}} knows to look in specific SDK locations. When {{mpich}} builds it assumes that {{libxml2}} can be found but fails to find it. Strangely, {{pkg-config}} v0.28 does not seem to be able to find {{libxml-2.0}} so there is no issue. One solution is to install the Command Line Tools but it might be more portable to attempt to disable {{libxml2}}.
| 2 |
1,167 |
DM-5848
|
04/25/2016 16:34:17
|
Investigate Jupyter internals, interactive widgets
|
In preparation for linking Jupyter notebooks with Firefly and other SUIT components, read Jupyter documentation. Learn how to build a sample widget or interactive dashboard in the Jupyter framework
| 2 |
1,168 |
DM-5849
|
04/25/2016 16:38:09
|
Investigate Ginga and Glueviz visualization tools
|
Ginga and Glue (glueviz) are community visualization tools in Python. Become familiar with the capabilities of both, thinking from the point of view of using Firefly for the display but using Python for many other things.
| 2 |
1,169 |
DM-5854
|
04/25/2016 17:36:26
|
Java array index out of bound error in VisSeverCommand.java
|
The class FileFluxCmdJson in VisServerCommand.java is calling {code} String[] res = VisServerOps.getFileFlux(fahAry, pt); {code} However, when the mouse is outside the image, the VisServerOps.getFileFlux(fahAry, pt) returns: {code} new String[]{PlotState.NO_CONTEXT} {code} It is fine for a single band. However, for 2 or 3 bands, the for loop below caused the index out of bound error because res is an array of length=1 and the expected res is an array of length=no of bands. {code} JSONObject obj= new JSONObject(); obj.put("JSON", true); obj.put("success", true); int cnt=0; JSONObject data= new JSONObject(); for(Band b : state.getBands()) { data.put(b.toString(), res[cnt++]); } data.put("success", true); {code} Thus, res\[cnt++\] caused array index out of bound error. To fix this issue, the for loop is changed as below: {code} int cnt=0; JSONObject data= new JSONObject(); Band[] bands = state.getBands(); for (int i=0; i<res.length; i++){ data.put(bands[i].toString(), res[i]); } data.put("success", true); JSONArray wrapperAry= new JSONArray(); obj.put("data", data); wrapperAry.add(obj); {code} When the mouse is outside the image, the res returns a new String\[\]\{PlotState.NO_CONTEXT\}, it is added to the JSONObject only once.
| 1 |
1,170 |
DM-5859
|
04/26/2016 11:03:44
|
Table: Add keyboard navigation
|
- Added arrow up/down to move between rows. - Added page up/down to move between pages. - Fixed table loading mask not showing - Fixed PagingBar rendering more than it should - Fixed annoying StandardView missing unique key warning
| 2 |
1,171 |
DM-5870
|
04/26/2016 17:46:13
|
Update testdata_subaru to support calib changes
|
Merging DM-5124 broke obs_subaru because the test data in testdata_subaru wasn't updated. Fix it.
| 0.5 |
1,172 |
DM-5883
|
04/27/2016 19:36:41
|
Include more information in DECam registry
|
obs_decam originally included 'object' and 'proposal' fields in the registry but these were removed at some point. Putting them back would allow users to more easily select data. I also suggest surveying the headers for additional useful fields.
| 1 |
1,173 |
DM-5885
|
04/28/2016 02:52:26
|
Create a JSON file for monitoring stack
|
Create a JSON or YAML file with: - Qserv version - libraries/deps version - other idea welcome This will interesting "GROUP BY" in monitoring tool (performance for each Qserv or xrootd version for example)
| 3 |
1,174 |
DM-5887
|
04/28/2016 10:11:48
|
lsstswBuild.sh --print-fail flag broken
|
The {{--print-fail}} flag appears to broken for at least some failure modes. https://github.com/lsst-sqre/buildbot-scripts/blob/master/lsstswBuild.sh#L145 Eg. https://ci.lsst.codes/job/stack-os-matrix/label=centos-6/10673//console
| 0.5 |
1,175 |
DM-5889
|
04/28/2016 12:22:05
|
Suppress gcc warnings about "unused local typedefs"
|
We should add {{\-Wno\-unused\-local\-typedefs}} to our gcc options. This cleans up the build significantly, because there's a flood of warnings of this type coming from boost. If we suppress those, it might become possible to notice warnings that we care about.
| 0.5 |
1,176 |
DM-5893
|
04/28/2016 14:46:49
|
LSST the Docs Fastly should redirect /en/latest/ to /
|
Previously we deployed documentation on Read the Docs. By default, Read the Docs would show the master version of documentation on "/en/latest/". Many links with that endpoint may already exist. We should configure Fastly to redirect such paths to "/".
| 0.5 |
1,177 |
DM-5898
|
04/28/2016 20:49:16
|
Python EUPS package can use $PYTHON
|
The {{python}} eups package has a script that checks that the python being used is version 2.7. This script can optionally check {{$PYTHON}} rather than the python in the path but I am confused as to what that test is going to do for us. The problem is that {{sconsUtils}} uses {{python}} and most of the shebangs use {{/bin/env python}} (although shebang rewriting on all platforms could help with that). I think the check script should have the {{$PYTHON}} support removed due to excessive confusion. It would also help if the check script worked with python 3 so that the wrong python could be caught.
| 1 |
1,178 |
DM-5899
|
04/29/2016 06:34:16
|
Support LSST-produced calibs
|
obs_decam currently uses a {{%(path)s\[%(ccdnum)d\]}} template for its calibs (bias, dark, flat, fringe). This is desirable in order to support calibs provided from external sources (e.g., NOAO). However, our calib construction code does not support such a path ({{path}} cannot be inferred for new data, and we can't write MEFs from multiple processes). We believe the best path forward is to split the {{DecamMapper}} into two mappers, one supporting calibs from external sources and one supporting calibs we construct ourselves. The alternative is to copy the external calibs to match a template like {{BIAS/%(date)s/BIAS-%(date)s-%(ccdnum)02d.fits}}, which means breaking apart the MEFs. I suggest also moving the defects into the obs_decam package because they're required for use, small and we don't have code to regenerate them.
| 0 |
1,179 |
DM-5900
|
04/29/2016 10:23:55
|
Create psutil EUPS package
|
Add the python {{psutil}} package to the stack as {{python_psutil}}.
| 0.5 |
1,180 |
DM-5904
|
04/29/2016 12:43:01
|
Create focus script
|
In DM-3368, we stripped out the focus calculation since it's not camera-generic, and the scatter/gather isn't necessary for general processing. We need to reinstate the focus calculation in its own scatter/gather script.
| 2 |
1,181 |
DM-5911
|
04/29/2016 15:24:35
|
Fix circular references in Mapper objects
|
Whilst running tests with pytest and the new file descriptor leak checker it became clear that Mapper objects were not freeing their resources when they were deleted. In particular, the registry objects remained and the associated sqlite database files were opened. This led to pytest running out of file descriptors when large test suites were being executed. The problem turns out to be the dynamically created map functions. These are created as functions (not bound methods) attached to an instance. Since they are not bound methods the instance object (self) has to be passed in to closure. This leads to self containing a reference to a function that contains a reference to self and this prevents the Mapper from ever being garbage collected (leading to all the resources being retained). A short term fix is pass the mappers into the closures using {{weakref}}. Eventually it would be nice to consistently make the {{map_}} items bound methods rather than attaching them as functions but that is beyond the scope of this ticket.
| 1 |
1,182 |
DM-5915
|
04/29/2016 17:47:34
|
Decide how to rework afw:Wcs guts with AST
|
Following the to-be-written recommendation for DM-4157, we plan to rework the guts of afw:Wcs to use AST. We need to decide how afw:Wcs will use AST, whether as a wrapper or as a complete replacement with AST. The product is a design
| 8 |
1,183 |
DM-5921
|
05/02/2016 09:29:00
|
Clarify how to work with ci_hsc's astrometry_net_data
|
ci_hsc's {{README.rst}} contains [a note|https://github.com/lsst/ci_hsc/blob/87b6ecb1cc0157cac8dafb356520f49f971bb1ec/README.rst#reference-catalog] on declaring & setting up the included reference catalogue data. I believe this was rendered obsolete by DM-5135, which automatically sets up the reference catalogue when ci_hsc itself is set up. Attempting to follow the documentation therefore produces confusing warning messages, and may break things. Please check if my understanding is correct and, if so, fix the documentation.
| 0.5 |
1,184 |
DM-5922
|
05/02/2016 10:33:22
|
Rework camera geometry to use the replacement for XYTransform
|
As part of overhauling XYTransform we will likely need to replace the way we describe the transformations supported by camera geometry and {{Detector}}. This is likely to include a new way of describing the coordinate frames (e.g. {{PIXEL}}. {{FOCAL_PLANE}} and {{PUPIL}}). If we adopt AST (as seems likely) then these frames will be AST {{Frames}}, the transforms will be AST {{Mappings}} and the collection described by {{Camera}} and {{Detector}} will be one or more AST {{FrameSets}}. An RFC for the redesigned API for camera geometry will be required and this ticket is to implement the resulting design.
| 8 |
1,185 |
DM-5926
|
05/02/2016 14:21:05
|
networking in strange state for newly created instances
|
When starting a new instance, occasionally something strange seems to happen with the network setup. The instance will come up but is inaccessible (icmp, ssh). When this happens, the console log shows that a DHCP address was obtained and cloud-init injected ssh-keys, so it isn't a total network setup failure. I have seen this happen a few times in the last couple of weeks but I can't reliably reproduce it. I'm wondering if neutron is logging anything interesting when this happens. This failure mode happened again a few minutes ago with 7adffa82-7221-454c-acfe-5f21cdd34ea8. Which I killed and recreated as instance b6f64981-099b-46e5-a27e-e3694372f447 with the same private IP address. The new instance is accessible as expected.
| 1 |
1,186 |
DM-5927
|
05/02/2016 14:39:02
|
API errors when trying to start up multiple instances
|
I am attempting to start up 20 {{m1.medium}} instances without floating IPs to take available of the new instance cap from DM-5840. This consistently fails after starting a few instances with an HTTP 403. {code:java} Error creating OpenStack server: Expected HTTP response code [201 202] when accessing [POST http://nebula.ncsa.illinois.edu:8774/v2/8c1ba1e0b84d486fbe7a665c30030113/servers], but got 403 instead {"forbidden": {"message": "Maximum number of ports exceeded", "code": 403}} {code} Of the instances that do manage to start, most end up in an error state with. {code:java} (openstack) server show 134b69dc-56fc-4249-b92f-e958e561ae3b +--------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------+ | Field | Value | +--------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------+ | OS-DCF:diskConfig | MANUAL | | OS-EXT-AZ:availability_zone | nova | | OS-EXT-STS:power_state | 0 | | OS-EXT-STS:task_state | None | | OS-EXT-STS:vm_state | error | | OS-SRV-USG:launched_at | None | | OS-SRV-USG:terminated_at | None | | accessIPv4 | | | accessIPv6 | | | addresses | | | config_drive | | | created | 2016-05-02T20:29:54Z | | fault | {'code': 500, 'message': 'No valid host was found. Exceeded max scheduling attempts 3 for instance 134b69dc-56fc-4249-b92f-e958e561ae3b. Last | | | exception: [u\'Traceback (most recent call last):\\n\', u\' File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 2235, in _do', | | | 'created': '2016-05-02T20:29:57Z'} | | flavor | m1.medium (3) | | hostId | b383eddb06f7a1cc5929e5fa8b6982cc523f5ac1cbe3c9c40120a700 | | id | 134b69dc-56fc-4249-b92f-e958e561ae3b | | image | centos-7-slurm-20160422210744 (7364ada7-263e-4fb0-a9f4-219ab19e0be0) | | key_name | jhoblitt-slurm | | name | slurm-slave4 | | os-extended-volumes:volumes_attached | [] | | project_id | 8c1ba1e0b84d486fbe7a665c30030113 | | properties | slurm_node_type='slave' | | status | ERROR | | updated | 2016-05-02T20:29:57Z | | user_id | 83bf259d1f0c4f458e03f9002f9b4008 | +--------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------+ {code}
| 2 |
1,187 |
DM-5933
|
05/02/2016 17:09:40
|
Replace jointcal.StarSelector with meas_algorithms.starSelector
|
jointcal has its own custom star selector. This should be removed and replaced with a star selector based on meas_algorithms.starSelector. A good choice might be meas_algorithms.objectSizeStarSelector.
| 2 |
1,188 |
DM-5934
|
05/02/2016 18:47:22
|
Update developer guide with Astropy guidance
|
Once RFC-178 is adopted the developer guide has to be updated to include guidance as to how Astropy can be used in the stack (similar to how Boost is documented).
| 1 |
1,189 |
DM-5935
|
05/02/2016 18:49:31
|
Package Astropy for the stack
|
Once RFC-178 is adopted Astropy needs to be packaged in an EUPS container. Given the complexity of Astropy dependencies the packaging will be done as for {{numpy}} and {{scipy}} by checking that Astropy is available (v1.1 will be the minimum version).
| 1 |
1,190 |
DM-5936
|
05/03/2016 09:17:02
|
Make afw rgb unit test PEP440 compliant for matplotlib check
|
If a user has a version of matplotlib installed from a git clone, the afw rgb unit test fails at the matplotlib version check. The versioning scheme for this type of install is determined by pep 440. Make the unit test properly handle this type of version comparison.
| 0.5 |
1,191 |
DM-5939
|
05/03/2016 11:17:34
|
Pre-release versions of matplotlib 2.0 break afw unit tests
|
In the afw rgb unit test, testWriteStarsLegacyAPI checks to make sure that a file name with an unknown extension raises a value error. In current version of matplotlib, saving a file with an unknown extension causes this error: {code} *** ValueError: Format "unknown" is not supported. Supported formats: eps, jpeg, jpg, pdf, pgf, png, ps, raw, rgba, svg, svgz, tif, tiff. {code} In matplotlib 2.0 prerelease the file is saved as a png when an unknown extension is specified. Since the write call success the unit test fails as it is expecting a failure. If nothing depends on this behavior, the unit test should probably be removed.
| 0.5 |
1,192 |
DM-5940
|
05/03/2016 14:21:22
|
Create new build based on the converted firefly code.
|
- remove all of the gwt code except for a few remaining files. - create separate build for the new firefly viewer, leaving the old fftools as it was before the JS conversion. - repackage files as needed moving forward.
| 8 |
1,193 |
DM-5941
|
05/03/2016 14:33:25
|
Private network not available across all instances
|
I'm setting up an ELK system. Part of that is an Elasticsearch system. When I bring up the system the private network is bisected. I attempted creating a security group, in case that was a problem but it didn't help. Note that the work around is to create security groups or use a firewall and use floating ips. This is far from ideal. I think the right solution is to use the private network. Example: First section {{p-es-1}} {{p-es-3}} {{p-es-k}} {code:bash} vagrant@es-1:~$ ifconfig ens3 Link encap:Ethernet HWaddr fa:16:3e:47:28:a7 inet addr:10.0.42.30 Bcast:10.0.42.255 Mask:255.255.255.0 inet6 addr: fe80::f816:3eff:fe47:28a7/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1454 Metric:1 RX packets:363265 errors:0 dropped:0 overruns:0 frame:0 TX packets:304215 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:95396177 (95.3 MB) TX bytes:238466304 (238.4 MB) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:850 errors:0 dropped:0 overruns:0 frame:0 TX packets:850 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1 RX bytes:138411 (138.4 KB) TX bytes:138411 (138.4 KB) vagrant@es-1:~$ ping 10.0.42.32 PING 10.0.42.32 (10.0.42.32) 56(84) bytes of data. 64 bytes from 10.0.42.32: icmp_seq=1 ttl=64 time=0.284 ms 64 bytes from 10.0.42.32: icmp_seq=2 ttl=64 time=0.266 ms 64 bytes from 10.0.42.32: icmp_seq=3 ttl=64 time=0.265 ms 64 bytes from 10.0.42.32: icmp_seq=4 ttl=64 time=0.302 ms ^C --- 10.0.42.32 ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 2998ms rtt min/avg/max/mdev = 0.265/0.279/0.302/0.019 ms vagrant@es-1:~$ ping 10.0.42.34 PING 10.0.42.34 (10.0.42.34) 56(84) bytes of data. 64 bytes from 10.0.42.34: icmp_seq=1 ttl=64 time=0.333 ms 64 bytes from 10.0.42.34: icmp_seq=2 ttl=64 time=0.325 ms 64 bytes from 10.0.42.34: icmp_seq=3 ttl=64 time=0.322 ms 64 bytes from 10.0.42.34: icmp_seq=4 ttl=64 time=0.319 ms ^C --- 10.0.42.34 ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 2998ms rtt min/avg/max/mdev = 0.319/0.324/0.333/0.022 ms vagrant@es-1:~$ ping 10.0.42.31 PING 10.0.42.31 (10.0.42.31) 56(84) bytes of data. From 10.0.42.30 icmp_seq=1 Destination Host Unreachable From 10.0.42.30 icmp_seq=2 Destination Host Unreachable From 10.0.42.30 icmp_seq=3 Destination Host Unreachable ^C --- 10.0.42.31 ping statistics --- 4 packets transmitted, 0 received, +3 errors, 100% packet loss, time 3017ms pipe 3 vagrant@es-1:~$ ping 10.0.42.33 PING 10.0.42.33 (10.0.42.33) 56(84) bytes of data. From 10.0.42.30 icmp_seq=1 Destination Host Unreachable From 10.0.42.30 icmp_seq=2 Destination Host Unreachable From 10.0.42.30 icmp_seq=3 Destination Host Unreachable ^C --- 10.0.42.33 ping statistics --- 4 packets transmitted, 0 received, +3 errors, 100% packet loss, time 3008ms pipe 3 vagrant@es-1:~$ ping 10.0.42.35 PING 10.0.42.35 (10.0.42.35) 56(84) bytes of data. From 10.0.42.30 icmp_seq=1 Destination Host Unreachable From 10.0.42.30 icmp_seq=2 Destination Host Unreachable From 10.0.42.30 icmp_seq=3 Destination Host Unreachable ^C --- 10.0.42.35 ping statistics --- 5 packets transmitted, 0 received, +3 errors, 100% packet loss, time 3999ms pipe 3 {code} Second section {{p-es-2}} {{p-es-4}} {{p-lfr}} {code:bash} vagrant@es-2:~$ ifconfig ens3 Link encap:Ethernet HWaddr fa:16:3e:6f:30:2c inet addr:10.0.42.31 Bcast:10.0.42.255 Mask:255.255.255.0 inet6 addr: fe80::f816:3eff:fe6f:302c/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1454 Metric:1 RX packets:196344 errors:0 dropped:0 overruns:0 frame:0 TX packets:160561 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:47667399 (47.6 MB) TX bytes:7135345 (7.1 MB) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:97268 errors:0 dropped:0 overruns:0 frame:0 TX packets:97268 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1 RX bytes:8558096 (8.5 MB) TX bytes:8558096 (8.5 MB) vagrant@es-2:~$ ping 10.0.42.33 PING 10.0.42.33 (10.0.42.33) 56(84) bytes of data. 64 bytes from 10.0.42.33: icmp_seq=1 ttl=64 time=0.311 ms 64 bytes from 10.0.42.33: icmp_seq=2 ttl=64 time=0.309 ms 64 bytes from 10.0.42.33: icmp_seq=3 ttl=64 time=0.300 ms ^C --- 10.0.42.33 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2000ms rtt min/avg/max/mdev = 0.300/0.306/0.311/0.020 ms vagrant@es-2:~$ ping 10.0.42.30 PING 10.0.42.30 (10.0.42.30) 56(84) bytes of data. From 10.0.42.31 icmp_seq=1 Destination Host Unreachable From 10.0.42.31 icmp_seq=2 Destination Host Unreachable From 10.0.42.31 icmp_seq=3 Destination Host Unreachable From 10.0.42.31 icmp_seq=4 Destination Host Unreachable ^C --- 10.0.42.30 ping statistics --- 5 packets transmitted, 0 received, +4 errors, 100% packet loss, time 4014ms pipe 3 vagrant@es-2:~$ ping 10.0.42.32 PING 10.0.42.32 (10.0.42.32) 56(84) bytes of data. From 10.0.42.31 icmp_seq=1 Destination Host Unreachable From 10.0.42.31 icmp_seq=2 Destination Host Unreachable From 10.0.42.31 icmp_seq=3 Destination Host Unreachable From 10.0.42.31 icmp_seq=4 Destination Host Unreachable From 10.0.42.31 icmp_seq=5 Destination Host Unreachable ^C --- 10.0.42.32 ping statistics --- 5 packets transmitted, 0 received, +5 errors, 100% packet loss, time 4023ms pipe 3 vagrant@es-2:~$ ping 10.0.42.34 PING 10.0.42.34 (10.0.42.34) 56(84) bytes of data. From 10.0.42.31 icmp_seq=1 Destination Host Unreachable From 10.0.42.31 icmp_seq=2 Destination Host Unreachable From 10.0.42.31 icmp_seq=3 Destination Host Unreachable ^C --- 10.0.42.34 ping statistics --- 4 packets transmitted, 0 received, +3 errors, 100% packet loss, time 3006ms pipe 3 vagrant@es-2:~$ ping 10.0.42.35 PING 10.0.42.35 (10.0.42.35) 56(84) bytes of data. 64 bytes from 10.0.42.35: icmp_seq=1 ttl=64 time=0.387 ms 64 bytes from 10.0.42.35: icmp_seq=2 ttl=64 time=0.278 ms 64 bytes from 10.0.42.35: icmp_seq=3 ttl=64 time=0.288 ms ^C --- 10.0.42.35 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1998ms rtt min/avg/max/mdev = 0.278/0.317/0.387/0.053 ms {code} This can be reproduced by sourcing your OpenStack credentials and running this [{{Vagrantfile}}|https://gist.github.com/jmatt/7b6eb6a042c4e63531d40d1a68069f33]. Use {{vagrant ssh p-es-1}} to connect to the {{p-es-1}} instance.
| 2 |
1,194 |
DM-5973
|
05/04/2016 15:36:15
|
Update developer guide with pytest guidance
|
Now that DM-5561 explains how to migrate to pytest compatibility the developer guide must be updated to state how to use pytest in unittests.
| 5 |
1,195 |
DM-5979
|
05/05/2016 11:59:15
|
tests in testArgumentParser.py fail Jenkins run-rebuild on nfs
|
(1) {{testOutputs}} fails because paths are compared literally Jenkins run-rebuild #139 failed with pipe_base https://ci.lsst.codes/job/run-rebuild/139//console {code:java} FAIL: testOutputs (__main__.ArgumentParserTestCase) Test output directories, specified in different ways ---------------------------------------------------------------------- Traceback (most recent call last): File "tests/testArgumentParser.py", line 497, in testOutputs self.assertEqual(args.input, DataPath) AssertionError: '/nfs/home/lsstsw/stack/Linux64/obs_test/2016_01.0-3-gafa6dd0+10/data/input' != '/home/lsstsw/stack/Linux64/obs_test/2016_01.0-3-gafa6dd0+10/data/input' {code} Please make the comparison more robust. (2) File descriptor leaks Jenkins run-rebuild #138 failed with pipe_base https://ci.lsst.codes/job/run-rebuild/138//console {code:java} FAIL: testFileDescriptorLeaks (lsst.utils.tests.MemoryTestCase) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/lsstsw/stack/Linux64/utils/2016_01.0-2-g97a6e33/python/lsst/utils/tests.py", line 133, in testFileDescriptorLeaks self.fail("Failed to close %d files" % len(diff)) AssertionError: Failed to close 1 files {code} {code:java} File open: /nfs/home/lsstsw/build/pipe_base/.nfs000000000a20a3f700005679 {code} This test passes on local disk.
| 2 |
1,196 |
DM-5986
|
05/06/2016 08:30:23
|
Use sagas in place of side-effects in chart-related controllers
|
Replace side-effects with saga and clean-up chart related controllers (TableStats, XYPlot and Histogram).
| 3 |
1,197 |
DM-6022
|
05/09/2016 09:12:08
|
Lazy load related chart data on table data update
|
When new table data received, the related chart data should be updated only for the components on display. Hidden components' data should be lazily updated when a component becomes visible.
| 3 |
1,198 |
DM-6026
|
05/09/2016 09:52:52
|
Make it possible to distinguish TABLE_NEW_LOADED actions triggered by sort
|
It would be beneficial to have in the TABLE_NEW_LOADED payload a trigger field, which would differentiate actions triggered by sort (where data do not change, only their order) or filter from other loads. We don't need to reload table statistics or histogram on sort. But we do need to to reload them on filter. created TABLE_SORT action to distinguish sorting from filtering. sorting should not reload xyplot nor catalog overlay. Also: - disable history when in api mode. - ensure tableMeta.source reflects the file on the server. - fix TablePanelOptions not resetting columns selection. - remove 'Fits Data' tab when no images available. - fix 'Coverage' appearing when it should.
| 2 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.