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,399 |
DM-7171
|
08/09/2016 08:20:46
|
Document interface for SpanSets class
|
Write up a brief technote describing the new SpanSet interface, both things such as functions etc, and descriptions about how it is expected to be used in the future, and made available through python. This will give others a chance to express their needs opinions for span sets while the development is still ongoing
| 5 |
1,400 |
DM-7172
|
08/09/2016 08:26:04
|
Implement SpanSet overlap tests
|
Implement testing for overlapping spans in SpanSets
| 3 |
1,401 |
DM-7177
|
08/09/2016 08:42:50
|
Document interface for new Footprints class
|
Create a technote and a community posting on the new Footprints class to both document the new api, and explain the differences with the old class.
| 8 |
1,402 |
DM-7179
|
08/09/2016 12:51:31
|
sconsUtils reads SConscript files in alphabetical order
|
I have made the deeply embarrassing discovery that I knowingly made sconsUtils' reading of SConstruct files discovered in subdirectories ordered alphabetically, and considered this okay because "include < lib < python < test". This needs to be made user-configurable, probably via a keyword argument to {{sconsUtils.scripts.BasicSConstruct}}.
| 1 |
1,403 |
DM-7180
|
08/09/2016 13:15:53
|
Port HSC aperture correction fix
|
Port [HSC-1416|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1416] to prevent {{ZeroDivisionError}} in {{MeasureApCorrTask}}.
| 1 |
1,404 |
DM-7182
|
08/09/2016 15:18:29
|
Discuss L1 database requirements (continuing)
|
There are few things that are not yet very well understood in the L1 database access from AP. I need to meet with pipeline people at LSST2016 and try to clarify all of them The list of questions will be added below.
| 8 |
1,405 |
DM-7190
|
08/10/2016 12:31:31
|
Fix region bugs related to zoom selected region, add empty region layer and add/remove more regions
|
This one is made to include some issues report in DM-7027 (issues 4, 5, 6): 4. When a region is selected, yellow dashed line appears around it. On zoom the line does not change color. 5. Can not add empty region. Line 124 of the test script. 6. Can not add or delete regions after the first one. (Load test script, click Show Regions, then Add Region, line 121 of the test script) When there is one region in the layer and you are adding another region with a different position but everything else the same, the added region is perceived to be the same.
| 2 |
1,406 |
DM-7192
|
08/10/2016 14:07:58
|
replaced image of the coverage is gone after expand mode
|
do a catalog search, then do an image search to replace coverage image by another image (say WISE), then go in expand mode and back, the image is replaced back to the initial coverage image
| 2 |
1,407 |
DM-7195
|
08/10/2016 19:41:45
|
Add a download feature to get the single exposure cutout from a LC
|
The LC viewer need an extra download button to get all the cutout from the light-curve table. The output can be a tar/zip file, or it can be also the wget (curl) scripts to download them if too many images.
| 2 |
1,408 |
DM-7196
|
08/10/2016 20:02:10
|
Make a design document explaining the light-curve core server-side functions
|
We need a design schema document to identify and describe the core functions that will be commonly used by the Light-curve viewer as well as the inputs and outputs on: - getting the single exposure image - compute and getting a phase folded curve - compute and getting periodogram - getting the peaks table Those functions will be used by the processors DM-7162, DM-7164, DM-7165 via one or several Firefly 'search' processor. Would be also helpful to add the description on the expected table format and content that the (future) NexSci API will offer.
| 1 |
1,409 |
DM-7199
|
08/11/2016 11:18:03
|
afwTable's .getX()/.getY() do not appear in dir()
|
On a SourceCatalog, I can call {{cat.getX()}} or {{cat.getY()}} to return an array of pixel coordinates, but neither of these functions appear in {{dir(cat)}}. This breaks introspection and makes it difficult to know what other such magic functions exist (e.g., I can't tell if there is an equivalent for ra/dec).
| 2 |
1,410 |
DM-7203
|
08/11/2016 14:33:46
|
LDM-151 review meeting, 2016-08-08
|
Prepare materials for and participate in the meeting.
| 2 |
1,411 |
DM-7204
|
08/11/2016 14:34:25
|
LDM-151 review meeting, 2016-08-08
|
Prepare materials for and participate in the meeting.
| 2 |
1,412 |
DM-7205
|
08/11/2016 14:34:57
|
LDM-151 review meeting, 2016-08-08
|
Prepare materials for and participate in the meeting.
| 2 |
1,413 |
DM-7206
|
08/11/2016 14:35:14
|
LDM-151 review meeting, 2016-08-08
|
Prepare materials for and participate in the meeting.
| 2 |
1,414 |
DM-7207
|
08/11/2016 14:44:58
|
Modify afw tests to support pytest
|
This ticket is for the work of migrating the AFW tests such that they run with the py.test test runner.
| 8 |
1,415 |
DM-7208
|
08/11/2016 15:02:25
|
Minor fixes for issues flagged by Eclipse codan
|
Fix a few minor errors that were flagged by the Eclipse Neon C++ code analyzer.
| 0.5 |
1,416 |
DM-7212
|
08/11/2016 17:13:31
|
The feature 'lock-by-click' in the readout panel doesn't work
|
The feature 'lock-by-click' in the readout panel doesn't work, when checked, the readout doesn't display any value from any image click.
| 0 |
1,417 |
DM-7214
|
08/12/2016 04:43:46
|
Replace docker_spy by hostfile management
|
docker_spy is broken and breaks travis CI. It is now replace with raw hostfile management, simpler and more robust
| 2 |
1,418 |
DM-7221
|
08/12/2016 20:32:59
|
TUNIT header is not uniformly applied to columns in FITS table output from afw.table
|
In looking at the Source table outputs (SRC*.fits files) in the validation_data_hsc repository, we noticed that the headers are not consistently applied in the FITS files generated by afw.table output. In particular, the TUNIT keywords are missing for the coord_ra and coord_dec columns, making it difficult for a client to determine that the columns are persisted in units of radians, especially since the FITS convention is for the default units for angles to be degrees. {quote}KEYWORD: TUNITn REFERENCE: FITS Standard STATUS: reserved HDU: table VALUE: string COMMENT: column units DEFINITION: The value field shall contain a character string describing the physical units in which the quantity in field n, after any application of TSCALn and TZEROn, is expressed. The units of all FITS header keyword values, with the exception of measurements of angles, should conform with the recommendations in the IAU Style Manual. For angular measurements given as floating point values and specified with reserved keywords, degrees are the recommended units (with the units, if specified, given as 'deg').{quote} http://heasarc.gsfc.nasa.gov/docs/fcg/standard_dict.html Accepting that we are not conforming to that convention, the proper value for TUNITn is "rad" for data in units of radians. While much access to afw.table-produced files will be through the afw.table interfaces, where this issue is irrelevant as long as round-tripping is successful, for exploratory and debugging purposes it is very useful to be able to access the file contents with standard tools. In addition, if the FITS tables produced from afw.table are to be used as the input to the database ingest, providing units for all columns will assist the database system in providing and validating correct column metadata to its clients, whether through VO standards or other means.
| 1 |
1,419 |
DM-7225
|
08/13/2016 00:10:01
|
File upload function
|
Develop a file upload function: - upload FITS, VOtable, IPAC table, CSV file, ... - distinguish file type - list multiple extensions of FITS, to know the type (image or table) of each extension - display header information of each extension or the data accordingly
| 20 |
1,420 |
DM-7239
|
08/15/2016 18:41:40
|
Any table update ('reset', sorting..) will also reset image options
|
When table is updated after sorting or clicking on 'reset' option, the image is reset to default option. If you have a different color stretch/scale or zoom, the image gets reset to initial values loosing the operations applied. Updates: This is the case with coverage image only. On every table update, it will re-calculate the coverage, then redraw it with default options. Prior to conversion, coverage image also reset its options when it does a redraw. However, it only does a redraw when the catalog data have changed, like when filter is applied.
| 2 |
1,421 |
DM-7250
|
08/16/2016 18:02:23
|
Adapt display_ds9 to py3
|
Follow the steps in the [LSST 2016 presentation|https://project.lsst.org/meetings/lsst2016/sites/lsst.org.meetings.lsst2016/files/201608-LSST2016-py3.pdf] by [~tjenness] to update the Python code in the {{display_ds9}} package. This will be a learning exercise to prepare for updating {{display_firefly}} for SUIT.
| 1 |
1,422 |
DM-7253
|
08/17/2016 10:27:42
|
Modify db package to support python3
|
LSST2016 DM hack session for updating LSST code to support python3. Instructions: https://project.lsst.org/meetings/lsst2016/sites/lsst.org.meetings.lsst2016/files/201608-LSST2016-py3.pdf
| 1 |
1,423 |
DM-7259
|
08/17/2016 14:42:41
|
jenkins user listing and per user builds is unreliable
|
I'm seeing some odd behavior with /asynchPeople/ only listing a small number of the actual users. The list keeps refreshing itself with a different partial list. Possibly related, /user/<userid> isn't listing all builds for a users, in some cases, it lists no builds at all for users which should have 100s
| 1 |
1,424 |
DM-7260
|
08/17/2016 14:48:52
|
Modify cat package to support python3
|
LSST2016 DM hack session for updating LSST code to support python3. Instructions: https://project.lsst.org/meetings/lsst2016/sites/lsst.org.meetings.lsst2016/files/201608-LSST2016-py3.pdf
| 1 |
1,425 |
DM-7267
|
08/17/2016 17:15:31
|
Add array equality helpers to TestCase
|
afw.math added equality helper method, e.g. {{assertImageEqual}}, that just call the appropriate NearlyEqual method with tolerance of 0. It would be good to have equivalent "assertArrayEqual" and "assertArrayNotEqual" methods that wrap assertClose, which has some useful functionality (e.g. plotting) beyond what numpy.testing.allClose provides.
| 1 |
1,426 |
DM-7268
|
08/17/2016 20:24:29
|
Record source measurement time in the metadata
|
Currently the measurement of sources in {{processCcd.py}} and {{imageDifference.py}} is not wrapped by {{pipeBase.timeMethod}}, and thus the metadata does not record this processing time. Adding this wrapper will improve our ability to track processing speed improvements.
| 1 |
1,427 |
DM-7271
|
08/18/2016 14:39:35
|
Change default format for float and double to %g
|
DM-7271: table enhancements * do not apply default data format * introduce optional display format * add "AUTO" and "NONE" as format keywords. * for fits table, set display format to "%.9g" for double type. * add support for TDISPn fits table header * remove condition so temp files will not get written into source directory When reading fits table, set display format to "%.9g" for double if TDISPn is not given.
| 2 |
1,428 |
DM-7273
|
08/18/2016 15:15:40
|
Smaller readout switch to bigger one unexpectedly
|
Either in firefly demo page or in Gator, the small readout switch unexpectedly into the exanded bigger readout. Please, check that the readout size and information layout should stay constant consistently. (I could duplicate it but there is no clear pattern step by step to reproduce, but definitively i could see readout switching back and forth - maybe related to 'lock-by-click' problem)
| 1 |
1,429 |
DM-7274
|
08/18/2016 15:21:45
|
Although the table shows more than 1 position, xy plot displays 1 single datapoint
|
In IRSAViewer and Gator/Atlas: one single point is shown in XY Plot (RA vs. DEC) despite the fact that the table contains more points (see attached snapshot) Step to reproduce from IRSAViewer (external viewer from Atlas) or from Gator itself: Do a catalog search 'm82' on AllWise around 100 arcsec.
| 1 |
1,430 |
DM-7275
|
08/18/2016 15:40:57
|
Image expand mode had name of image at top left whereas migrated image view has "Tiled View"
|
Before migration, expanded single image had the name on top left corner. The current migrated view says 'Tiled View' which is not correct with the view itself. Please, add correct information of the expanded mode and/or the image name.
| 1 |
1,431 |
DM-7279
|
08/18/2016 16:32:39
|
Firefly table and xy plot 'reset' should returned default values
|
'reset' button before migration returned the initial default values, not the previous applied values. Please, restore function so 'reset' feature would give back the initial default values. For example, if table starts with 'show units', 50 rows per page, clicking 'reset' button should give back this values if user changed them before.
| 0.5 |
1,432 |
DM-7280
|
08/18/2016 16:55:14
|
Atlas: table scrambled values when few columns are selected
|
Atlas table has inconsistent values when a few columns are selected. Please fix. (Not happening in Gator btw)
| 2 |
1,433 |
DM-7295
|
08/19/2016 17:07:12
|
Get astrometry.net that works with Python 3
|
The current release of astrometry.net does not support Python 3. Upstream needs to be fixed.
| 2 |
1,434 |
DM-7299
|
08/19/2016 17:10:24
|
Check lmfit works with Python 3
|
lmfit is meant to work with Python 3 but this needs to be checked. Some code in the tree does not work with Python 3 but it is possible that this code is not used by LSST.
| 0 |
1,435 |
DM-7309
|
08/19/2016 17:20:26
|
Port obs_cfht to Python 3
|
This ticket covers the work required to get obs_cfht working with Python 3.
| 1 |
1,436 |
DM-7314
|
08/20/2016 09:33:32
|
Odd Jenkins failure
|
A Python 3 Jenkins build failed with a very unusual log full of "#" and no clear idea of what went wrong. https://ci.lsst.codes/job/stack-os-matrix/label=centos-7,python=py3/14730//consoleFull
| 1 |
1,437 |
DM-7317
|
08/21/2016 02:19:29
|
Log scale doesn't work with sample table attached
|
When using the attached sample ipac table with 2 columns 'period' and 'power' from 'Data Sets: Catalogs & Images' dialog (firefly viewer), the XY-plot display correctly the data 'period' vs. 'period. Changing Y axis to plot 'power' column and selecting 'log' scale, the axis disappear and nothing seems to be converted in log scale. An error message can be seen in the console related to highchart.js: highcharts.js:15 Uncaught Highcharts error #10: www.highcharts.com/errors/10P @ highcharts.js:15setTickInterval @ highcharts.js:16setScale @ highcharts.js:17(anonymous function) @ highcharts.js:18each @ highcharts.js:8setSize @ highcharts.js:18shouldComponentUpdate @ XYPlot.jsx:350updateComponent @ Please, investigate why and fix. Thanks!
| 2 |
1,438 |
DM-7324
|
08/22/2016 13:27:35
|
Port ci_hsc to Python 3
|
Work associated with ensuring that {{ci_hsc}} works with Python 3.
| 1 |
1,439 |
DM-7325
|
08/22/2016 13:34:50
|
Port meas_extensions_ngmix to Python 3
|
Work associated with adding support for Python 3 to {{meas_extensions_ngmix}}.
| 1 |
1,440 |
DM-7326
|
08/22/2016 13:35:09
|
Adapt FireflyClient (renamed to firefly_client.py) to Python 3
|
The stack is being adapted to work with Python 3 as well as Python 2. Following the guide from LSST2016 for porting packages to Python 3, adapt the FireflyClient API. This will allow afw.display to work with Firefly in a Python 3 stack.
| 2 |
1,441 |
DM-7327
|
08/22/2016 13:37:57
|
Check ngmix works on Python 3
|
Check that {{ngmix}} works on python 3.
| 1 |
1,442 |
DM-7328
|
08/22/2016 13:40:28
|
Port validate_drp to Python 3
|
This ports {{validate_drp}} to Python 2+3 compatibility. (Note that the work is still against the {{u/sqre/measurement-api}} integration branch until we can coordinate the coordinate the deployment with SQUASH.)
| 0.5 |
1,443 |
DM-7329
|
08/22/2016 14:03:46
|
Modify meas_extensions_photometryKron tests to support pytest
|
This ticket is for the work of migrating the meas_extensions_photometryKron tests such that they run with the py.test test runner.
| 0.5 |
1,444 |
DM-7332
|
08/22/2016 14:35:15
|
Modify meas_extensions_simpleShape tests to support pytest
|
This ticket is for the work of migrating the meas_extensions_simpleShape tests such that they run with the py.test test runner.
| 0.5 |
1,445 |
DM-7336
|
08/22/2016 16:46:16
|
Rotation of image display bug
|
The rotation of a z-scale log stretched or north-up image operation fails and changes the stretch. The image becomes black/white. That doesn't happen with linear stretch btw. It looks like a server -side problem. Step to reproduce: Either by searching from Spitzer GOALS images or just uploading the attached FITS file, then stretch on 'z-scale log', then rotate (45deg). The stretch changes. Same for north-up operation.
| 2 |
1,446 |
DM-7338
|
08/22/2016 19:03:13
|
Fix-up any code that uses butler.repository
|
See https://community.lsst.org/t/access-to-root-in-butler/991 When running constructBias.py in lsst_apps w_2016_34 I get the error: AttributeError in map: 'Butler' object has no attribute 'repository' The source of the error is probably https://github.com/lsst/pipe_drivers/blob/master/python/lsst/pipe/drivers/constructCalibs.py#L585 All code that uses butler.repository should be fixed. If that's too much work possibly the ticket could get changed to fix constructCalibs only for now.
| 2 |
1,447 |
DM-7341
|
08/23/2016 09:59:44
|
Handle lsst.utils.tests dependency better in testExecutables.py
|
The {{testExecutables.py}} script that allows py.test to run executable unittests requires lsst.utils.tests. Several packages such as sphgeom explicitly avoid making lsst.utils a dependency. Hence {{testExecutables.py}} is unable to reside inside the {{sphgeom}} package and {{py.test}} is unable to run the executable unittests for now. Figure out which is better: # Make sphgeom depend on lsst.utils # Remove the lsst.utils dependency from testExecutables.py
| 1 |
1,448 |
DM-7347
|
08/23/2016 12:45:50
|
Modify meas_deblender tests to support pytest
|
This ticket is for the work of migrating the meas_deblender tests such that they run with the py.test test runner.
| 0.5 |
1,449 |
DM-7350
|
08/23/2016 13:43:07
|
Cleanup ip_diffim's afwData test skipping
|
There are a number of {{if not self.defDataDir: print("skipping"); return}} blocks in the ip_diffim tests that should be converted to {{@unittest.skipIf}} decorators. Otherwise, those tests may silently not be run, which is bad.
| 1 |
1,450 |
DM-7352
|
08/23/2016 14:51:39
|
Prepare for testing the candidate technology for the alert distribution system
|
In order to test out the suggested candidate technology for alert distribution within the LSST system (Kafka) several activities need to be carried out. 1. Perform a literature review of relevant documents: Kafka paper and Comet paper at least 2. Answer relevant questions for setting up testing: e.g. * What are topics used for? * What partition sizes are optimal? * Time scales for tests? Product will be a short writeup of the literature review and any questions that came up and were resolved.
| 20 |
1,451 |
DM-7355
|
08/23/2016 15:11:22
|
Provide a set of parameters to measure and contexts to test
|
The tests will have clearly defined measurements and failure modes. We will need a tool for monitoring all the parameters. Example system params to measure: * latency and throughput * CPU usage * mem usage * network I/O * disk I/O Example distribution system tests: * Kafka node goes down * Vary rampup of producers * Vary message size * Vary message block size * Vary number of consumers Result will be a list of system parameters to monitor, a list of distribution system tests, and a tool to do the monitoring.
| 20 |
1,452 |
DM-7356
|
08/23/2016 15:13:16
|
Run test on prototype alert distribution and report on results
|
Tests are defined in DM-7355, but should be done in a staged way to increase the complexity of the system to test scaling. Not all test scenarios need to be tested with each configuration. A scheme like the following could work: # Test 1: Mac with single server, 189 prodcuers #* 1 consumer #* 10 consumers #* 100 consumers # Test 2: Mac with 3 servers, 189 producers #* 1 consumer #* 10 consumers #* 100 consumers # Test 3: on big Nebula virtual machine with single server, 189 producers #* 1 consumer #* 10 consumers #* 100 consumers # Test 4: on one Nebula virtual machine with 3 servers, 189 producers #* 1 consumer #* 10 consumers #* 100 consumers # Test 5: 3 Nebula virtual machines #* 189 producers within Nebula: 1, 10 and 100 consumers internal to Nebula #* 189 external producers: 1, 10, 100, and N consumers both internal and external to Nebula Product will be a DMTN on the results of using Kafka as the backend technology for supporting the internal alert distribution system.
| 20 |
1,453 |
DM-7358
|
08/23/2016 15:32:03
|
Modify meas_modelfit tests to support pytest
|
This ticket is for the work of migrating the meas_modelfit tests such that they run with the py.test test runner.
| 0.5 |
1,454 |
DM-7372
|
08/24/2016 06:59:14
|
Add information on milestone relationships to DMTN-020
|
Per [this discussion of LDM-472|https://github.com/lsst/LDM-472/commit/5ad5f731463cb0b17f8919c6d6016e63441b0a2e#commitcomment-18628148], please add material to DMTN-020 about relationships between milestones.
| 1 |
1,455 |
DM-7376
|
08/24/2016 09:57:48
|
Failure to identify location of clear supernova in a subtraction
|
I've run a subtraction of two images, one with a clear supernova (SNR~100), the other taken a year later. The supernova shows up very clearly, but does not get properly identified by the object detection and measurement. If run with {{config.doMerge=False}} then I get the first attachment, which shows the identification of a footprint in which the SN is found, but the X, Y position are set to be the presumably the first object that went in to the footprint. It's not re-centered at the SN. If I run with {{config.doMerge=True}}, then I get the third attachment, in which I believe the SN has been subsumed into the larger object of the dipole at the galaxy center. Some notes 1. There is significant galaxy background (that's what I wanted to do the subtraction). This changes the noise properties and, from my understanding of a discussion on Hipchat, breaks assumptions made by the de-correlation step. 2. These images are from a NIR detector, so they are created from a sequence of raw images in a grid dither pattern, which have been processed and combined to make these final images. This means that the noise varies significantly across the image, from the center which is covered by all raw images, to the corners which are each just covered by one. To recreate on lsst-dev.ncsa.illinois.edu: Set up the LSST stack + some custom branches in {{pipe_tasks}}, {{ip_diffim}}, {{obs_file}}: {code} . ~wmwv/.bashrc.lsst {code} {code} WIYN=/lsst8/wmwv/WIYN imageDifference.py ${WIYN}/test_dr1 --id fileroot=SN2011gy_A_H_20111115 --templateId fileroot=SN2011gy_A_H_20121028 --output ${WIYN}/test_dr1 --configfile ~wmwv/wiyn/diffimconfig.py --logdest wiyn_imageDifference.log --clobber-config --clobber-versions {code} If you're testing for yourself, you may wish to change the output repo to your own cusomt repo so we don't accidentally confuse each other with various runs. The active parts of {{diffimconfig.py}} are {code} config.doUseRegister=False config.convolveTemplate=True config.doWriteMatchedExp=True config.doDecorrelation=True config.doMerge=True config.subtract.kernel.name='AL' from lsst.ip.diffim.getTemplate import GetCalexpAsTemplateTask config.getTemplate.retarget(GetCalexpAsTemplateTask) {code} For a quick start, the following will display the images: {code} ds9 /lsst8/wmwv/WIYN/test_dr1/calexp/SN2011gy_A_H_{20111115,20121028}.fits /lsst8/wmwv/WIYN/test_dr1/diff/SN2011gy_A_H_20111115/diffexp.fits {code}
| 8 |
1,456 |
DM-7379
|
08/24/2016 13:14:29
|
random seed not run in command line test
|
In the conversion of ip_diffim to pytest a random.seed was moved to inside the setup_module function as opposed to the seUp method. When run from the command line (for example using Jenkins) this test can fail.
| 1 |
1,457 |
DM-7384
|
08/24/2016 14:56:06
|
Modify obs_lsstSim to support py.test
|
Migrate the {{obs_lsstSim}} tests such that they run with the {{py.test}} test runner.
| 0.5 |
1,458 |
DM-7386
|
08/24/2016 15:10:27
|
Jenkins/lsstsw no longer seems to build optional dependencies in all cases
|
If I ask Jenkins (or {{lsstsw}}) to build {{skymap}} the optional dependency of {{healpy}} is not included in the build. If I try to build {{afw}} it does include the optional dependencies of {{pyfits}}, {{matplotlib}} and {{afwdata}}. {{pipe_base}} does bring in its optional dependencies as well. I haven't worked out what is "special" about {{skymap}}. For an example Jenkins build: https://ci.lsst.codes/job/stack-os-matrix/label=centos-7,python=py3/14837//console Table file: {code} setupRequired(numpy) setupRequired(afw) setupOptional(healpy) {code}
| 0.5 |
1,459 |
DM-7387
|
08/25/2016 07:49:09
|
Modify obs_decam to support py.test
|
Migrate the {{obs_decam}} tests to support py.test
| 0.5 |
1,460 |
DM-7392
|
08/25/2016 10:16:20
|
More LDM-151 Review Updates
|
Implement changes identified in walking through the Algorithmic Components and Software Primitives sections with [~swinbank] and [~krughoff].
| 1 |
1,461 |
DM-7405
|
08/26/2016 15:45:09
|
Add VOTable support when uploading table
|
Uploading a votable result from simple cone search is not currently supported. We should provide VOTable xml file as part of the format supported by table upload. Make sure that it handle also VOTable with BINARY2 encoding (attached sample from Gaia DR1).
| 8 |
1,462 |
DM-7415
|
08/29/2016 09:38:56
|
Port dax_dbserv to Python 3
|
Work related to porting {{dax_dbserv}} to Python 3.
| 0.5 |
1,463 |
DM-7416
|
08/29/2016 09:39:49
|
Port dax_imgserv to Python 3
|
Work related to porting {{dax_imgserv}} to Python 3.
| 2 |
1,464 |
DM-7417
|
08/29/2016 09:40:30
|
Port dax_metaserv to Python 3
|
Work related to porting {{dax_metaserv}} to Python 3.
| 0.5 |
1,465 |
DM-7418
|
08/29/2016 09:41:22
|
Port dax_webserv to Python 3
|
Work related to porting {{dax_webserv}} to Python 3.
| 0.5 |
1,466 |
DM-7419
|
08/29/2016 09:42:11
|
Port dax_webservcommon to Python 3
|
Work related to porting {{dax_webservcommon}} to Python 3.
| 0.5 |
1,467 |
DM-7424
|
08/29/2016 13:26:45
|
Rework joint photometric calibration in LDM-151
|
The current text in LDM-151 for joint calibration (by [~pyoachim]) mostly concerns global calibration, but references to it in the DRP pipelines section assume we'll use Gaia for global calibration. I'll try to resolve that discrepancy with minimal modification on this issue, and then ask [~zivezic] and [~rhl] to review.
| 1 |
1,468 |
DM-7425
|
08/29/2016 14:11:39
|
Port pipe_supertask to Python 3
|
Work for porting {{pipe_supertask}} to Python 3.
| 1 |
1,469 |
DM-7429
|
08/29/2016 17:39:06
|
Publish LSE-163 to LSST the Docs
|
The treatment will be a static HTML landing page, similar to ldm-151.lsst.io
| 0.5 |
1,470 |
DM-7433
|
08/29/2016 19:00:01
|
Create test case for processFile
|
Add a testing suite to {{processFile}}. Specifically create a simple test case that verifies that {{processFile.py}} runs on a known set of test data. Optionally create simple additional tests if any occur. Implementation Plan 1. This test data will be from {{afwdata}}, as this adds minimal dependencies. See https://community.lsst.org/t/should-i-take-example-test-files-from-afwdata-or-obs-test-to-write-a-test-case-for-processfile/1101/2 for a bit of discussion. 2. The dependency on {{afwdata}} will be {{setupOptional}}. A user shouldn't have to download {{afwdata}} just to run {{processfile}}, but we will want to run this test as part of our regular Jenkins builds and CI efforts to make sure things don't get broken. Tests of performance against a known standard will be deferred to the {{lsst_ci}} package.
| 2 |
1,471 |
DM-7436
|
08/30/2016 07:24:05
|
Cleanup in admin/tools
|
Remove obsolete files and directories and update documentation. See: - admin/tools/cluster/ - admin/tools/*
| 2 |
1,472 |
DM-7437
|
08/30/2016 09:38:03
|
Fix eupspkg command for qserv containers
|
A bug was introduced during DM-6444. Fix is provided here.
| 2 |
1,473 |
DM-7442
|
08/30/2016 12:35:50
|
Write unit tests for DCR template generation code
|
DM-5697 and DM-6249 created code that generates DCR-matched template images for image subtraction. These functions should have unit tests.
| 8 |
1,474 |
DM-7444
|
08/30/2016 12:41:31
|
Improve jointcal plotting backend
|
While working on the jointcal quiver plots, etc. I made all the plots with the default, interactive, backend. Now that I need to use larger datasets on lsst-dev, interactive mode won't work, but would be useful to keep as an option. I had started to convert to using Agg during the All Hands Meeting, but got stuck on some strange interactions with quiver. This story is to capture the work I started on it, and to finish cleaning up that code. It might even be worth lifting the plotting code out of the tests, now that they're becoming more complicated. It would be useful to be able to generate these plots during non-testing jointcal runs. This might be a good opportunity to develop the "unified plotting abstraction layer" described in DM-5790.
| 8 |
1,475 |
DM-7445
|
08/30/2016 12:45:27
|
DCR template generation speed improvements
|
The current DCR template generation code takes approximately 30s per pixel on a single core to run. This code needs to be optimized to run much faster.
| 8 |
1,476 |
DM-7447
|
08/30/2016 13:50:17
|
Run DCR template generation on real data
|
The DCR template generation code has been developed and tested using simulated data. It would be informative to try running it on real data to identify new issues and see if it works.
| 2 |
1,477 |
DM-7448
|
08/30/2016 16:05:11
|
Table reset unset option 'Show unit' initially set
|
Reset feature works ok as expected unless if the table is created with 'show unit' option checked initially reset button will unset the option when it shouldn't changed it. Please investigate and fix. The problem can be shown in the table with filters and units on by default here: http://localhost:8080/firefly/demo/ffapi-highlevel-test.html
| 1 |
1,478 |
DM-7450
|
08/30/2016 17:27:59
|
Update coding standard to reflect non-executable tests (RFC-215)
|
Following the discussion at RFC-215, we need to update the developer guide to reflect that python tests should not be executable, nor have a shabang at the top. This is probably a few sentences to the python [testing portion|https://developer.lsst.io/coding/python_testing.html] part of the dev. guide, possibly in a new subsection at the end.
| 0.5 |
1,479 |
DM-7455
|
08/30/2016 18:13:57
|
Scale up Kafka alert producers
|
Figure out how to use Docker compose or something similar to easily scale up from one producer to 189 producers, one per CCD.
| 5 |
1,480 |
DM-7456
|
08/30/2016 18:15:01
|
Scale up Kafka alert consumers
|
Use Docker compose or something similar to easily scale up from one Kafka alert consumer to N consumers.
| 2 |
1,481 |
DM-7458
|
08/31/2016 12:47:52
|
Cannot add base_GaussianFlux to the list of default plugins in DipoleFitTask.
|
The DipoleFitTask plugin in ip_diffim currently registers a number of default measurement tasks. However, if base_GaussianFlux is registered, the following error is produced: Alias for 'slot_Shape_flag' must be defined before initializing 'base_GaussianFlux' plugin. {0} lsst::pex::exceptions::LogicError: 'Alias for 'slot_Shape_flag' must be defined before initializing 'base_GaussianFlux' plugin.' Track this down and fix it so that we can add base_GaussianFlux to the default list.
| 2 |
1,482 |
DM-7460
|
08/31/2016 14:33:42
|
No help link/anchor option XY-plot component
|
Table component has an option to add a link to onlinehelp for table documentation. Xy-plot is missing this feature and need an anchor to link to xy-plot help dcumentation. Please add to the API a way to pass a help-id property and add an anchor in the toolbar.
| 2 |
1,483 |
DM-7461
|
08/31/2016 14:37:45
|
afw test suite fails in the absence of afwdata
|
Running a fresh build of afw master on os x fails on two unit tests. One is in testExecutables.py and is related to not finding AFWData. On my system AFWData is not installed and the test should be skipped, but is still run. The other is DM-7474.
| 0.5 |
1,484 |
DM-7464
|
08/31/2016 16:09:50
|
Repackage Firefly Python API in its own pip-installable repository
|
After a discussion between [~gpdf], [~xiuqin] and [~shupe], there is a strong rationale for separating the FireflyClient API into its own repository (not combined with widgets): * FireflyClient has very few dependencies, while {{firefly_widgets}} already depends on Astropy and more dependencies may be added. * FireflyClient is pure Python, while {{firefly_widgets}} includes both Javascript and Python. The proposal is to move FireflyClient out of the {{firefly}} repository and into its own repository {{firefly_client}}. -Within this repository, FireflyClient needs to be packaged to be pip-installable via {{pip install firefly_client}}.- -To conform to Python module naming conventions, the module needs to be all lower-case, so that the users will import the class with something like {{from firefly_client import FireflyClient}} after it has been installed.- Examples of using the Python API could be included in an {{examples}} subdirectory in this repository.
| 2 |
1,485 |
DM-7465
|
08/31/2016 16:34:59
|
Add requirement annotations to DPDD
|
When linking items in DPDD to requirements and design documents, we need to provide anchor links that can be referenced outside of DPDD and which are guaranteed not to change. Section numbers and "item 5 in list on page 3" are not acceptable anchors. Explicit numbers will be assigned as margin notes to requirements-like items in DPDD.
| 20 |
1,486 |
DM-7470
|
08/31/2016 19:06:55
|
Firefly viewer (and IRSAVIewer) shows an extra coverage tab when doing a catalog search
|
Once the viewer shows an image search or externally calling the viewer to expand an image previously displayed, it will display a coverage image (extra tab) after doing a catalog search. In IRSAVIewer, this is inconsistent with previous flow and appearance, a catalog search expect to return and overlaid on top of the previously image displayed. Coverage shouldn't appear if an image is already loaded and a search catalog is triggered. Plus, when the user get rid off the catalog, the image left is the selected image (could be the added coverage image). At some point, this was working as before but the flow had changed. Please, restore the way it was before, no coverage after doing a catalog search when an image is already loaded from image search or pushed externally to the viewer.
| 1 |
1,487 |
DM-7492
|
09/01/2016 17:02:01
|
Load calexps into PDAC
|
Igor has located calexps, and begun work to stage them to NCSA. Figure out final location in PDAC needed to support imgserv, transfer images there, and drop duplicates.
| 8 |
1,488 |
DM-7494
|
09/01/2016 17:07:54
|
PDAC imgserv Butler configuration
|
Address butler configuration for imgserv to it can access calexps within PDAC
| 8 |
1,489 |
DM-7503
|
09/02/2016 08:38:58
|
Discuss deblender requirements with stakeholders
|
Chat with stakeholders in the deblender (at least RHL, Jim Bosch) to get a better feeling for their vision of how it should be developed in the future. Understand the architectural requirements for multi-band deblending.
| 2 |
1,490 |
DM-7504
|
09/02/2016 08:41:15
|
Compile list of missing or inadequate deblender functionality
|
As part of DM-3622, we aim to make the single-band deblender equal to "the state of the art". What does this mean in practice? Compile a list of features we need to add (the SDSS anti-shredding algorithm is the canonical example; are there others?) and pathological behaviour that we need to fix. Ensure they're all programmed into the epic as stories.
| 1 |
1,491 |
DM-7509
|
09/02/2016 12:44:04
|
Logging system sensitive to %s in string
|
There are two bugs in the log package: log.info("%s") results in: {code} TypeError: not enough arguments for format string {code} this is because Log._log is defined with this line: {code} self.log(level, os.path.split(frame.f_code.co_filename)[1], inspect.stack()[2][3], frame.f_lineno, fmt % args) {code} and in this case args is an empty tuple. A trivial fix is to replace this with: {code} msg = fmt % args if args else fmt self.log(level, os.path.split(frame.f_code.co_filename)[1], inspect.stack()[2][3], frame.f_lineno, msg) {code} However, doing so exposes another bug. The following will segfault: {code} log.log(2000, "foo", "bar", 5, "%s") {code} This is because Log.log is extended in logLib.i as follows: {code} void log(int level, std::string const& filename, std::string const& funcname, unsigned int lineno, std::string const& msg) { self->log(log4cxx::Level::toLevel(level), log4cxx::spi::LocationInfo(filename.c_str(), funcname.c_str(), lineno), msg.c_str()); {code} and the version of Log.log it calls expects additional format arguments. In general the log package seems to use {{logMsg}} when no {{%s}} formatting is wanted, and {{log}} when such formatting is wanted, so I propose to fix this using: {code} void logMsg(int level, std::string const& filename, std::string const& funcname, unsigned int lineno, std::string const& msg) { self->logMsg(log4cxx::Level::toLevel(level), log4cxx::spi::LocationInfo(filename.c_str(), funcname.c_str(), lineno), msg.c_str()); {code} In addition, this requires the first fix to be changed to call {{logMsg}} instead of {{log}}
| 2 |
1,492 |
DM-7510
|
09/02/2016 13:18:55
|
Add support for HSC-R2 filter
|
Port of [HSC-1419|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1419].
| 0.5 |
1,493 |
DM-7511
|
09/02/2016 13:32:36
|
Firefly API JSDoc build in Jekins
|
We need to add JSDoc generation in Jekins build and bundle it in the firefly.war file when we make Firefly release.
| 2 |
1,494 |
DM-7512
|
09/02/2016 13:35:17
|
obs packages need a unified test framework
|
The various obs* package test cases should derive from a set of parent TestCases, so that they all trivially have the same testing functionality. obs_decam has more tests written for it than most of the other packages, but most of those tests could be lifted into some higher package, with the obs_decam test looking like, e.g. {code} ...boilerplate... class GetIdTestCase(obs_test_helper.tests.IdTestCase): def setUp(self): self.mapper = DecamMapper(root=".") super(GetIdTestCase, self).setUp() self.dataId = {'visit'=229388, 'ccdnum'=13, 'filter'='z'} self.result_id = 22938813' ...boilerplate... {code} with all of the test* methods living {{obs_test_helper.tests.IdTestCase}}. This is just a sketch of a design, but I think it would both simplify deploying new obs packages and allow us to almost trivially improve testing coverage in the existing packages.
| 40 |
1,495 |
DM-7518
|
09/03/2016 09:21:43
|
Wrap log package with pybind11 instead of swig
|
The {{log}} package was recently added as a future replacement for {{pex_logging}}. Wrap this package with pybind11 instead of swig.
| 2 |
1,496 |
DM-7520
|
09/03/2016 20:34:54
|
XY plot is not shown after closing one of the catalog tab
|
When 2 or more catalog search result tables are shown, the XY-plot displays the table selected. If one click on another tab, the xy-plot refresh and gets updated correctly plotting the table datapoints automatically. If the user close the table, the next table gets focused and one expect to see the xy-plot to be updated. The xy-plot doesn't refresh and shows empty grey background. Please, investigate and fix.
| 2 |
1,497 |
DM-7521
|
09/03/2016 22:18:50
|
Add image feature in the image viewer toolbar is inconsistent when single image
|
The toolbar of the image viewer shows a button to add or replace an image ('plot'). The option 'Create new plot' doesn't work when the viewer shows a single image without the 'grid'/'single' image expand mode toolbar (that happen for example in Gator but can be seen in demo page higher level API test). The lock image feature is also not needed when only one image is shown. The toolbar is different in Gator in OPS than it is in the migrated version. Please check the inconsistency and fix the toolbar. 9/7/2016 Xiuqin WU After discussion today, the decision is to make the "Create new plot" option work when the "Add image" icon (the one with + sign) in both the normal mode and expanded mode. Leave the lock icon as is.
| 1 |
1,498 |
DM-7523
|
09/05/2016 10:16:17
|
obs_sdss test should not print outside of test
|
In DM-7346 the {{testSelectSdssImages.py}} test was modified to skip if a server was unavailable but the reason for the lack of availability was printed to standard error at the module level. This print is not captured by pytest (it only captures test output). The reason has to be moved inside the skip message.
| 1 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.