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
|
|---|---|---|---|---|---|
2,499 |
DM-12447
|
10/27/2017 14:18:31
|
Make Detector.transform and Camera.transform support lists of points
|
Implement RFC-392: make Detector.transform and Camera.transform support lists of points (or single points) and delete the CameraPoint class. Removing the CameraPoint class also requires a minor change to Camera.findDetectors and findDetectorsList.
| 5 |
2,500 |
DM-12450
|
10/28/2017 10:58:39
|
Implement RFC-407: improve interface for clobbering vs. reusing outputs
|
See RFC for description. IMO, this has bitten too many DRP team members recently to just put it on the backlog; I think it's really costing us time and money. Even if the RFC needs to stew for a while before merging, I'd like to get at least a partial implementation on a branch while it's fresh in my mind.
| 2 |
2,501 |
DM-12452
|
10/30/2017 09:04:48
|
Add FrameDict class
|
Add a new class FrameDict to astshim that is a FrameSet with a table for looking up frame index by domain. This can greatly simplify much of the code in afw that manipulates FrameSets.
| 2 |
2,502 |
DM-12455
|
10/30/2017 11:33:25
|
Please install v14.0 in the shared stacks on lsst-dev
|
The stack release v14.0 just came out. It would be useful if v14.0 is available in the shared stack on lsst-dev.
| 1 |
2,503 |
DM-12463
|
10/31/2017 10:29:13
|
Create initial design for how DCR will fit in the stack
|
Now that the prototype DCR code is finished it needs to be refactored and brought in to the stack. Since there is a substantial amount of code involved I will write an initial design first. The result of this ticket will be a brief report describing the code that will be added to existing packages and any anticipated changes.
| 8 |
2,504 |
DM-12464
|
10/31/2017 10:45:43
|
DCR correction design review
|
Review the design of the DCR algorithm in the stack, and gather feedback from stakeholders.
| 2 |
2,505 |
DM-12465
|
10/31/2017 10:47:38
|
Revise DCR technote
|
Revise the DCR technote DMTN-037 based on feedback received on the initial full draft.
| 3 |
2,506 |
DM-12467
|
10/31/2017 11:03:48
|
Prototype DCR code maintenance
|
While working on the design of how the DCR algorithm will fit in the stack, the existing prototype code is expected to change to reflect new functionality and limitations.
| 2 |
2,507 |
DM-12473
|
10/31/2017 14:50:15
|
Add getParallacticAngle() to visitInfo
|
[~sullivan] has done a bunch of math for calculating things related to refraction. Some of these should live in VisitInfo, since it knows the necessary values for the calculations. In particular, {{visitInfo::getParallacticAngle()}} would be very helpful. I suspect that there are some others in his DCR code that we'd like to have more broadly available. Ian suggests that he could do this as a pair coding exercise with [~rowen] or [~krzys], since he doesn't know C++ that well.
| 2 |
2,508 |
DM-12475
|
10/31/2017 15:37:16
|
Simplify PSF calculation in prototype DCR code
|
In order to simplify the transition of the prototype DCR code to the stack, several components should be re-written. This includes the PSF model, which currently depends on a lot of old and complicated code that deconvolves DCR from measured PSFs.
| 2 |
2,509 |
DM-12476
|
10/31/2017 15:41:33
|
Re-write Bandpass class and usage in prototype DCR code
|
The current bandpass implementation leads to an inaccurate effective wavelength calculation for DCR. That implementation should change, and the way the bandpass is used throughout the prototype code should be updated
| 5 |
2,510 |
DM-12480
|
11/01/2017 11:44:00
|
Update obs_comCam policy file
|
Following review comments on DM-12429, the policy for obs_comCam is not the minimal required to produce the same functionality, as a lot of things are redefined identically to how they are defined for the default in obs_base. This ticket is to make a best-effort at improving that situation, _and_ to fix a number of places in the path templates that are not currently correct (this is a newish obs_package and they were born wrong).
| 5 |
2,511 |
DM-12491
|
11/02/2017 16:18:37
|
Reduce compareWarp I/O
|
We already assume that a list of spanSets representing the artifacts can fit in memory, so we can assume that the list of artifact CANDIDATES can also fit in memory. Lets loop over the warps once, building the count map and candidates at once and then filter them afterwards.
| 2 |
2,512 |
DM-12524
|
11/07/2017 08:33:03
|
AST should still write in FITS-WCS format after offsetting CRPIX
|
If I offset CRPIX by inserting a shift at the beginning of the GRID to IWC mapping, the resulting WCS cannot be written in FITS-WCS format. David Berry has a fix in AST. This will require a new unit test in astshim and enables an improvement in ast: the shift can be added after GRID instead of between PIXEL0 and GRID (breaking the desired rule that PIXEL0 to GRID is always a shift of +1).
| 1 |
2,513 |
DM-12527
|
11/07/2017 10:41:56
|
base build failure on Ubuntu due to gcc non-detection
|
sconsUtils is not correctly detecting the default gcc (5.4) on Ubuntu 16.04. This results in {{-fno-lto}} not being included in the compiler options, resulting in a build failure (first failing package is {{base}}). Here's what the gcc non-detection looks like in the build log: {code} [2017-11-07T09:20:29.476932Z] Checking who built the CC compiler...unknown [2017-11-07T09:20:29.476948Z] CC is unknown version unknown {code}
| 2 |
2,514 |
DM-12529
|
11/07/2017 11:08:52
|
Enum comparison should use == not is
|
The *showVisitSkyMap.py* script in the {{examples}} sub-directory of the {{skymap}} repo uses the comparison: {code} ccd.getType() is cameraGeom.SCIENCE {code} This no longer evaluates to *True* when appropriate. The condition here should be `==`, not `is` (it is likely the behavior changed along with the pybind11 wrapping and has simply gone unnoticed since).
| 0.5 |
2,515 |
DM-12531
|
11/07/2017 15:18:21
|
Implement RFC-409: only check configurations/schemas/versions in output repos
|
Implements RFC-409. If this is as easy as I'm guessing, I should be able to get this done before the RFC is adopted, and then merge it at the same time as DM-12450 to allow me to group the announcements about these changes in behavior.
| 1 |
2,516 |
DM-12547
|
11/08/2017 13:13:04
|
SUIT and Firefly integration and test
|
This epic will capture the effort for integration and test in S18 of SUIT, including PDAC portal update/test, new features in portal an dFirefly test, packaging and deployment issues.
| 40 |
2,517 |
DM-12555
|
11/08/2017 15:23:37
|
HiPS: query a HiPS server to see what is available.
|
This issue needs research. It is currently possible from CDS if there is a standard. Research and implement the ability to create a list of HiPS repositories. The service is documented in section 5.2 of the attach HiPS pdf. The development includes, * send query to HiPS server to get public HiPS per information from [http://aladin.u-strasbg.fr/hips/list|https://github.com/Caltech-IPAC/firefly/pull/url] the available HiPS images can be retrieved by sending the query like [http://alasky.unistra.fr/MocServer/query?hips_service_url=*&dataproduct_type=!catalog&dataproduct_type=!cube&get=record|https://github.com/Caltech-IPAC/firefly/pull/url] * show the list of the found public HiPS in a table
| 8 |
2,518 |
DM-12556
|
11/08/2017 15:28:41
|
reportPerformance.py can't handle new metrics
|
Now that TE1 is calculated on the master branch of {{validate_drp}} but not included in the release metrics. This causes a {{KeyError}} when I run {{reportPerformance.py}} on JSON files produced with a master version.
| 1 |
2,519 |
DM-12561
|
11/09/2017 08:02:05
|
jupyterlabdemo build failing
|
{code:java} > npm pack @jupyter-widgets/jupyterlab-manager jupyter-widgets-jupyterlab-manager-0.29.3.tgz Traceback (most recent call last): File "/usr/bin/jupyter-labextension", line 11, in <module> load_entry_point('jupyterlab==0.29.0rc0', 'console_scripts', 'jupyter-labextension')() File "/usr/lib/python3.4/site-packages/jupyter_core/application.py", line 266, in launch_instance return super(JupyterApp, cls).launch_instance(argv=argv, **kwargs) File "/usr/lib/python3.4/site-packages/traitlets/config/application.py", line 658, in launch_instance app.start() File "/usr/lib/python3.4/site-packages/jupyterlab/labextensions.py", line 174, in start super(LabExtensionApp, self).start() File "/usr/lib/python3.4/site-packages/jupyter_core/application.py", line 255, in start self.subapp.start() File "/usr/lib/python3.4/site-packages/jupyterlab/labextensions.py", line 64, in start for arg in self.extra_args] File "/usr/lib/python3.4/site-packages/jupyterlab/labextensions.py", line 64, in <listcomp> for arg in self.extra_args] File "/usr/lib/python3.4/site-packages/jupyterlab/commands.py", line 137, in install_extension return IOLoop.instance().run_sync(func) File "/usr/lib64/python3.4/site-packages/tornado/ioloop.py", line 458, in run_sync return future_cell[0].result() File "/usr/lib64/python3.4/site-packages/tornado/concurrent.py", line 238, in result raise_exc_info(self._exc_info) File "<string>", line 4, in raise_exc_info File "/usr/lib64/python3.4/site-packages/tornado/gen.py", line 1069, in run yielded = self.gen.send(value) File "/usr/lib/python3.4/site-packages/jupyterlab/commands.py", line 208, in install_extension_async raise ValueError(msg) ValueError: "@jupyter-widgets/[email protected]" is not compatible with the current JupyterLab Conflicting Dependencies: JupyterLab Extension Package >=0.51.0-0 <0.52.0-0 >=0.50.2-0 <0.51.0-0 @jupyterlab/services >=0.12.0-0 <0.13.0-0 >=0.11.1-0 <0.12.0-0 @jupyterlab/application >=0.12.0-0 <0.13.0-0 >=0.11.1-0 <0.12.0-0 @jupyterlab/notebook >=0.12.0-0 <0.13.0-0 >=0.11.1-0 <0.12.0-0 @jupyterlab/rendermime >=0.12.0-0 <0.13.0-0 >=0.11.1-0 <0.12.0-0 @jupyterlab/coreutils The command '/bin/sh -c jupyter labextension install @jupyter-widgets/jupyterlab-manager' returned a non-zero code: 1 Docker build failed. {code}
| 1 |
2,520 |
DM-12571
|
11/10/2017 00:26:23
|
Update dev guide to allow super()
|
This ticket is to implement the final change from RFC-397. I've tweaked the wording slightly here to clarify the single/multiple inheritance point. This is the replacement version of the section of the python style guide about {{super()}}: {code} `super` MAY be used with care to call inherited methods Python provides `super()` so that each base class’s method is only called once. Using `super()` ensures a consistent Method Resolution Order, and prevents inherited methods from being called multiple times. In Python 3, `super()` does not require naming the class that it is part of, making its use simpler and removing a maintenance issue. The trickiest issue with the use of `super()` is that, in the presence of multiple inheritance, there is no way for a class to know for certain which inherited method will be called. In particular, this means that the calling signature (arguments) for all versions of a method must be compatible. As a result, there are a few argument-related caveats about the use of `super()` in multiple inheritance hierarchies: * Only pass `super()` the exact arguments you received. * When you use it on methods whose acceptable arguments can be altered on a subclass via addition of more optional arguments, always accept `*args`, `**kw`, and call `super()` like `super().currentmethod(alltheargsideclared, *args, **kwargs)`. If you don’t do this, forbid addition of optional arguments in subclasses. * Never use positional arguments in `__init__` or `__new__`. Always use keyword args, and always call them as keywords, and always pass all keywords on to `super()`. To use `super()` with multiple inheritance, all base classes in Python's Method Resolution Order need to use `super()`; otherwise the calling chain gets interrupted. If your class may be used in multiple inheritance, ensure that all relevant classes use `super()`, including documenting requirements for subclasses. Following these guidelines for single inheritance hierarchies, will let them be extended to multiple inheritance with minimal difficulty. {code}
| 1 |
2,521 |
DM-18249
|
11/10/2017 08:59:40
|
SAL features - add authList support to XML
|
Detailed design
| 2 |
2,522 |
DM-12587
|
11/10/2017 09:22:23
|
Use minikube for travis-ci
|
* Improve Qserv container version management: use tag for Qserv container (produced with git describe (--parent?)) * Build run-kubectl container at runtime with a given version or install kubectl * What about qserv/qserv:dev container? * add qserv_deploy to qserv_distrib? * Try to speed up the build... (reduce container image size)
| 8 |
2,523 |
DM-12588
|
11/10/2017 10:49:40
|
Port validate_drp documenattion
|
The code in {{validate_drp}} was ported to use {{verify}} in DM-12253, but that did not include porting the documentation. This ticket is to update documentation in {{validate_drp}} for API changes as well as general docstring cleanup.
| 2 |
2,524 |
DM-12593
|
11/13/2017 08:40:42
|
Use HSC S17A Junk List to validate CompareWarp
|
Use Junk list from Matsuoka-san to validate CompareWarpAssemble
| 2 |
2,525 |
DM-12596
|
11/13/2017 10:55:54
|
AstrometryTask.distort broken
|
The changes in DM-5922 were not propagated to {{AstrometryTask.distort}} in {{meas_extensions_astrometryNet}} so that method is broken. The fix is trivial.
| 1 |
2,526 |
DM-12610
|
11/13/2017 16:00:15
|
Document lsst-dev filesystems
|
{{lsst-dev01}} has access to all the GPFS filesystems available to the Verification Cluster (ie, as documented at https://developer.lsst.io/services/verification.html#verification-gpfs). However, if you didn't already know that, you wouldn't discover it by reading https://developer.lsst.io/services/lsst-dev.html. Please cross-link this documentation appropriately.
| 1 |
2,527 |
DM-12611
|
11/13/2017 21:13:38
|
FrameDict(FrameSet const &) broken
|
FrameDict(FrameSet const &) results in an unusable FrameDict in C++ because AST has already reclaimed the raw pointer. pybind11 avoids the issue, so it is difficult to test in Python. Add a simple C++ function that Python can call to induce the problem, call it from {{test_frameDict.py}} to demonstrate the problem, then fix the problem.
| 1 |
2,528 |
DM-12615
|
11/14/2017 11:00:03
|
Add copy-constructors to astshim objects
|
Most astshim objects do not provide a copy-constructor (motivated by the discussion in DM-9174?). This means that to copy an object, one needs complex statements like {{Object(std::move(*object.copy()))}}. Since astshim objects can be copied anyway through {{copy}} or a temporary object, adding a copy-constructor would allow for more idiomatic C++. The copy-constructor could be implemented either by indirect constructions like the one above, or by something more efficient.
| 1 |
2,529 |
DM-12616
|
11/14/2017 12:25:29
|
BUG: partial decimated data returned on repeated request
|
Using slate-demo-explicit2.ipynb from firefly_client examples. If the request is reissued (last cell reloaded) before the first one completes, partial results (100 pts instead of ~1000) are returned for heatmap. (See attached.) Controlling pageSize in DecimationProcessor.java fetchData does not work when the cached version of the data is returned. We need to pass pageSize from the client.
| 2 |
2,530 |
DM-12652
|
11/14/2017 16:17:59
|
code change to deal with 32bit mask layer in LSST image
|
Update the code to auto-generate the mask layers for all 32 bits when the mask extension is detected in the image.
| 2 |
2,531 |
DM-12658
|
11/15/2017 10:20:51
|
base_PixelFlags_flag_clipped not getting set on measurements on CompareWarp Coadds
|
Catalogs measured from CompareWarpCoadds don't have {{base_PixelFlags_flag_clipped}} set if clipped. The only reason SafeClipped coadds do is because the coadd masks are manually set before writing out as a workaround for: DM-9953. {code} # Set the coadd CLIPPED mask from the footprints since currently pixels that are masked # do not get propagated maskExp = retStruct.coaddExposure.getMaskedImage().getMask() maskExp |= maskClip {code} I"m going to add this to CompareWarp, but we should remember to remove it from both when DM-9953 is finished.
| 2 |
2,532 |
DM-12660
|
11/15/2017 14:16:33
|
Install test and study a local k8s installer
|
this local installer could be used for running integration tests on travis-ci.
| 5 |
2,533 |
DM-12667
|
11/16/2017 09:40:12
|
Implement minimal Butler POSIX Datastore prototype
|
Implement a minimal Butler Datastore (as defined in DMTN-056) backed by a POSIX filesystem. The intent of this ticket is to build a minimum prototype for testing purposes to be used with either the Registry from DM-12613 (or DM-12371). This prototype is to be as simple as possible but should be useable to inform decisions about pluggability, chaining, caching and API layering for later versions.
| 8 |
2,534 |
DM-12675
|
11/16/2017 15:21:23
|
Developer guide inaccurately summarises issue semantics
|
https://developer.lsst.io/processes/workflow.html#tickets makes various claims about the association of different types of issue (story/bug/improvement) with epics. In particular, it claims that "bug" and "improvement" type issues are not associated with epics. This is simply incorrect: bugs and improvements should be associated with epics in just the same way as stories, and are treated identically for the purposes of earned value accounting. (I think this bad documentation is based on a misunderstanding of the outcome of RFC-43.)
| 1 |
2,535 |
DM-12690
|
11/16/2017 17:25:02
|
Make ConstrainedPolyModel actually support initFromWCS
|
While sorting out the best approach for getting jointcal to ingest a SkyWcs, we discovered that the {{ConstrainedPolyModel}} was ignoring the {{initFromWCS}} constructor boolean flag. Looking at the history, it appears it was never used: the chip transfo was always being initialized with the input WCS. This is an easy fix, and I'll also make it a configurable, so we can test how larger datasets behave when it is {{False}}; the testdata all appears to be fine (initial chi2 is different, but it quickly settles down to the same value).
| 0.5 |
2,536 |
DM-12692
|
11/17/2017 08:30:22
|
Improve temporal threshold for CompareWarp
|
An integer maxNumEpochs is too crude. The original fraction temporalThreshold of the number warps entering an image is too crude. Evaluate and test a fraction with a floor based on the local N_epochs.
| 2 |
2,537 |
DM-12694
|
11/17/2017 09:52:11
|
Add queue option for allocateNodes.py
|
Following IHS-612, there will be multiple slurm queues on LSSTVC. It would be great to be able to tell {{allocateNodes.py}} which queue to send jobs to.
| 1 |
2,538 |
DM-12697
|
11/17/2017 13:12:15
|
Fix hollowed out cores of saturated stars in CompareWarp
|
Thus far I've been clipping any any region for which we don't have information from the PSF-matched warp. This includes more area than direct warp because of matching kernel smears out the bad pixels and edges of calexps. Test allowing saturated pixels through. Merge if it works.
| 3 |
2,539 |
DM-12700
|
11/17/2017 14:28:01
|
Flip CompareWarpAssembleCoaddTask on by default for RC and ci_hsc
|
Switch defaults everywhere (not just obs_subaru coaddDriver). Includes running ci_hsc with CompareWarpAssembleCoadd.
| 2 |
2,540 |
DM-12701
|
11/17/2017 15:51:37
|
Update showVisitSkyMap.py for unique visit and tract identification
|
Update the color mapping of the visit outlines such that each visit gets a unique color. Also add a legend with the visit numbers such that they can be identified in the plot. Additionally, allow for multiple tracts to be specified and have their outlines drawn on the plot with unique gray-scaling and added to the legend.
| 1 |
2,541 |
DM-12712
|
11/17/2017 17:15:21
|
Update LDM-148 for Commissioning Review
|
Adjust text and diagrams to match service designs. Submit RFC to baseline new version.
| 20 |
2,542 |
DM-12718
|
11/17/2017 17:18:51
|
Investigate alternatives for packaging/build infrastructure
|
Investigate and propose an alternative to current product/package structure and packaging and build tools. Submit an RFC or determine that one is not timely.
| 40 |
2,543 |
DM-12720
|
11/17/2017 17:21:20
|
Prepare and execute 15.0 release
|
Ensure that all of the following steps are executed, performing as many as possible directly and training on each: * Identify any pre-release blockers (“must-have features”) * Track blockers to closure * Eups publish rc1 candidate * Git Tag v15.0-rc1 * Github release lsst_demo 15.0 * Branch 15.0 of newinstall.sh (lsst) * Track any latent bugs to closure * Repeat with additional -rcN candidates * Confirm DM Externals are at stable tags * Tag DM Auxiliary (non-lsst_distrib) repos * Perform full OS testing (see https://ls.st/faq2 ) * Git Tag 15.0, rebuild, eups publish * Produce factory binaries * Test factory binaries * Gather contributed binaries * Update Prereqs/Install * Update Known Issues * Gather Release notes * Gather Metrics report * Email announcement
| 40 |
2,544 |
DM-12721
|
11/17/2017 17:34:41
|
SUIT and Firefly deployment in docker
|
deployment of SUIT, PDAC using docker technology
| 0 |
2,545 |
DM-12764
|
11/20/2017 11:07:54
|
Overhaul SkyWcs
|
As part of DM-10765 it became apparently that SkyWcs needed many changes, including: - Do not inherit from Transform - Add FITS binary table persistence - Add missing functionality as methods or free functions In addition, it is possible to greatly simplify the code using the new {{ast::FrameDict}} class. [~jbosch] suggested, and I agree, that it is better to do the SkyWcs overhaul on a ticket separate than DM-10765, making DM-10765 itself smaller and more focused.
| 20 |
2,546 |
DM-12765
|
11/20/2017 11:11:10
|
Record filter ratios in HSC coadds
|
This is the most minimal version of DM-12366, requested by NAOJ. It makes sense to do it on a separate ticket. This will mostly be highly HSC-specific code, as it's a lot harder to come up with a way to report fractions of different filters used when you can have more than two filters and arbitrary names for them; for HSC we know exactly which pairs of filters we need to take ratios of.
| 1 |
2,547 |
DM-12766
|
11/20/2017 11:14:16
|
coaddDriver with --cores > 1 produces MPI_Abort(MPI_COMM_WORLD, 1)
|
To reproduce, the first one with --cores=1 works, but second with --cores=2 does not: {code} source /software/lsstsw/stack/loadLSST.bash setup lsst_distrib export wideVisitsG=9852^9856^9860^9864^9868^9870^9888^9890^9898^9900^9904^9906^9912^11568^11572^11576^11582^11588^11590^11596^11598 coaddDriver.py /datasets/hsc/repo --rerun RC/w_2017_46/DM-12545:private/yusra/psfMatching/newStack --time 500 --cores=1 --id tract=8766 patch=5,5 filter=HSC-G --selectId ccd=0..8^10..103 visit=$wideVisitsG coaddDriver.py /datasets/hsc/repo --rerun RC/w_2017_46/DM-12545:private/yusra/psfMatching/newStack --time 500 --cores=2 --id tract=8766 patch=5,5 filter=HSC-G --selectId ccd=0..8^10..103 visit=$wideVisitsG {code} Note to get any useful output you'd need to either switch: makeCoaddTempExp.doApplyUbercal=False AssembleCoadd.doApplyUbercal=False OR setup meas_mosaic (which I currently can't build with the python3 stack)
| 1 |
2,548 |
DM-12771
|
11/20/2017 13:23:18
|
Support the new FitsChan SipReplace attribute
|
Add support for the new {{FitsChan}} attribute {{SipReplace}}. This makes AST believe the inverse SIP coefficients and will be usable in DM-12764 to improve the accuracy of SkyWcs.skyToPixels for WCS with SIP terms.
| 1 |
2,549 |
DM-12780
|
11/21/2017 11:00:16
|
prune eups.lsst.code s3 backups
|
The daily backups for {{s3://eups.lsst.codes}} were growing unbounded. Backups have been prune down to retain only the 1st day of each month prior to the current month. Eg. {code:java} #!/bin/bash #set -e set -o xtrace for m in {4..10}; do mon=$(printf "%02d" $m) for d in {2..30}; do day=$(printf "%02d" $d) aws s3 rm --recursive "s3://eups.lsst.codes-backups/2017/${mon}/${day}" & done done {code} Either a rotation script is needed or s3 object expiration needs to be set. Ie., backups on every day but the first of the month have a 30 day expiration set on the objects.
| 2 |
2,550 |
DM-12783
|
11/21/2017 12:11:22
|
Normalize weights differently for morphology and SED updates
|
It is believed that the problems with bad colors in HSC-Z and Y that we observed in DM-12776 are due to the way we are using inverse variance maps to weight gradient steps in the deblender. When two bands have substantially different mean variance, certain colors converge more quickly than other colors, and at all times are capable of taking larger steps toward the minimum, which we believe results in poor colors in the bands with higher variance. Similarly, images with widely varying pixel variances could also see some pixels reaching convergence more quickly than others (although we have not observed this directly). To combat this [~pmelchior] and I propose to normalize the weights for SED updates along each band, so that only pixel by pixel variations are weighted for each SED update, and normalize the weights for morphologies along each single band image. This should give us more uniform convergence and hopefully solve DM-12776 as well.
| 1 |
2,551 |
DM-12794
|
11/21/2017 16:05:23
|
Fix Qserv dev container (and Travis CI) builds
|
The recent upgrade of the python3 baseline after stack release 14.0 seems to have busted the Qserv container builds (and thus Travis CI for Qserv)
| 1 |
2,552 |
DM-12802
|
11/22/2017 14:07:00
|
Add shape measurements to coadd comparison.
|
Add ext_shapeHSM_HsmShapeRegauss_e1, ext_shapeHSM_HsmShapeRegauss_e2, ext_shapeHSM_HsmShapeRegauss_resolution to the coadd comparison script to aid with assessing changes relevant to shear measurements.
| 1 |
2,553 |
DM-12815
|
11/27/2017 14:56:35
|
convert jenkins jenkins-ebs-snapshot job to pipeline
|
This trivial job needs to be converted to pipeline in order to implement timeouts.
| 0.5 |
2,554 |
DM-12818
|
11/27/2017 16:44:10
|
CSS needs new parameter for match table separation.
|
Currently qana uses database-global "ovelap" value as a match table "separation" parameter which is wrong. Database-global "ovelap" is supposed to be a default overlap value for tables that don't define their own overlap. Match table separation is not really related to overlap, so to reduce confusion we need to add new parameter to match table configuration in CSS and use is to set qana parameters.
| 3 |
2,555 |
DM-12819
|
11/27/2017 19:22:09
|
Explore possible reduction of memory footprint needed for image cutouts
|
Currently, ImageServ is passing data id to butler to retrieve the FULL image from the underlying fits file, before performing the cutout per user-specified dimensions, in a 2-step process. It may be possible to combine the two steps into a single one, in the following manner: image = butler.get(dataset_type, bbox=bbox, immediate=True, tract=tract, patch=patch, filter=filterName) Note: bbox dimensions always in pixels.
| 5 |
2,556 |
DM-12848
|
11/28/2017 12:16:15
|
ap_verify unit tests fail on lsst-dev
|
One of the unit tests for {{ap_verify}} tests whether its running-time metrics return a sensible time for a dummy Task execution. Because the task is a dummy, it almost immediately raises an exception, allowing the timing code to run. However, on {{lsst-dev}} (and, so far, only {{lsst-dev}}), the running time returned is equal to {{0.0 * astropy.units.second}}, failing a test for a positive value. This result should be investigated and, if necessary, the test modified to return a nontrivial result. The assertion should not be removed if at all possible, because a measurement of zero could result from incorrect propagation of {{None}} or other invalid values.
| 2 |
2,557 |
DM-12854
|
11/28/2017 16:28:20
|
ongoing jenkins dockerd/xfs errors
|
Jenkins jobs that use docker are frequently hanging and {{dockerd}} / {{xfs}} errors are appearing in the {{dmesg}}: {code:java} [279961.166094] INFO: task dockerd:902 blocked for more than 120 seconds. [279961.169742] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [279961.173508] dockerd D ffff8800a188e010 0 902 1 0x00000080 [279961.176932] ffff880033883d78 0000000000000086 ffff8803bb2e8fd0 ffff880033883fd8 [279961.180601] ffff880033883fd8 ffff880033883fd8 ffff8803bb2e8fd0 ffff8800a188e000 [279961.184682] ffff8800a188e040 ffff88036f27c140 ffff8800a188e068 ffff8800a188e010 [279961.188403] Call Trace: [279961.190270] [<ffffffff816a94e9>] schedule+0x29/0x70 [279961.193155] [<ffffffffc01732ea>] xfs_ail_push_all_sync+0xba/0x110 [xfs] [279961.196618] [<ffffffff810b1910>] ? wake_up_atomic_t+0x30/0x30 [279961.199554] [<ffffffffc015c2e1>] xfs_unmountfs+0x71/0x1c0 [xfs] [279961.202526] [<ffffffffc015cded>] ? xfs_mru_cache_destroy+0x6d/0xa0 [xfs] [279961.205747] [<ffffffffc015ee92>] xfs_fs_put_super+0x32/0x90 [xfs] [279961.209261] [<ffffffff81203722>] generic_shutdown_super+0x72/0x100 [279961.212640] [<ffffffff81203b67>] kill_block_super+0x27/0x70 [279961.215738] [<ffffffff81203ea9>] deactivate_locked_super+0x49/0x60 [279961.218801] [<ffffffff81204616>] deactivate_super+0x46/0x60 [279961.221628] [<ffffffff8122184f>] cleanup_mnt+0x3f/0x80 [279961.224301] [<ffffffff812218e2>] __cleanup_mnt+0x12/0x20 [279961.227135] [<ffffffff810ad247>] task_work_run+0xa7/0xf0 [279961.230449] [<ffffffff8102ab62>] do_notify_resume+0x92/0xb0 [279961.233768] [<ffffffff816b52bd>] int_signal+0x12/0x17 {code} These problems seem to go away, at least for awhile, after the node is restarted (they will not soft reboot). It isn't yet known if this is a kernel bug or some of random EBS I/O timeouts. As it seems to be only (?) triggered by dockerd, it seems much more likely to be a kernel issue. What is unusual is that this doesn't seem to have been an issue until ~ a week ago and this doesn't correlate with a kernel or dockerd version change.
| 5 |
2,558 |
DM-12861
|
11/29/2017 12:49:08
|
jenkins s3backup-eups job is failing
|
The last several {{s3backup-eups}} builds have failed. Eg., https://ci.lsst.codes/job/sqre/job/backup/job/s3backup-eups/215/consoleFull {code:java} copy failed: s3://****/stack/redhat/el6/devtoolset-3/miniconda3-4.3.21-10a4fa6/[email protected] to s3://****/2017/11/29/2017-11-29T12:12:10Z/stack/redhat/el6/devtoolset-3/miniconda3-4.3.21-10a4fa6/[email protected] An error occurred (InvalidArgument) when calling the UploadPartCopy operation: Range specified is not valid for source object of size: 27092590 {code}
| 0.5 |
2,559 |
DM-12873
|
11/30/2017 12:31:28
|
Run pipe_analysis scripts on w_46-processed RC data at NCSA
|
In support of the LDM-534 QA milestone, run {{coaddAnalysis.py}}, {{colorAnalysis.py}} and {{visitAnalysis.py}} on all coadds and visits from the weekly 46 RC processing run (/datasets/hsc/repo/rerun/RC/w_2017_46/DM-12545/).
| 2 |
2,560 |
DM-12881
|
12/01/2017 00:30:12
|
coaddDriver tries to unset doMatchBackgrounds, which does not exist
|
See https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1426
| 0.5 |
2,561 |
DM-12882
|
12/01/2017 07:59:35
|
Frequent catastrophic misalignment in coadd inputs
|
Catastrophically bad WCSs that print through to the coadd seem to have much more common between _42 (where they were basically nonexistent) and _46. This manifests both as duplicated sources and bad clipping.
| 2 |
2,562 |
DM-12890
|
12/01/2017 10:15:30
|
Remove imageREST_v0 (deprecated API) wrapper from code base.
|
As is imageREST_v0 API (URL pattern/style) is already supported on top of v1 code base. Once we transition over to imageREST_v1, which can be seen as v0++ from functionality standpoint, there is really no need for the old v0 code (isolated to a few files) to remain in the code base.
| 1 |
2,563 |
DM-12894
|
12/01/2017 10:49:54
|
Comments on "beta" HiPS viewing in Firefly
|
Congratulations on getting HiPS viewing going in Firefly! In general it looks really good. I have mostly minor comments of a wide variety, which I will post as a document attached to this ticket.
| 2 |
2,564 |
DM-12909
|
12/01/2017 18:10:06
|
Test failure in meas_mosaic
|
Carelessness in the merge of DM-12882 led to a failing unit test. Fixing it now.
| 0.5 |
2,565 |
DM-12924
|
12/05/2017 16:34:04
|
SpherePoint.offset should work at the poles and for negative offsets
|
In replacing Coord with SpherePoint (DM-11162) I discovered a problem in the skymap package: skymap makes heavy use of Coord.offset, including for points at a pole. However, SpherePoint rejects such offsets (as well as negative offsets). I believe the behavior of {{offset}} for a coord at the pole is unambiguous and unsurprising if the coord is constructed from longitude, latitude. However, I acknowledge that this is less so for a coord constructed from a 3-vector. Nonetheless, I propose to change the behavior of SpherePoint to match Coord and document the behavior at the pole. I also propose to allow negative offsets, as the intent is unambiguous for those and Coord supports it. Also make sure the sign convention for the orientation of offset is the same for {{SpherePoint}} as {{Coord}} and document it carefully.
| 1 |
2,566 |
DM-12937
|
12/06/2017 15:33:22
|
Image retrieval via v0 API for 'i' band deep coadd returning index out of range
|
The error response should have been along the line of 'image not found'. Just for record, deepcoadd cutouts for bands other than r result in the `IndexError: list index out of range`. Example: `http://lsst-qserv-dax01.ncsa.illinois.edu:5003/image/v0/deepCoadd?ra=9.6&dec=-1.1&filter=i`
| 5 |
2,567 |
DM-12938
|
12/06/2017 15:53:44
|
ap_pipe crashes if --output is absolute path
|
If {{ap_pipe}} is called with an absolute path as its {{--output}} directory, it will crash soon after attempting to ingest defects with a message like: {noformat} ap.pipe.defectIngest INFO: Ingesting defects... usage: ap_pipe.py input [options] ap_pipe.py: error: Error: input='[partialdir]/[outputdir]/ingested' not found {noformat} A similar error appears if {{--output}} is relative and the working directory is anything other than the parent of {{\[outputdir]}}. I suspect the problem is because {{defectIngest}} assumes {{repo}} must be a path relative to the output directory's parent, but have not tested to make sure.
| 2 |
2,568 |
DM-12940
|
12/06/2017 16:58:21
|
Catch the error when adding marker or footprint to a plot without image (due to image search failure)
|
For the plot with no image due to an image search failure, some running error occurs while adding a marker or a footprint to that plot. The marker/footprint adding should skip the undefined plot or the plot with no image.
| 1 |
2,569 |
DM-12943
|
12/06/2017 17:59:37
|
Investigate coadd covariance impact on detection kernels
|
Determine the correlation matrix empirically from blank patches of sky on a coadd, then see if we can construct a detection kernel that corrects for it.
| 2 |
2,570 |
DM-12949
|
12/07/2017 12:12:13
|
Filtering table from scatter chart fails when column expressions are involved
|
The error is: "...from data where ("w1mpro-w2mpro" > -1.3191681767193026) and ("w1mpro-w2mpro" < -0.7958581413409266) and ("w3mpro" > 8.643434512115258) and ("w3mpro" < 13.130081532416503) ) as b) WITH DATA]; nested exception is java.sql.SQLSyntaxErrorException: user lacks privilege or object not found: w1mpro-w2mpro from:null" Here "w1mpro-w2mpro" should probably be "w1mpro"-"w2mpro" 12/14/2017 TG https://github.com/Caltech-IPAC/firefly/pull/516 - now using db to calculate column expression values for general charts (we used expression lib before) - fixed filter from chart when column expressions are used - allow same columns to be used for x and y - fixed filtering issues for expressions with alpha-numeric columns. Unfortunately, if a column name contains space, filter will not work the second time, because filter parser is using space as a delimiter. Created DM-13037 for this issue. - updated histogram request to get the expression calculation in the database. - fixed selection bug in heatmap I have introduced when checking that user is selecting active trace. - created tickets for outstanding column expression issues: DM-13036 Use db to calculate expressions for decimation (heatmap data) DM-13039 Use custom database functions for column expressions functions not supported by DB DM-13038 Support column expressions for column names that are not alpha-numeric
| 8 |
2,571 |
DM-12968
|
12/11/2017 14:08:33
|
Include INTERP+CR pixels in coadds
|
I think we agreed at the 2018-12-11 Monday Meeting that it's better to included interpolated CR pixels in the coadd (since the interpolation is pretty good) rather than leave them out and get lots more pixels masked with INEXACT_PSF. [~price], if you're in a position to do this quickly before the next HSC release, please steal it. Otherwise I'll try to get to it later.
| 1 |
2,572 |
DM-12969
|
12/11/2017 14:10:30
|
Configure LDM/DMTR docs on Travis for LSST the Docs
|
This ticket covers effort associated with configuring LDM and DMTR (LaTeX documents) for deployment on LSST the Docs.
| 2 |
2,573 |
DM-12972
|
12/11/2017 14:48:06
|
Write paper on deblender
|
[~pmelchior] has been writing up a paper based on the new deblender. For my part I will help write some sections of the paper, including results from tests on both HSC and Sim data.
| 8 |
2,574 |
DM-12980
|
12/12/2017 10:01:52
|
Add display_firefly to lsst_distrib
|
This ticket implements RFC-421. {{display_firefly}} will be added as {{setupRequired}} to the table file in {{lsst_distrib}}.
| 1 |
2,575 |
DM-12992
|
12/12/2017 17:08:30
|
Confirm access to the newly loaded NEOWISE data table
|
confirm that the newly loaded NEOWISE data table is accessible through current DAX service
| 1 |
2,576 |
DM-13037
|
12/14/2017 11:14:38
|
Second filter fails on column names with spaces (NED)
|
If a column name contains space, filter will not work the second time, because filter parser is using space as a delimiter. (see parse in FilterInfo.js) Test case: NED catalog search. Using table filters, filter on "Redshift Points" in table, then filter on "Distance". Alternatively, create a chart with the columns that contain spaces, filter from the chart. The second filter is producing a db error.
| 3 |
2,577 |
DM-13041
|
12/14/2017 14:25:10
|
Attend Galaxy and Cosmology Class in Dec
|
Attend Michael Strauss and Jenny Greene's observational galactic astronomy class to better understand the scientific applications of the deblender. There are only 2 weeks of class this month.
| 2 |
2,578 |
DM-13045
|
12/15/2017 09:38:14
|
Test new deblender on simulated data
|
Before updating the stack API (DM-12404) and testing the deblender on HSC data (DM-11330), we should make sure that the new version works on the same simulated data as well or better than the previous version.
| 5 |
2,579 |
DM-13052
|
12/15/2017 16:53:15
|
AssociationTask does not call update on associated DIAObjects
|
After running ap_pipe and ap_verify the L1DB produced by AssociationTask does not update the values of the stored DIAObjects. This causes the appearance that each DIAObject is associated with only one DIASource. This ticket will fix this case.
| 2 |
2,580 |
DM-13054
|
12/15/2017 18:53:24
|
Add colorterm config support to jointcal
|
[~boutigny]'s work on color terms in u/fix_outliers should help improve the photometry models. This ticket is to port over [~boutigny]'s work in the u/fix_outliers branch (specifically this commit: https://github.com/lsst/jointcal/commit/e1d0292c71275315a6b17b67ecaf47acd2ffbee8 ) to use {{ReferenceSourceSelectorTask}}, add a unittest to demonstrate that the color terms do affect the fit (for both the simple, and constrained models), and update the other tests to reflect any changes in the fit metrics.
| 8 |
2,581 |
DM-13055
|
12/17/2017 18:11:22
|
reject NaN centroid sigmas in astrometrySourceSelector
|
Jointcal is still getting NaNs in some of the HSC PDR1 data. It appears that finite errors are not guaranteed by the centroid_flag, so we have to reject non-finite Sigmas during source selection. For now, we'll add it to astrometrySourceSelector, but we'll have to think of a better solution since this will affect all source selectors.
| 1 |
2,582 |
DM-13073
|
12/18/2017 16:22:38
|
Add CCOB Milestone test in LDM-503
|
Update LDM-503 to include approriate tests for handling data from Camera Calibration Optical Bench (CCOB). This may only be possible after the Feb meeting which sets the CCOB schedule.
| 1 |
2,583 |
DM-13080
|
12/19/2017 12:45:29
|
Add reference band flags used for forced coadd measurements to persisted parquet tables
|
It is very useful for qa/debugging to know which band was used as the reference band for the measurements in forced photometry on the coadds. These are currently only persisted in the *deepCoadd_ref* output file, so will need to read these in and add the appropriate columns to the parquet tables.
| 2 |
2,584 |
DM-13082
|
12/19/2017 13:44:19
|
test failure due to DM-12968 config move
|
It was not in fact safe to move the badMaskPlanes config option from CoaddBaseTask to AssembleCoaddTask. Master is broken.
| 0.5 |
2,585 |
DM-13084
|
12/19/2017 14:16:39
|
Be smarter about combining metadata from FITS headers
|
Our afw code that reads FITS headers for images and exposures works as follows: - It reads the metadata (as a PropertySet or PropertyList) from the first HDU - It reads the metadata from the next HDU (the image plane) - It combines them using PropertySet.combine If the same keyword is present in both sets of metadata, this can cause problems. For example: - In some files LTV[12] is specified as 0 in the first HDU and -XY0 as a float in the image HDU. This causes a failure with a complaint about mismatched types. Even if the type is int in the second HDU we end up with an array of values which is not what we want. - In some files NAXIS[12] is specified as 0 in the first HDU and typical values in the next HDU. This results in an array value for NAXIS[12], which is not what we want. My suggestion is to write a free function that combines metadata in a FITS-friendly manner: - For a select few FITS-specific keywords, including COMMENT and HISTORY, use the current behavior: every time the keyword is found, add its value to an array. Require that the types match. - For all other keywords, when a name is re-used, keep only the most recent version. Do not require that the types match.
| 2 |
2,586 |
DM-13096
|
12/20/2017 15:35:39
|
Add refraction calculation to the stack
|
Add a calculation of atmospheric refraction and utilities for differential refraction to the stack. These calculations are needed for the DCR-corrected templates that are being written in DM-9615, but they can be made more general and separated from the rest of the DCR code.
| 2 |
2,587 |
DM-13099
|
12/20/2017 18:24:32
|
Can't set only one axis binning value on decimated plot
|
In the decimated plots, I can't change the number of bins in the x-direction only. I enter a number, hit apply, and nothing happens. Seems that i have to set both axis. Can we use a default value for the one that is not filled in?
| 3 |
2,588 |
DM-13116
|
12/21/2017 23:13:57
|
Implement weighted strict monotonicity
|
The strict monotonicity projection using only the nearest neighbor creates fractal-like unphysical features and affects the accuracy of the deblender. This ticket is to implement a strict, weighted monotonicity projection similar to the weighted monotonicity operator that calculates the radial gradient. For speed, this will have to be written in C++.
| 2 |
2,589 |
DM-13123
|
12/22/2017 12:56:14
|
Doxygen search broken
|
When I visit http://doxygen.lsst.codes/stack/doxygen/x_masterDoxyDoc/index.html, type something into the search box, and hit enter, I get a {{search.php}} file to download in response. Obviously, I should get search results. This was discussed on DM-10544, but doesn't seem to have actually been fixed there (or, if it was, it has subsequently broken again).
| 1 |
2,590 |
DM-13126
|
12/22/2017 13:31:08
|
possible bug in pixel coord readout
|
From Robert's input #7 in DM-8409: Pixel coords are off by (0.5, 0.5) – the middle of the bottom left pixel should be (0, 0) (i.e. offset by (1, 1) from the fits standard, which assumes fortran-style 1-indexed arrays) *(#7)*
| 0 |
2,591 |
DM-13129
|
12/22/2017 13:47:46
|
Warnings in test_camGeomFitsUtils.py
|
test_camGeomFitsUtils.py issues warnings that appear to be bugs we should fix. Examples: {code} /Users/rowen/UW/LSST/lsstsw3/build/afw/python/lsst/afw/cameraGeom/fitsUtils.py:76: UserWarning: WARNING: Failed to set setName attribute with None value: setName(): incompatible function arguments. The following argument types are supported: 1. (self: lsst.afw.table.ampInfo.ampInfo.AmpInfoRecord, name: str) -> None ... /Users/rowen/UW/LSST/lsstsw3/build/afw/python/lsst/afw/cameraGeom/fitsUtils.py:76: UserWarning: WARNING: Failed to set setBBox attribute with None value: setBBox(): incompatible function arguments. The following argument types are supported: 1. (self: lsst.afw.table.ampInfo.ampInfo.AmpInfoRecord, bbox: lsst.afw.geom.box.Box2I) -> None {code} See attached log for more info
| 0.5 |
2,592 |
DM-13134
|
12/22/2017 14:26:19
|
Firefly Python API: disp.pan(0,0) is ignored
|
Robert's input #9, DM-7321 disp.pan(0, 0) is ignored (I think anything below (0.5, 0.5) fails). I'd expect to be able to pan any point to the centre of the display, but I'd certainly expect that it'd clip to a valid coord not silently ignore my request)
| 3 |
2,593 |
DM-13135
|
12/22/2017 14:28:00
|
Firefly Python API: need to deal with killing Firefly display window
|
Robert's input #10, DM-7321 Killing the firefly display window seems to leave the notebook that's talking to it perfectly happy, but it doesn't respawn the window even if I call the constructor again.
| 0 |
2,594 |
DM-13136
|
12/22/2017 16:23:11
|
Investigate processing failure of HiTS visit 411657, ccd 47
|
During the DM-503-3 processing, we encountered an error for HiTS dataId visit 411657, ccd 47, filter='g': {code} File "/software/lsstsw/stack3_20171023/stack/miniconda3-4.3.21-10a4fa6/ Linux64/meas_algorithms/14.0-7-g23fdbe95+15/python/lsst/meas/algorithms/ measureApCorr.py", line 251, in run (name, len(subset2), self.config.minDegreesOfFreedom+1)) RuntimeError: Unable to measure aperture correction for required algorithm 'base_PsfFlux': only 0 sources, but require at least 2. {code} Further investigation shows that 6 PSF sources are selected, but all have self.refFluxKeys.flag set, so they raise the error above in {{measureApCorr}}. This ticket is to investigate the root cause of the failure to select usable PSF sources.
| 2 |
2,595 |
DM-13144
|
12/28/2017 02:47:22
|
Launch S15 large scale test @ cc-in2p3
|
Non regression on Qserv performances
| 3 |
2,596 |
DM-13145
|
12/28/2017 10:25:02
|
Fix LTD Dasher's title truncation
|
LTD Dasher trims document handles from titles to protect from cases where the document handle was accidentally inserted into the document title string. But for test reports, the title legitimately includes a document handle (but for a different document). See https://dmtr-53.lsst.io/v/index.html The fix is to only trim the document's own handle from a title (and only if it occurs as a distinct word unit).
| 0.5 |
2,597 |
DM-13162
|
01/03/2018 14:11:03
|
Fix warning in processEimage
|
`processEimage.py` currently loads the metadata of a simulated observation twice and runs the same code both times, except it only provides a mapper the second time. This generates a warning the first time the code is run, and is unnecessary because the second call provides the correct exposure with VisitInfo.
| 0.5 |
2,598 |
DM-13166
|
01/04/2018 09:02:39
|
Update AST to add support for writing SIP terms
|
Update AST to the latest version, which adds support for writing SIP terms to FITS headers.
| 0.5 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.