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,199 |
DM-6028
|
05/09/2016 10:05:53
|
Validation is not performed on unchanged fields
|
Currently, validation is performed only if a field has changed. We need to be able to validate all fields on form submit. The issue is not limited to initial (ex. empty) value being invalid. The invalid message is lost when a field is unmounted/re-mounted. You can test the following way: - http://localhost:8080/firefly/;a=layout.showDropDown?view=AnyDataSetSearch - Open chart settings, enter 1000 into X/Y ratio - the field is shown as invalid - Switch to histogram and back, the invalid message is gone, the field appears to be valid Another test case is Example Dialog tab 'X 3', 'X 3' tab test field initial value 88 is invalid (it should be between 22 and 23), but it appears valid.
| 2 |
1,200 |
DM-6029
|
05/09/2016 10:08:05
|
Error message is not shown
|
The error message is not showing consistently when mouse is over tha exclamation icon.
| 1 |
1,201 |
DM-6030
|
05/09/2016 10:32:39
|
Investigate possibilty of cosmic ray muons (etc) for precision gain calibration
|
In the era of CBPs, we care about absolute system throughput, and thus need to accurately know the gain of amplifiers in the CCDs. Initially, this can be done by lab-based Fe55 characterisation (modulo the non-linearity, though that itself will need to be need to be characterised and corrected for), but changes in the relative gains of the various amplifiers need to be monitored, and this must be done in a way that is not degenerate with the optical transmission in any way. Theoretically it should be possible to use cosmic ray muon tracks, and tracks from radioisotope contamination of the glass/dewar, to measure the (change in the) relative gains of the amplifiers. Early work has shown that this does work in principle, but this ticket is for some further effort to see whether this method can provide the necessary accuracy given the amount of data available remains to be seen. This ticket would normally need to be significantly more points, but as it builds on earlier work, it can, at least for initial results, be done quite cheaply. Initial investigation will inform further work, which will be carried out in S17 as DM-8276.
| 8 |
1,202 |
DM-6036
|
05/09/2016 11:42:32
|
Produce and ingest master calibs for USNO monocam data.
|
Use the construct*.py scripts added to pipe_drivers to produce temporally relevant master biases, darks, flats (and fringe frames?) for the recent USNO observing with monocam. A small amount of hacking will be required due to the fact that the current ingestion model assumes that each CCD frame has a USNO counterpart which tells about the telescope pointing etc, but the bias frames do not have these. Once the master calibs are produced, get them ingested.
| 2 |
1,203 |
DM-6037
|
05/09/2016 11:50:43
|
Reduce sky data from USNO monocam run
|
Using the master calibs produced in DM-6036, push all the monocam data through processCcd. Others will run sanity checks on the output (initial astrometry & photometry). From there I believe people will look at using the data to test jointcal & sim_astrom etc, but this ticket just related to the initial reduction. As more data comes in from the 2nd telescope, a little further hacking may be necessary to keep everything running. Some of this will likely be hacky or need one-off solutions/header modification, hence the higher-than-normal number of story points assigned to what one might expect to be an hour-long job.
| 3 |
1,204 |
DM-6041
|
05/09/2016 12:16:01
|
Functional use cases for light curve
|
Work with Vandana Desai (IRSA) to tabulate science use cases for tools. Then transform the science use cases to functional use cases ("this is how we want the tool/interface to behave"). This work is to identify common functional and scientific use cases between PTF/ZTF and LSST to inform LSST on how the SUIT web portal might be organized for user interaction with LSST data.
| 1 |
1,205 |
DM-6044
|
05/09/2016 13:01:29
|
Add LoadReferenceObjectsTask to task documentation page
|
The documentation for {{LoadReferenceObjectsTask}} should show up on the task documentation page, despite its being an abstract base class.
| 0 |
1,206 |
DM-6045
|
05/09/2016 14:46:48
|
Nominal PSF required by processCcd
|
After the processCcd refactor, non-sky images, or, in general, images for which an initial PSF estimate cannot be made, cause {{ProcessCcdTask}} to fail if {{config.doCalibrate=True}}. To work around this, I put a dirty hack at line 157 of my {{processCcd.py}}: {code} from lsst.meas.algorithms.installGaussianPsf import InstallGaussianPsfTask, FwhmPerSigma task = InstallGaussianPsfTask() task.config.fwhm = 1.0 * 3.53223006755 task.run(exposure=exposure) measFwhm = exposure.getPsf().computeShape().getDeterminantRadius() * FwhmPerSigma {code} to ensure that there would always be kind of PSF. This should be redone in a way that someone who knows what they're doing approves of.
| 2 |
1,207 |
DM-6048
|
05/09/2016 16:07:02
|
Bundle up more HSC data for validate_drp
|
We would like to include a larger set of HSC data for validation. I tested this while in Tucson. My working dir was {{/tigress/pprice/frossie}}. The raw and processed data should be stuffed into validation_data_hsc
| 3 |
1,208 |
DM-6050
|
05/09/2016 16:11:21
|
Table caching optimizations
|
We need to avoid duplicate requests which result from minor differences in TableRequest parameters, which are not used to get data. For example, loading catalog table, which triggers table statistics, and then getting an XY plot, results in 3 requests, returning identical data. 1. RequestClass=ServerRequest; *tbl_id=tbl_id-1;* UserTargetWorldPt=10.68479;41.26906;EQ_J2000;m31;ned; SearchMethod=Cone; catalog=wise_allwise_p3as_psd; RequestedDataSet=wise_allwise_p3as_psd; radius=200; use=catalog_overlay; catalogProject=WISE 2. RequestClass=ServerRequest;RequestedDataSet=wise_allwise_p3as_psd; catalog=wise_allwise_p3as_psd; use=catalog_overlay; UserTargetWorldPt=10.68479;41.26906;EQ_J2000;m31;ned; catalogProject=WISE; radius=200; SearchMethod=Cone 3. RequestClass=ServerRequest; *tbl_id=xyplot-tbl_id-1;* catalog=wise_allwise_p3as_psd; use=catalog_overlay; UserTargetWorldPt=10.68479;41.26906;EQ_J2000;m31;ned; SearchMethod=Cone; RequestedDataSet=wise_allwise_p3as_psd; catalogProject=WISE; radius=200; *decimate=decimate=ra,dec,10000,1,,,,* The difference between 1 and 2 is tbl_id parameter. The difference between 2 and 3 is tbl_id and decimate parameters. As well as the order of the parameters. None of which change the catalog search result. Test Case: Test Searches, Test catalog, AllWISE Source, radius=200
| 2 |
1,209 |
DM-6051
|
05/09/2016 16:12:24
|
Add extendedness vs. star selector test to single-visit validation in ci_hsc
|
ci_hsc has a test that verifies that extendedness as measured on coadds broadly agrees with the star selection done for PSF estimation on individual frames. This tests a bunch of stuff, including aperture corrections on the coadds and propagation of flags from visits to coadds. It doesn't test that aperture correction vs. extendedness logic is correct in processCcd.py, but just copying this test to the appropriate validation function in ci_hsc should do the trick. This is currently broken, but should be fixed in DM-5877.
| 2 |
1,210 |
DM-6054
|
05/10/2016 10:35:46
|
Minor updates in suptertask from following DMTN-002
|
Some examples in the DMTN-002 seem slightly out of date. Update supertask documentation and code to catch up with some recent developments in the stack.
| 2 |
1,211 |
DM-6063
|
05/11/2016 15:03:25
|
Fix how aperture correction is applied
|
[~lauren] committed a fix Jan 15 to how aperture correction is applied that I accidentally lost when refactoring in DM-4692. https://github.com/lsst/pipe_tasks/commit/d904e3d188698b4f57bf3dad1516b0bf201078f5 Restore the fix. The need for this fix suggests a design flaw in measurement that will be fixed as part of DM-5877
| 1 |
1,212 |
DM-6067
|
05/11/2016 18:32:58
|
S17 Butler DB storage
|
Initial implementation to be read-only, DB -> in-memory AFWTable. DB connection info to reside in repository config. Query substitution elements to be taken from data id.
| 40 |
1,213 |
DM-6074
|
05/12/2016 11:00:32
|
Add RegistryField support to Task.makeSubtask
|
As part of implementing RFC-183 add support for tasks specified in {{lsst.pex.config.RegistryField}} to {{lsst.pipe.base.Task.makeSubtask}}
| 2 |
1,214 |
DM-6075
|
05/12/2016 11:06:51
|
Document the need for abstract base tasks for tasks
|
As part of RFC-183 document the fact that variant tasks should have a common abstract base class that defines the API. If we add future tasks that we feel are likely to have variants, then we should create an abstract base class. Candidates include star selectors, PSF determiners and ISR tasks. Note that this applies to tasks LSST provides in its stack, not to variants users produce and other obscure one-off code. Also document the desire that tasks with anticipated many variants, such as star selectors, and PSF determiners should be in registries. This explicitly excludes tasks such as ISR where only one task is likely to be useful for a given set of data.
| 2 |
1,215 |
DM-6077
|
05/12/2016 11:15:20
|
Change PSF determiners into tasks
|
PSF determiners are already configurables, and some benefit from having a log. Take the logical next step and make them instances of {{lsst.pipe.base.Task}}.
| 1 |
1,216 |
DM-6078
|
05/12/2016 13:15:51
|
Aperture correction fails to measure a correction for the final plugin in the list and reports misleading errors
|
Since the refactoring of DM-4692, runs of *processCcd.py* detail the following in their logs: {code:title=With base_PsfFlux and base_GaussianFlux plugins registered} processCcd.charImage.detectAndMeasure.measureApCorr WARNING: Only 0 sources for calculation of aperture correction for 'base_PsfFlux'; setting to 1.0 processCcd.charImage.detectAndMeasure.measurement: Measuring 65 sources (65 parents, 0 children) processCcd.charImage.detectAndMeasure.measurement.applyApCorr: Applying aperture corrections to 1 flux fields processCcd.charImage.detectAndMeasure.measurement.applyApCorr: Use naive flux sigma computation ... processCcd.calibrate.detectAndMeasure.measurement.applyApCorr: Applying aperture corrections to 2 flux fields processCcd.calibrate.detectAndMeasure.measurement.applyApCorr: Use naive flux sigma computation processCcd.calibrate.detectAndMeasure.measurement.applyApCorr WARNING: Could not find base_GaussianFlux_flux or base_GaussianFlux_fluxSigma in apCorrMap {code} {code:title=With base_PsfFlux, base_GaussianFlux, and ext_photometryKron_KronFlux plugins registered} processCcd.charImage.detectAndMeasure.measureApCorr: Measuring aperture corrections for 2 flux fields processCcd.charImage.detectAndMeasure.measureApCorr WARNING: Only 0 sources for calculation of aperture correction for 'base_PsfFlux'; setting to 1.0 processCcd.charImage.detectAndMeasure.measureApCorr WARNING: Only 0 sources for calculation of aperture correction for 'base_GaussianFlux'; setting to 1.0 processCcd.charImage.detectAndMeasure.measurement.applyApCorr: Applying aperture corrections to 2 flux fields processCcd.charImage.detectAndMeasure.measurement.applyApCorr: Use naive flux sigma computation ... processCcd.calibrate.detectAndMeasure.measurement.applyApCorr: Applying aperture corrections to 3 flux fields processCcd.calibrate.detectAndMeasure.measurement.applyApCorr: Use naive flux sigma computation processCcd.calibrate.detectAndMeasure.measurement.applyApCorr WARNING: Could not find ext_photometryKron_KronFlux_flux or ext_photometryKron_KronFlux_fluxSigma in apCorrMap {code} I can confirm that for the latter, running HSC data with the fix on DM-6063, the aperture corrections are being measured and applied for the PsfFlux and GaussianFlux measurements, but NOT for the KronFlux measurements. Looking at the output from the current "expected" values for the {{lsst_dm_stack_demo}} we see that there is an offset in the Psf-Gaussian fluxes, implying the Gaussian fluxes are not being measured (and hence not applied): !demo_current.png|width=500! From this I conclude that the aperture corrections are indeed being measured for all but the final entry in the plugin list. This implies that the report of "Only 0 sources for calculation of aperture correction for 'xxx_xxFlux'; setting to 1.0" is incorrect for all but the final plugin measurement. The demo previously successfully calculated aperture corrections and, after the logic fix of DM-4836, applied them in the correct order: !demo_previous.png|width=500! The sources of these issues and fixes for them are the goal of this issue.
| 2 |
1,217 |
DM-6082
|
05/13/2016 09:31:43
|
Add Sublime Text configuration tips to Developer Documentation
|
[~rowen] and [~Parejkoj] have some good tips about setting up Sublime Text. [~jsick] suggested that we add these configuration tips to the Developer Documentation. http://developer.lsst.io/en/latest/#part-tools Both want to include info about recommended packages, but also the linter configurations to support the DM styles. I paste in here various helpful parts from the HipChat Software Development room discussion of this. Both verbatim, and summarized. 1. Install {{Package Control}} 2. Packages: {{Git}}, {{GitGutter}}, {{SideBarEnhancements}}, {{SublimeLinter}}, {{SublimeLinter-flake8}}, {{SublimeLinter-html-tidy}}, {{SumNumbers}}, {{Gist}}, {{BracketHighlighter}}, {{TrailingSpaces}}, {{Trimmer}}, {{OmniMarkupPreviewer}}, {{ReStructuredTextImproved}}, {{MarkDown Editing}}, {{Colorsublime}} 3. Themes: {{Sunburst}} color scheme * VIM users: {{Vintageous}} + Mac OS X configuration: {{defaults write com.sublimetext.3 ApplePressAndHoldEnabled -bool false}} so that holding down 'j' moves downward. Note that {{Vintageous}} is not a complete implementation of {{vim}}, but it at least allows enough basics so that one doesn't go crazy switching back and forth. link the {{subl}} command to {{/usr/local/bin}} Quick Tips: "option-select (to select blocks) and select something then cmd-D are both extremely useful for modifying lots of things at once." "Similarly, ctrl-shift-up/down arrow." "cmd-click on multiple lines to have multiple synchronized cursors" Configurations: 1. [~rowen]'s SublimeText Preferences file: https://jira.lsstcorp.org/secure/attachment/27846/Preferences.sublime-settings 2. Configuration {{flake8}} so that it works in the linting can take a bit of work if {{flake8}} isn't in your default path. See SublimeLinter.sublime-settings attachment for [~rowen]'s configuration: https://jira.lsstcorp.org/secure/attachment/27845/SublimeLinter.sublime-settings The above are useful, but we'll need someone to detail the linter stuff more.
| 1 |
1,218 |
DM-6083
|
05/13/2016 09:45:56
|
Enable websocket client to pickup channel parameter from url
|
send websocket channel information via url. keep channel information on browser reload. This is needed for Firefly Python API and external (when Firefly viewer is invoked trough URL) API.
| 1 |
1,219 |
DM-6084
|
05/13/2016 09:50:48
|
meas_algorithms cannot be built with XCode 7.2.1
|
The LSST stack fails to build on OS X 10.10 "Yosemite" using XCode 7.2.1, the last version that is compatible with that operating system. I have attached a build log from [~wmwood-vasey]. [~smonkewitz] suggests trying the following (HipChat UW DM room, 2016-05-12 18:12 Pacific): in BinnedWcs.h change: {code} virtual PTR(afw::image::Wcs) clone() const { return PTR(afw::image::Wcs)(new BinnedWcs(_parent, _xBin, _yBin, _xy0)); } {code} to: {code} virtual PTR(afw::image::Wcs) clone() const { return PTR(afw::image::Wcs)(std::make_shared<BinnedWcs>(_parent, _xBin, _yBin, _xy0)); } {code} with the following explanation (HipChat SQuaRE room 2016-05-12 18:26 Pacific): {{enable_shared_from_this}} usually holds a {{weak_ptr}} to this internally, and the first {{shared_ptr}} to manage an instance is assigned to the internal {{weak_ref}}. It looks to me like this particular version of the STL only allows {{std::shared_ptr<A>}} to be assigned to a {{weak_ptr<B>}} if {{A}} is implicitly convertible to {{B}}. In this case the first {{shared_ptr}} to manage the {{BinnedWcs}} is a {{shared_ptr<Wcs>}}, and I think a static cast is required to get from {{Wcs *}} to {{BinnedWcs *}}, so the compiler barfs.
| 0 |
1,220 |
DM-6100
|
05/13/2016 15:20:32
|
afw/tests/rgb.py fails due to .ttf files
|
afw/tests/rgb.py fails for me with the below error. We likely shouldn't be trying to track system resources like fonts, as we don't have any control over them. {code} [2016-05-12T19:46:12.528961Z] Failed test output: [2016-05-12T19:46:12.536029Z] tests/rgb.py [2016-05-12T19:46:12.536057Z] [2016-05-12T19:46:12.536070Z] ...s......ss...F. [2016-05-12T19:46:12.536106Z] ====================================================================== [2016-05-12T19:46:12.536138Z] FAIL: testFileDescriptorLeaks (lsst.utils.tests.MemoryTestCase) [2016-05-12T19:46:12.536173Z] ---------------------------------------------------------------------- [2016-05-12T19:46:12.536192Z] Traceback (most recent call last): [2016-05-12T19:46:12.536261Z] File "/Users/parejkoj/lsst/lsstsw/stack/DarwinX86/utils/2016_01.0-4-g52f464f/python/lsst/utils/tests.py", line 134, in testFileDescriptorLeaks [2016-05-12T19:46:12.536330Z] self.fail("Failed to close %d file%s" % (len(diff), "s" if len(diff) != 1 else "")) [2016-05-12T19:46:12.536352Z] AssertionError: Failed to close 2 files [2016-05-12T19:46:12.536356Z] [2016-05-12T19:46:12.536391Z] ---------------------------------------------------------------------- [2016-05-12T19:46:12.536404Z] Ran 17 tests in 3.451s [2016-05-12T19:46:12.536407Z] [2016-05-12T19:46:12.536424Z] FAILED (failures=1, skipped=3) [2016-05-12T19:46:12.536445Z] File open: /Library/Fonts/NISC18030.ttf [2016-05-12T19:46:12.536479Z] File open: /System/Library/Fonts/Apple Color Emoji.ttf [2016-05-12T19:46:12.536495Z] The following tests failed: [2016-05-12T19:46:12.539928Z] /Users/parejkoj/lsst/lsstsw/build/afw/tests/.tests/rgb.py.failed [2016-05-12T19:46:12.540060Z] 1 tests failed {code}
| 0.5 |
1,221 |
DM-6111
|
05/15/2016 11:46:58
|
Browsers should cache editions for a shorter time period than Fastly
|
Currently we set {{Cache-Control: max-age=31536000}} so that Fastly caches uploads from LTD Mason for a year on its POPs. This has the side-effect of also having browsers potentially cache documentation on the client for up to a year. In practice, browsers churn through their cache space more quickly, but I've noticed that Safari has no cap on its cache space, and therefore can hold onto pages for a long time. The solution is to set a {{Surrogate-Control}} max age to 1 year, and have {{Cache-Control: max-age=0, private, must-revalidate}}. This will be done on LTD Keeper during the copy phase of a build into an edition (since it is reasonable for a client to cache a build forever), but then give us the flexibility to update an edition instantly. In the future we may want a more nuanced solution where CSS and JavaScript, for example, are cached longer on the browser.
| 1 |
1,222 |
DM-6112
|
05/15/2016 16:08:03
|
Provide minimal documentation for meas_extensions_photometryKron
|
Please provide a minimal level of documentation for meas_extensions_photometryKron, 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).
| 0.5 |
1,223 |
DM-6126
|
05/16/2016 17:37:33
|
LSST's version of Astrometry.net doesn't build on Ubuntu 16.04
|
Reproduced building on Ubuntu 16.04. https://groups.google.com/forum/#!topic/astrometry/aDCjhfMYhpE The current version (0.67) does build successfully standalone. These two patches fix 0.5.0: https://github.com/dstndstn/astrometry.net/commit/7ded70917d7cf1efa1d3af6d0da8b336ebbf9d92.diff and https://github.com/dstndstn/astrometry.net/commit/7c65b3cefc4f33c59af90c1a40b5f246002cdf28.diff Though only the first one is needed, I believe the second one is part of the build already.
| 1 |
1,224 |
DM-6127
|
05/16/2016 18:05:05
|
ngmix has no license
|
ngmix does not have a license, which means we shouldn't distribute it. Work with Erin Sheldon to see if he is willing to add one.
| 1 |
1,225 |
DM-6128
|
05/16/2016 20:13:00
|
Expanded view not doing fit/fill consistently
|
Expanded view not doing fit/fill consistently. Sometimes is seems to fit/fill and resize it correctly, other times it stays at the zoom level. It should always fit/fill and change zoom level with resize when in expanded mode. (unless zoom type is FORCE_STANDARD).
| 1 |
1,226 |
DM-6133
|
05/17/2016 11:06:44
|
mpi4py does not compile under Yosemite due to hardcoded MACOSX_DEPLOYMENT_TARGET
|
{{mpi4py}} build on Yosemite (Mac OS X 10.10) fails with {code} _build.log:[2016-05-17T16:51:55.847161Z] error: $MACOSX_DEPLOYMENT_TARGET mismatch: now "10.9" but "10.10" during configure {code} For details see attached build log. The {{MACOSX_DEPLOYMENT_TARGET}} is being set in {{ups/eupspkg.cfg.sh}} {code} [serenity mpi4py] cat ups/eupspkg.cfg.sh # If MACOSX_DEPLOYMENT_TARGET is not set, we force it to be at least 10.9 # (Mavericks). This is the earliest version of OS X expected to work with # release 11 of the LSST stack. # This works around DM-5409, wherein mpi4py was attempting to use an OS X 10.5 # SDK, based on querying Anaconda, and failing. export MACOSX_DEPLOYMENT_TARGET=${MACOSX_DEPLOYMENT_TARGET:-10.9} {code} What is it that is supposed to be setting {{MACOSX_DEPLOYMENT_TARGET}}? And why is it not set at the time when {{ups/eupspkg.cfg.sh}} is run, but is set to 10.10 by the time the actually compilation is done?
| 1 |
1,227 |
DM-6138
|
05/17/2016 16:02:38
|
Change Fields groups to handle other actions better
|
The fields group can be out of sync with actions if they are trying to use store data when that actual value is changes. This is a classic side-effect issue. It can be solved with sagas. Our current example. The color panels updating from the plot when the activePlotId changes. More to do: * field groups need a sega to more effective respond to out side actions * the dispatchChangeFieldGroup needs better, more documented parameters * update multiple fields at the same time. * should we have the field group support reset to init state? probably not, but look into it. * change init values? * Check example dialog and see if the large/smaller example is validating correctly.
| 2 |
1,228 |
DM-6139
|
05/17/2016 16:05:23
|
Change server side hardcopy code to work better with the non-GWT call
|
The server hard to make a hard copy now takes a StaticDrawInfo object. We want to use only a region array. Change the server side to support this.
| 2 |
1,229 |
DM-6147
|
05/18/2016 14:36:47
|
Set SUSPECT mask in ISR task and make saturation a double
|
Implement RFC-190 and mask suspect pixels: Add {{selectLevel}} to {{lsst.afw.cameraGeom.AmpInfoCatalog}}, as a double, and add support for it to {{lsst.ip.isr.IsrTask}}, analogously to masking saturation: iif {{suspectLevel}} is not {{nan}} then set the {{SUSPECT}} flag for pixels above the suspect level. Also change the type of {{saturation}} in the {{AmpInfoCatalog}} from {{int}} to {{double}}, so that the existing test for {{nan}} actually works
| 5 |
1,230 |
DM-6149
|
05/18/2016 15:28:38
|
Reduce memory utilization in mysql proxy
|
Jon is trying to run tests with large result which kills proxy/czar because it runs out of virtual memory. Would be nice to reduce memory use and find a way not to keep query result in memory.
| 2 |
1,231 |
DM-6151
|
05/18/2016 19:26:12
|
Failure to fail when fallbackFilterName is None
|
When no {{fallbackFilterName}} is set, we can get a confusing error message when failing to load a calib: {code} RuntimeError: Unable to retrieve dark for {'filter': 'U', 'date': '2016-05-12T02:58:56.591', 'ccd': 0, 'basename': '2016-05-12skyflats_02', 'object': 'FLAT', 'visit': 883, 'expTime': 20.0006, 'channel': 16} and no fallback filter specified: Unknown value type for filter: <type 'NoneType'> {code} This is unrelated to the calib load failure, and merely reflects the fact that {{fallbackFilterName=None}}.
| 1 |
1,232 |
DM-6166
|
05/20/2016 17:41:31
|
Time AST and compare to our WCS code
|
Time TAN-SIP for our code and for AST, in order to get a sense of the performance impact of switching to AST for our WCS implementation.
| 3 |
1,233 |
DM-6177
|
05/23/2016 03:26:20
|
Increase memory locked amount in container
|
In order to lock memory, the memory locking limit within the container for the qserv worker needs to be raised. My understanding is the container uses whatever is the host setting so the limit has to be set for the container user and whatever the user is inside the container. The particular limits is: memorylocked 64 kbytes notice that by default it's 64K. That needs to be raised to say 75% of the real machine size. I wouldn't make it unlimited as a memlock mistake may crash the whole machine. The limits are specified in "/etc/security/limits.conf". You will know that you are successul when you ssh into the container as the qserv worker user and the "limit" command tell you have can lock lots of memory. We would also set the CAP_IPC_LOCK privilege but setting the soft/hard limit above should be good enough. So, let's start with that.
| 2 |
1,234 |
DM-6179
|
05/23/2016 08:35:50
|
Support Python 3 migration
|
Support the migration of the DM code to Python 3. This includes writing transition documentation, integration of a new scons, migrating a handful of low-level packages and liaising with the teams on their packages. The final outcome of this epic is that everything would be in place for the migration at the August All Hands meeting.
| 40 |
1,235 |
DM-6180
|
05/23/2016 08:39:53
|
Update LSE-61 requirements and traceability
|
With the updates to DPDD and LDM-151 in the early part of F16, there is a need to update LSE-61 (DMSR) such that it can directly trace requirements from OSS+DPDD through LSE-61 and down to implementation LDM documents. This will require substantial rewrites of many of the existing requirements and possible addition of new requirements. It may also be necessary to add annotations to DPDD and other LDM documents to provide traceability anchors for DMSR. The outcome of this epic is a new baselined DMSR approved by CCB.
| 40 |
1,236 |
DM-6185
|
05/23/2016 21:17:40
|
Get jointcal running on minimum data
|
It is very important for other teams to have a version of jointcal running to remove the sensitivity on the errors in astrometric reference catalogs. The suggestion is to get jointcal running with CFHT, HSC, DECam and lsstSim.
| 100 |
1,237 |
DM-6188
|
05/23/2016 22:39:51
|
First draft of overview ("vision") document
|
See https://dmtn-016.lsst.io
| 3 |
1,238 |
DM-6199
|
05/24/2016 00:41:24
|
Stack API documentation
|
Stack API Doc generation -> pipelines.lsst.io Deliverables: * a proof of concept of a CI-driven API doc build * documentation content planning
| 20 |
1,239 |
DM-6206
|
05/24/2016 03:11:10
|
CI Improvements: Jenkins 2 upgrade etc
|
This epic covers a timeboxed maintainance of the Jenkins-based CI system, including the Jenkins 2 upgrade as well as the required updates to the Jenkins-puppet module. It also may include work done as part of DM-6204 brought over to the apps CI service. Highlights: - Jenkins 2 upgrade in production at ci.lsst.codes - Improvements releases as part of the widely used puppet Jenkins module https://github.com/jenkinsci/puppet-jenkins
| 8 |
1,240 |
DM-6208
|
05/24/2016 03:18:45
|
SQuaRE services disaster recovery
|
This is a timeboxed effort to test and improve backups and disaster recovery for SQuaRE services. It is unlikely to be sufficient in itself. Delivered: daily snapshots of git repos in lsst, lsst-dm and lsst-sqre orgs, with a progressive roll-off retention policy. Git-LFS repos are not currently serviced by this strategy, work on this will be scheduled at a later date.
| 8 |
1,241 |
DM-6209
|
05/24/2016 03:19:49
|
Ad-hoc developer requests
|
This is a bucket epic for ad-hoc developer requests that cannot be postponed till the next planning cycle. In the event that it is underutilised for this purpose, it will be assigned to technical debt DM-5850
| 8 |
1,242 |
DM-6224
|
05/24/2016 09:24:01
|
F16 Butler Repository Refactor
|
Per KT, the parent/peer repository relationship scheme was not an exact fit for what we need. We discussed and decided that butler should manage its own input and output repositories. Also discussed with KT and Gregory was the ability to select inputs by 'tagging' repositories. The design discussion with the larger group is captured in RFC-184.
| 40 |
1,243 |
DM-6239
|
05/24/2016 11:22:28
|
The grid labels are not placed in the right position when the coordinate is Ecliptic coordianates
|
The algorithm to calculate the label position does not work well for the Ecliptic coordinate system. The algorithm needs to be modified to work for all the coordinates.
| 2 |
1,244 |
DM-6246
|
05/24/2016 13:17:24
|
Vertical overscan off by one again
|
In DM-5524 [~price] fixed the vertical overscan by directly editing the amp info catalogs, but didn't mark the camera generating code as bad. In DM-6147 I regenerated the files, reintroducing the problem. The problem seems to be a subtle bug in the camera generating code. Rather than try to fix it, I'll convert the fixed catalogs directly and mark the generating code as broken. [~price] will issue an RFC that suggests a better way to handle generating amp info and once that is dealt with we can come up with a more permanent fix (e.g. delete the generating code or fix it).
| 0.5 |
1,245 |
DM-6247
|
05/24/2016 13:18:08
|
DRP Outline for LDM-151
|
Write outline for Data Release Production section of LDM-151, using the DRP Data Flow diagram as the organizing principle.
| 2 |
1,246 |
DM-6248
|
05/24/2016 13:19:53
|
DRP Top-Level Diagram and Descriptions, Draft 1
|
Insert the content from the DRP Data Flow diagram on Confluence into LDM-151, adjusting it to the outline developed on DM-6247.
| 2 |
1,247 |
DM-6251
|
05/24/2016 13:21:54
|
Convert DRP Top-Level Diagram to standard conventions
|
DM-6248 adds a large, complex diagram that will need to be cleaned up and converted to use the same conventions and colors as other diagrams in LDM-151.
| 2 |
1,248 |
DM-6261
|
05/24/2016 13:48:00
|
Cleanup and standardize DRP background matching, coaddition, and diffim diagrams
|
DM-6256 will produce rough diagrams that will require cleanup and standardization. [~ctslater] has made some suggestions for the current diagram that I'll implement on this issue, so I'm assigning it back to me. I'll also go ahead and integrate his updated DRP overview diagram (currently on Confluence) into LDM-151 here.
| 1 |
1,249 |
DM-6280
|
05/25/2016 12:37:26
|
The labels in HMS formate are wrong in WebGrid
|
The labels in HMS format no longer show hh:mm:ss anymore. The porting introduced the bug.
| 1 |
1,250 |
DM-6281
|
05/25/2016 13:01:02
|
More visualization features in S17
|
New features for visualization in Firefly: error-bars in 2D scatter plot, allow user to control symbol size and shapes for overlaid objects, histogram improvement, density plot improvements.
| 100 |
1,251 |
DM-6288
|
05/25/2016 18:22:29
|
Chart options display
|
Make chart options "in-place" popup, similar to table options for consistent look. It will also alleviate resizing, because the chart size won't need to change when options are open.
| 3 |
1,252 |
DM-6294
|
05/26/2016 11:56:58
|
Add support for pybind11 to build system
|
Add pybind11 as third party package to the stack. Update sconsUtils to support building with pybind11. Use daf_base DateTime to demonstrate that this works.
| 8 |
1,253 |
DM-6297
|
05/26/2016 12:01:26
|
Wrap afw::detection with pybind11
|
The generated wrappers will live parallel to the Swig wrappers. This ticket only covers the C++ wrappers themselves, not the Python layer on top (which will continue to use the old wrappers) all work will stay on a separate branch and will not be merged to master until DM-8467 is complete. The tests included in this ticket are: # {color:#14892c}testExposureTable.py{color} # {color:#14892c}testFootprint1.py{color} # {color:#14892c}testFootprint2.py{color} # {color:#14892c}testFootprintEllipse.py{color} # {color:#14892c}testFootprintMergeCatalog.py{color} # {color:#14892c}testGaussianPsf.py{color} # {color:#14892c}testHeavyFootprint.py{color} # {color:#14892c}testRgb.py{color} # {color:#14892c}testTicket2019.py{color}
| 5 |
1,254 |
DM-6306
|
05/26/2016 14:43:29
|
Executable test in utils needs to test an executable
|
In DM-4036 all the test binaries were removed as no longer being needed. This had the unfortunate side effect that the {{testExecutables.py}} test no longer tests anything. This ticket will be used for adding a test file.
| 1 |
1,255 |
DM-6309
|
05/27/2016 07:11:52
|
Update LDM-151 with SDQA Skeleton and Outline
|
1. Update the LDM-151 draft with the SDQA Skeleton from the DMLT + SciPipelines working group discussions of May 16-20. Implement as bullet points in a semi-coherent list. (/) 2. Clean up list. (/)
| 1 |
1,256 |
DM-18251
|
05/27/2016 10:34:25
|
Old T&S Epic carried over from old JIRA project - no longer valid
|
Old T&S Epic carried over from old JIRA project - no longer valid
| 2 |
1,257 |
DM-6313
|
05/27/2016 11:43:40
|
Create miniconda3 EUPS package
|
{{newinstall.sh}} currently installs miniconda via EUPS. To replicate that functionality in Python3 we need to create a {{miniconda3}} package. This package should be almost identical to {{miniconda2}}. Requires that {{lsstsw}} first be updated to support python 3.
| 1 |
1,258 |
DM-6314
|
05/27/2016 11:51:39
|
Port lsstsw to Python 3
|
Get {{lsstsw}} working with Python 3: * Update the {{deploy}} script to allow a Python 3 python to be installed and modify the version checking code. * Demonstrate that {{lsstsw}} {{rebuild}} will successfully build and install a third-party non-Scons package.
| 5 |
1,259 |
DM-6316
|
05/27/2016 12:18:25
|
Update newinstall.sh to support Python 3
|
{{newinstall.sh}} currently insists on installing and checking for python 2.7. This needs to be changed to allow Python 3. Requires {{sconsUtils}} works with Python 3 as the {{lsst}} EUPS package is installed as part of {{newinstall.sh}}.
| 1 |
1,260 |
DM-6317
|
05/27/2016 12:21:50
|
Update developer guide to include Python 3
|
Update the developer guide to indicate that Python 3 must be supported and that code must run on Python 2.7 and 3. This ticket will reference the tech note delivered as part of DM-6315. Writing extensive user documentation on the {{future}} package is beyond the scope of this ticket.
| 2 |
1,261 |
DM-6319
|
05/27/2016 12:43:15
|
Adjust sconsUtils to query python on path for executable location
|
{{sconsUtils}} has to be modified to ensure it works with Python 3. Additionally SWIG calls might need to be changed to trigger Python 3 mode.
| 3 |
1,262 |
DM-6320
|
05/27/2016 12:45:05
|
Port utils to Python 3
|
Ensure that the {{utils}} package will work with Python 3.
| 2 |
1,263 |
DM-6322
|
05/27/2016 12:47:00
|
Port base package to Python 3
|
Ensure that {{base}} works with Python 3.
| 2 |
1,264 |
DM-6323
|
05/27/2016 13:13:36
|
Lead Python 3 migration at All Hands Meeting
|
* Prepare for all hands meeting. * Present plan to developers. * Advise developers doing migration. * Contribute fixes as required.
| 8 |
1,265 |
DM-6325
|
05/27/2016 14:50:55
|
Replace BOOST_STATIC_ASSERT with static_assert
|
Replace BOOST_STATIC_ASSERT with static_assert from C++11.
| 0.5 |
1,266 |
DM-6326
|
05/27/2016 15:15:26
|
reST roles for mock code references
|
Add mock code reference roles so that authors can add semantics to their writing without attempting to make actual references to API documentation that does not _yet_ exist. Covers all roles in the Python domain, and supports tilde syntax for collapsing the namespace.
| 0.5 |
1,267 |
DM-6328
|
05/28/2016 17:08:35
|
add hsc driver script to validate_drp
|
Add an equivalent of {{examples/runChftTest.sh}} to {{validate_drp}} to process {{validation_data_hsc}}.
| 8 |
1,268 |
DM-6346
|
05/31/2016 11:55:05
|
User installation and operation instructions for conda
|
Create documentation for the Stack conda binaries created in DM-5415 as part of the Science Pipelines documentation
| 3 |
1,269 |
DM-6348
|
05/31/2016 14:01:06
|
Write Calibration Products Production section of LDM-151
|
Write photometric calibration pipeline section of LDM-151
| 20 |
1,270 |
DM-6368
|
06/01/2016 10:26:54
|
Adjust version check of EUPS python package to allow v3
|
To enable Python 3 support of the stack the EUPS {{python}} stub package needs to allow Python 3.
| 0.5 |
1,271 |
DM-6373
|
06/01/2016 14:52:12
|
Improve skeleton for LDM-151 Algorithmic Components
|
For all subsections in Algorithms Components owned by [~jbosch]: - Provide enough bullet points to capture scope. - Add bullet points for subtly difficult aspects of components. - Add extra level subsubsubsection level for Measurement. - Create matrix of measurement algorithms and contexts.
| 1 |
1,272 |
DM-6375
|
06/01/2016 15:18:58
|
New image visualization functions (F16)
|
TO support the pipeline QA and build the first web portal, there will be new functions need to be developed. This epic is to collect those functions.
| 40 |
1,273 |
DM-6378
|
06/01/2016 15:28:38
|
Persist output of simple DCR correction
|
DM-5695 will create transfer matrices stored as numpy arrays. This ticket extends that work to determine a useful format and write functionality to persist those arrays.
| 2 |
1,274 |
DM-6383
|
06/01/2016 15:44:50
|
Use template DCR images for image differencing
|
DM-6382 creates template images of a field at arbitrary airmasses, which can be used to match the template airmass to the science image precisely to mitigate Differential Chromatic Refraction in image differencing. This ticket is to determine the best method to supply the new templates to image differencing, which may be simply to create a new exposure and ingest/process the template as though it were a real observation.
| 2 |
1,275 |
DM-6392
|
06/01/2016 19:29:13
|
Text on variability characterization for LDM-151
|
Expand the variability characterization algorithmic section of LDM-151.
| 1 |
1,276 |
DM-6437
|
06/02/2016 14:41:35
|
Convert GWT projection and Coorindate Conversion routine to JavaScript
|
convert Booth's projection code and Judy Bennet's coordinate conversion routines to pure javascript
| 8 |
1,277 |
DM-6457
|
06/03/2016 15:57:22
|
Design and RFC for Repository Refactor
|
Drive the RFC for Repo Refactor to completion (this includes a lot of design work)
| 20 |
1,278 |
DM-6458
|
06/03/2016 16:00:24
|
Expand skeleton in LDM-151
|
We need to flesh out the skeleton text to contain full descriptions of the algorithms and pipelines we expect the baseline design to use.
| 20 |
1,279 |
DM-6459
|
06/03/2016 16:00:39
|
productize "Repository Refactor"
|
After RFC-184 is closed: implement, unit tests, review, document, submit. When this story closes, I think RFC-184 status is supposed to be changed from Adopted to Implemented.
| 20 |
1,280 |
DM-6473
|
06/06/2016 15:38:18
|
Possible image related issues in firefly viewer
|
Image Meta Data tab * images cannot be remove, but in expanded mode, it can. * selecting image no longer highlight table. the reverse works fine. * visualize/saga/ImageMetaDataWatcher.js:272 returns -1. * when a non-meta table is selected, images are shown, but not the toolbar. * after table is removed, images are still there. image external api does not mix well with firefly viewer. * firefly viewer uses 'triViewImages’ viewer_id while api has no viewer_id. as a result, images loaded by api will be lost once table or other searched data are returned. * catalog overlay are drawn outside of the images. more issues: - -It's possible to select distance tool and then area selection. First drag would define area selection, all the following line. A click would be defining a 0 length line, even if point selection is enabled.- _moved to_ DM-6656
| 8 |
1,281 |
DM-6474
|
06/06/2016 17:26:01
|
Restore star selector registry
|
Restore the registry for star selectors that was lost in DM-5532, now that tasks in registries can be used as subtasks. Also use the registry where appropriate.
| 2 |
1,282 |
DM-6490
|
06/07/2016 11:38:11
|
Investigate calibration zeropoint offset between HSC vs. LSST processCcd.py runs
|
As reported in DM-4730, while the scatter between single frame processing measurements of the same dataset on the HSC vs. LSST stacks is quite good (rms = 0.009 mag between Gaussian fluxes, for example, in the figure shown on that ticket), there is a clear offset (0.0166 mag in the figure shown) in the zeropoint between the two stacks (it is systematic, i.e. no trend with magnitude). The cause may well be due to slight differences in the reference stars selected for calibration. We also speculated about differences in slot definitions used in the calibrations steps (e.g. for aperture corrections, psfex, etc...), so I have rerun visit 1322 through both stacks having forced all apertures used in calibration to be the same, namely a circular aperture of 12 pixels measured using the sinc algorithm (as opposed to "naive"). I have attached the *processCcd.py* config files for the two runs so my settings can be reproduced. Also of note, I am using a {{meas_algorithms}} branch on the HSC stack with the following commit: {code} commit 173ad0b32ed4f4ab074f1a942d2d3f758e189917 Author: Lauren MacArthur <[email protected]> Date: Wed Jan 13 16:35:59 2016 -0500 Hack to allow flux.aperture to be used in apCorr Since it does not seem possible to access the nth element of a schema element that is an array in the context of setting a config override, this allows for flux.aperture to be set as calibrate.measureApCorr.reference and it sets it to index 4 (which corresponds to a radius of 12 pixels) in the __init__. This was selected to match the current LSST default. diff --git a/python/lsst/meas/algorithms/measureApCorr.py b/python/lsst/meas/algorithms/measureApCorr.py index 9f6c599..f1fa99d 100644 --- a/python/lsst/meas/algorithms/measureApCorr.py +++ b/python/lsst/meas/algorithms/measureApCorr.py @@ -81,6 +81,9 @@ class MeasureApCorrTask(lsst.pipe.base.Task): def __init__(self, schema, **kwds): lsst.pipe.base.Task.__init__(self, **kwds) self.reference = KeyTuple(self.config.reference, schema) + if self.config.reference == 'flux.aperture': + print "NOTE: setting aperture correction flux to flux.aperture[4] ==> radius = 12 pixels" + self.reference.flux = self.reference.flux[4] self.toCorrect = {} {code} I attach some of the figures comparing the PSF fluxes from these runs which compare the output of the two stacks having matched the two src catalogs. There are two sets: 1) having adjusted the flux for each source to the zeropoint calculated in the calibration and stored as *FLUXMAG0* 2) having adjusted the flux for all sources to a common zeropoint (zp=33.0, chosen to roughly match the calibrated zp). Note that my figures do include aperture corrections (in DM-5301, many of the plots show fluxes pre-aperture correction). I have also included plots that directly compare the aperture corrections applied (difference in mag units). Finally, I also include plots comparing the 12 pixel circular aperture mags (i.e. to which no apCorr is added). Clearly, the zeropoint determined in the calibration of the two stacks differs between the two stacks and, in particular, there seem to be some very problematic CCDs where the differences are particularly significant (~0.05 mag, and not always in the same direction). Please investigate the source of this discrepancy.
| 8 |
1,283 |
DM-6494
|
06/07/2016 15:43:06
|
Better error messages from the camera mapper when a template cannot be formatted
|
The CameraMapper produces a very unhelpful traceback if it cannot format a template string with the provided data ID dict. For example: {code} Traceback (most recent call last): File "/Users/rowen/UW/LSST/lsstsw/stack/DarwinX86/pipe_tasks/12.0.rc1-3-gb785bf9/bin/processCcd.py", line 25, in <module> ProcessCcdTask.parseAndRun() File "/Users/rowen/UW/LSST/lsstsw/stack/DarwinX86/pipe_base/12.0.rc1-1-g832266b/python/lsst/pipe/base/cmdLineTask.py", line 450, in parseAndRun parsedCmd = argumentParser.parse_args(config=config, args=args, log=log, override=cls.applyOverrides) File "/Users/rowen/UW/LSST/lsstsw/stack/DarwinX86/pipe_base/12.0.rc1-1-g832266b/python/lsst/pipe/base/argumentParser.py", line 479, in parse_args self._processDataIds(namespace) File "/Users/rowen/UW/LSST/lsstsw/stack/DarwinX86/pipe_base/12.0.rc1-1-g832266b/python/lsst/pipe/base/argumentParser.py", line 577, in _processDataIds dataIdContainer.makeDataRefList(namespace) File "/Users/rowen/UW/LSST/lsstsw/stack/DarwinX86/pipe_base/12.0.rc1-1-g832266b/python/lsst/pipe/base/argumentParser.py", line 126, in makeDataRefList dataRef=dr)] File "/Users/rowen/UW/LSST/lsstsw/stack/DarwinX86/pipe_base/12.0.rc1-1-g832266b/python/lsst/pipe/base/argumentParser.py", line 935, in dataExists return butler.datasetExists(datasetType = datasetType, dataId = dataRef.dataId) File "/Users/rowen/UW/LSST/lsstsw/stack/DarwinX86/daf_persistence/12.0.rc1-1-gc553c11+4/python/lsst/daf/persistence/butler.py", line 288, in datasetExists locations = self.repository.map(datasetType, dataId) File "/Users/rowen/UW/LSST/lsstsw/stack/DarwinX86/daf_persistence/12.0.rc1-1-gc553c11+4/python/lsst/daf/persistence/repository.py", line 392, in map return self.doParents(Repository.doMap, *args, **kwargs) File "/Users/rowen/UW/LSST/lsstsw/stack/DarwinX86/daf_persistence/12.0.rc1-1-gc553c11+4/python/lsst/daf/persistence/repository.py", line 325, in doParents res = func(parent, *args, **kwargs) File "/Users/rowen/UW/LSST/lsstsw/stack/DarwinX86/daf_persistence/12.0.rc1-1-gc553c11+4/python/lsst/daf/persistence/repository.py", line 405, in doMap loc = self._mapper.map(*args, **kwargs) File "/Users/rowen/UW/LSST/lsstsw/stack/DarwinX86/daf_persistence/12.0.rc1-1-gc553c11+4/python/lsst/daf/persistence/mapper.py", line 169, in map return func(self.validate(dataId), write) File "/Users/rowen/UW/LSST/lsstsw/stack/DarwinX86/daf_butlerUtils/12.0.rc1+6/python/lsst/daf/butlerUtils/cameraMapper.py", line 284, in mapClosure return mapping.map(mapper, dataId, write) File "/Users/rowen/UW/LSST/lsstsw/stack/DarwinX86/daf_butlerUtils/12.0.rc1+6/python/lsst/daf/butlerUtils/mapping.py", line 123, in map path = mapper._mapActualToPath(self.template, actualId) File "/Users/rowen/UW/LSST/lsstsw/stack/DarwinX86/daf_butlerUtils/12.0.rc1+6/python/lsst/daf/butlerUtils/cameraMapper.py", line 732, in _mapActualToPath return template % self._transformId(actualId) TypeError: %d format: a number is required, not NoneType {code} It is unclear what string was being formatted with what data, making the problem difficult to diagnose and correct. I suggest changing line 732 of CameraMapper.py from: {code} return template % self._transformId(actualId) {code} to something like the following: {code} try: transformedId = self._transformId(actualId) return template % transformedId except Exception as e: raise RuntimeError("Failed to format %r with data %r: %s" % (template, transformedId, e)) {code} Here are the last few lines of the same traceback after applying this change: {code} path = mapper._mapActualToPath(self.template, actualId) File "/Users/rowen/UW/LSST/lsstsw/stack/DarwinX86/daf_butlerUtils/12.0.rc1+6/python/lsst/daf/butlerUtils/cameraMapper.py", line 735, in _mapActualToPath raise RuntimeError("Failed to format %r with data %r: %s" % (template, transformedId, e)) RuntimeError: Failed to format '%(date)s/%(filter)s/decam%(visit)07d.fits.fz[%(hdu)d]' with data {'date': '2013-02-10', 'ccdnum': 10, 'hdu': None, 'visit': 176837, 'filter': 'z'}: %d format: a number is required, not NoneType {code} A bit wordy, but it is much easier to figure out what went wrong. I have stumbled across this problem twice in the last few weeks, so I consider this change fairly important. The first time it was caused by a defective format string in a paf file. This time I'm not yet sure what is causing it, but at least I have something to go on.
| 0.5 |
1,284 |
DM-6497
|
06/08/2016 02:14:02
|
Assist IN2P3 engineer in loading DC2013 data sample
|
Bogdan Vulpescu, IN2P3 engineer, tried to load DC2013 data sample. Fabrice help was required to install Qserv in multi-nodes and understand data-loading system. Some issues have been found and will be reported in future tickets: - a script to publish loaded data (i.e. insert db name in qservw_worker.Dbs) would be useful - mysql client might break proxy if option are not provided correctly (a bug report will be available soon)
| 3 |
1,285 |
DM-6514
|
06/09/2016 09:06:59
|
Minor fixes to linearization
|
DM-5462 added linearization to {{IsrTask}} but had a few loose ends which this ticket aims to correct: - I intended to enable linearization by default, but somehow lost that change. - I intended to update obs_test to use null linearization, but I forgot and the previous item meant I didn't catch the omission - It turns out that the butler data proxy object will not work with functors (attempting to call the retrieved item results in an error, rather than resolving the proxy). This is easily worked around by using immediate=True when retrieving linearizers. This didn't show up until DM-6356 because obs_decam is the only camera that uses linearization lookup tables, and obs_subaru avoids the problem by not returning a proxy.
| 1 |
1,286 |
DM-6516
|
06/09/2016 11:09:11
|
Convert footprint support
|
Convert the footprint support from the GWT code
| 20 |
1,287 |
DM-6519
|
06/09/2016 15:22:54
|
Temp local background broken
|
The temp local background feature has been broken and needs to be fixed.
| 0.5 |
1,288 |
DM-6533
|
06/12/2016 15:58:52
|
LDM-151 adjustments
|
Adding text to LDM-151 where appropriate, working around the structure defined by Jim et al.
| 2 |
1,289 |
DM-6542
|
06/14/2016 09:26:00
|
Prevent external viewer from popup blockers.
|
Currently, when external viewer launched, it is blocked by pop-up blockers. Need to change polling logic to a pushed solution so the 'launch' action can happen immediately.
| 3 |
1,290 |
DM-6566
|
06/15/2016 15:29:08
|
Make updateSourceCoords and updateRefCentroids more visible
|
Implement RFC-197 to make updateSourceCoords and updateRefCentroids more visible
| 1 |
1,291 |
DM-6569
|
06/16/2016 09:51:33
|
Remove the extra init method from the SourceDetectionTask
|
SourceDetectionTask defines both {{init(self, schema=None, **kwds)}} and {{\_\_init\_\_(self, schema=None, **kwds)}}. The first exists purely because of a Doxygen bug that makes {{\copydoc \_\_init\_\_}} fail. However, {code} copydoc \_\_init\_\_ {code} works. Remove the non-dunder init method and update the documentation with {code} \copydoc \_\_init\_\_ {code}.
| 1 |
1,292 |
DM-6590
|
06/17/2016 14:08:38
|
Collection of small bugs and look and feel issues
|
1. In the color stretch dialog: (in chrome Version 50.0.2661.102 (64-bit) on my Mac OSX 10.9.5) * the asinh beta and powerLaw Gamma input field do not look like part of the input fields group. Too much white space in between. * When clicked on the Z scale option when the asinh and powerLaw types selected, the min and max values overlapped with the option choice.
| 2 |
1,293 |
DM-6592
|
06/17/2016 16:10:13
|
enable subMenu in the menu list
|
We want to have a subMenu component in the Firefly so we could group some of the actions together by putting them into subMenu. Added submenu capability to drop down menu. Submenu can be nested to multiple levels. Also, implemented ticket DM-14515 to place project footprints into submenu. You can test this by loading any image, then select {{Overlay Markers}} to see drop down with submenu.
| 8 |
1,294 |
DM-6601
|
06/20/2016 12:15:08
|
Port change to EXP-ID handling
|
From [HSC-1409|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1409]: {quote} Due to an operational reason (to meet the requirement of Subaru FITS dictionary), the definition of EXP-ID is soon to be changed in the data acquisition side. In the new definition, EXP-ID is set to 'HSCE%08d' where the letter 'E' is fixed as requested in the dictionary, and the number part corresponds to exactly the same number as our familiar 'visit'. obs_subaru:ingest.py needs to be updated to include this rule. The data taken with this change so far are: HSCA07441200--HSCA07441757 HSCA90925200--HSCA90929557 {quote} The change made as part of HSC-1409 introduces a new code path for the updated data, while old data continue to be supported with the old code path.
| 0.5 |
1,295 |
DM-6608
|
06/20/2016 16:46:35
|
Finalize v12 Pipelines release documentation
|
Add the release announcement and finalize other documentation details in pipelines.lsst.io for the v12 release.
| 1 |
1,296 |
DM-6612
|
06/21/2016 02:39:18
|
Make HSC processing without bright object catalogs easier
|
obs_subaru enables bright object masks by default, as that's desirable for HSC production runs. However, when HSC data is processed without bright object masks available (as will happen in most GO observations and development use), multiBandDriver.py will fail because the BRIGHT_OBJECT mask plane is not present but the base_PixelFlags algorithm is configured to make use of it. This is confusing, and it also requires the definition of a configuration file to fix the problem because base_PixelFlags cannot be configured directly on the command-line. Some possibilities for fixing this: - Add the BRIGHT_OBJECT mask plane in AssembleCoadd if doMaskBrightObjects is True but the external catalog is not found. This will make the PixelFlags operation a silent no-op. - Allow configuration options to allow PixelFlags algorithm to silently skip some flags if the appropriate masks are not available. I am sure there are other options as well.
| 2 |
1,297 |
DM-6613
|
06/21/2016 03:32:22
|
Typo in afw/display/interface.py
|
There's a typo in interface.py; the patch is {code} diff --git a/python/lsst/afw/display/interface.py b/python/lsst/afw/display/interface.py index 8599629..d7f58ea 100644 --- a/python/lsst/afw/display/interface.py +++ b/python/lsst/afw/display/interface.py @@ -537,7 +537,7 @@ class Display(object): k, x, y = ev.k, ev.x, ev.y # for now try: - if self.callbacks[k](k, x, y): + if self._callbacks[k](k, x, y): break except KeyError: print >> sys.stderr, "No callback is registered for %s" % k {code}
| 2 |
1,298 |
DM-6614
|
06/21/2016 03:36:27
|
Include Kron parameters in algorithm metadata
|
The Kron code doesn't set the algorithm metadata. E.g. {code} algMetadata.set("ext_photometryKron_KronFlux_nRadiusForFlux", config.plugins["ext_photometryKron_KronFlux"].nRadiusForFlux) {code}
| 1 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.