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,299 |
DM-6617
|
06/21/2016 10:08:30
|
Catalog Search Panel bugs
|
from pull request DM-6500: https://github.com/Caltech-IPAC/firefly/pull/102 * 2MASS All-Sky 'Read Me!' link in Catalog Search panel points to http://localhost:8080/irsaviewer/Q'http://hades.ipac.caltech.edu/applications/Gator/GatorAid/irsa/scan.html'E * -If you search m31 2MASS scan info catalog (4th catalog in the list), then bring back catalog panel, the first catalog is highlighted, but if you search, you'll notice that you are still searching 2MASS scan info.-
| 2 |
1,300 |
DM-6620
|
06/21/2016 13:20:18
|
Cannot instantiate LoadAstrometryNetObjectsTask without Config object
|
One should be able to create a LoadAstrometryNetObjectsTask without passing a Config object, if one only wants the default configuration. Currently it raises TypeError: {code} Traceback (most recent call last): File "testJointcal.py", line 79, in setUp refLoader = LoadAstrometryNetObjectsTask() TypeError: __init__() takes at least 2 arguments (1 given) {code} If the config object really is a kwarg, it should default None and create a default config, so that one doesn't have to do, e.g.: {code} LoadAstrometryNetObjectsTask(LoadAstrometryNetObjectsConfig()) {code}
| 0.5 |
1,301 |
DM-6627
|
06/21/2016 14:39:09
|
Fix base_* stuff in CcdImage.cc
|
CcdImage.cc currently has hard-coded a bunch of {{getSchema().find("base_blah").key}} things. These should either be replaced with "slot_*", config.blahName, or dealt with at a higher level (e.g. not loading all those values directly inside of ccdImage::LoadCatalog). Once this is done, we should delete the comments at the top of the file.
| 1 |
1,302 |
DM-6630
|
06/21/2016 17:02:41
|
Support ingesting reference catalogs from FITS files
|
Support a means of ingesting index reference catalogs from FITS tables (e.g. SDSS catalogs).
| 2 |
1,303 |
DM-6631
|
06/22/2016 04:12:34
|
Single-frame processing tasks are no longer usable without a Butler
|
Adding a butler argument to the constructor signatures for {{CharacterizeImageTask}}, {{CalibrateTask}}, and {{ProcessCcdTask}} makes these tasks difficult to use without a butler. The fix is to make the butler argument optional (with a default of None), while adding another argument that allows a fully-constructed reference object loader to be provided directly instead. This is closely related to DM-6597, which has the opposite problem: pipe_drivers' {{SingleFrameDriverTask}} doesn't take a butler argument, but it needs to in order to provide one to {{ProcessCcdTask}}. I have a fix for this just about ready, but I'd like to add some unit tests that verify we can run all of these tasks both from the command-line and directly before calling it complete.
| 3 |
1,304 |
DM-6633
|
06/22/2016 05:31:23
|
HSC ISR configuration file is applied to ProcessCcdTask, not IsrTask
|
{{obs_subaru/config/hsc/isr.py}} has its config options specified relative to {{ProcessCcdTask}}'s config hierarchy, not {{IsrTask}}'s. This allows the ISR task to be retargeted in this file, but it will prevent {{IsrTask}} from being run as a {{CmdLineTask}} directly. ISR Task retargeting should be moved to {{config/processCcd.py}}, allowing the {{config/isr.py}} level to be moved to the appropriate level.
| 1 |
1,305 |
DM-6635
|
06/22/2016 08:14:07
|
Typo in CoaddSrcTransformTask
|
[~price] points out a typo [in {{CoaddSrcTransformTask}}|https://github.com/lsst/pipe_tasks/blob/0eef0fd518098cc25c66bfff40f53ccca9058431/python/lsst/pipe/tasks/transformMeasurement.py#L263]: {{self}} should not be repeated.
| 1 |
1,306 |
DM-6638
|
06/22/2016 13:35:52
|
LTD Keeper: Auto slug for edition paths deals with underscores
|
Had a bug where {{utils.auto_slugify_edition}} did not replace underscores with a dash, and therefore failed {{utils.validate_path_slug}}. This created a silent breaked where a branch like {{u/rowen/r12_patch1}} did not get an edition created for it. This ticket adds this replacement code and adds a test for such a case.
| 0.5 |
1,307 |
DM-6647
|
06/23/2016 09:49:06
|
Adapt qa analysis script to apply corrections measured by meas_mosaic
|
DM-2674 involves getting HSC's {{meas_mosaic}} working with the LSST stack. This issue consists of adapting the analysis.py script of DM-4393 & DM-4730 to (optionally) apply the astrometric and photometric solutions derived running {{meas_mosaic}} to the individual visits before comparison. This is useful in general and is specifically useful in comparing the {{meas_mosaic}} results between the HSC and LSST stacks.
| 2 |
1,308 |
DM-6651
|
06/23/2016 12:14:49
|
Move new reference loader so meas_astrom can use it and perform some cleanup
|
The new reference object loader code lives in pipe_tasks, which means it cannot be directly used by code in meas_astrom. This will hamper separating astrometry.net out of meas_astrom, because unit tests need reference catalogs and meas_astrom cannot depend on pipe_tasks. Also, I'd like to take a cleanup pass on the module names, so the new code is easier to find, and improve the unit tests.
| 2 |
1,309 |
DM-6652
|
06/23/2016 12:16:37
|
Remove database hack
|
DM-5988 introduced a hack in reading the raw files: we use a database to cache metadata from the shutter files and update the camera files at read time. The camera files have now been "sanitised" (updated with the appropriate metadata), and it's time to remove the hack. [~mfisherlevine] writes: {quote} Data is on lsst-dev in: /nfs/lsst2/photocalData/data/monocam/sanitised9/1m3/1m3 Raw calibs are in: /nfs/lsst2/photocalData/data/monocam/sanitised9/1m3/calibs Regarding what I want: everything to be the same, but with a normal ingest, i.e. no splicing, just taking everything that is needed from one set of files. Some points to note: * should be able to ingest all the raws and calibs files, and register their OBJECT types to allow processing with these as ids (inc. pipe_drivers scripts) * pipe_drivers master calib scripts should still run (and their outputs still be ingestable) * processCcd should run {quote}
| 2 |
1,310 |
DM-6653
|
06/23/2016 12:40:21
|
implement the active target
|
When a dialog such as catalog search is displayed, it should be able to pick up the active target or the coordinates from a highlighted row in a table. Please, implement the mechanism that will automatically pick up those coordinates and pre-fill the search form for you.
| 0.5 |
1,311 |
DM-6657
|
06/23/2016 17:05:42
|
ffApi XYplot related issues found by irsa integration
|
* default symbol size, shape,and color setting is different from that of original version. * no XY Plot Options pop-out windows * the plot displays non-ascii characters on the panel (for example: Fit ) * miss Filter Dialog on the plot panel comparing with the original version. * does not accept default column names for the plot.
| 1 |
1,312 |
DM-6660
|
06/23/2016 20:13:55
|
CR finder does not care about XY0 of input image
|
Port of [HSC-1391|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1391]: {quote} The current version of CR finder does not care about XY0 of the input image and when I try to run CR finder on warped (difference) image, PSF cannot be properly extracted. {quote} and: {quote} I have noticed that the center of warped image is a gap between CCDs and PSF estimation there will fail. So get PSF without specifying the position is good enough. PSF class will select the best position. {quote}
| 0.5 |
1,313 |
DM-6661
|
06/23/2016 20:35:08
|
ConfigDictField says "Inequality in keys for..." even if I give 2 same configurations
|
From [HSC-1401|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1401]: {quote} config.py: {code:python} from lsst.meas.photocal.colorterms import ColortermGroupConfig for key in ['i', 'i2', 'y', 'r', 'N1', 'N2', 'N3', 'z']: root.calibrate.photocal.colorterms.library[key] = ColortermGroupConfig.fromValues({}){code} This comamnd line {code:bash} rm -fr output ; for i in {1..2} ; do processCcd.py ./HSC --output output -C config.py ; done {code} raises following error {noformat} 2016-06-01T02:43:45: processCcd FATAL: Comparing configuration: Inequality in keys for calibrate.photocal.colorterms.library: ['z', 'i', 'i2', 'r', 'y', 'N1', 'N2', 'N3'] != ['N3', 'i', 'i2', 'r', 'y', 'N1', 'N2', 'z'] 2016-06-01T02:43:45: processCcd FATAL: Failed in task initialization: Config does match existing config on disk for this task; tasks configurations must be consistent within the same output repo (override with --clobber-config) {noformat} {quote}
| 0.5 |
1,314 |
DM-6663
|
06/24/2016 10:47:21
|
Study iPlant as a potential candidate for workspace implementation
|
in 2015 iPlant was rebranded to CyVerse (http://www.cyverse.org/) with a revised mandate to serve all life sciences. CyVerse's Data Store is based on technology iRODS (http://irods.org/). CYVerse's Atmosphere provides a managing portal for users's VM instances and data spaces called volume. The instance and volume is tied under a project. There are other tools and UIs under CyVerse. Data Store and Atmosphere are very close to what we wanted for LSST workspace. It provides many VM instance images preconfigured for life sciences domain-specific tasks. We could definitely learn from this if LSST provides the VM for its users. LSST could supply instance images with specific astronomical tools preconfigured. Deciding if the CyVerse could be used as LSST workspace implementation will need much more study and discussion with other teams involved in workspace design and implementation. The direction we are going with Jupyter Notebook and JupyterHub most likely preclude us from using CyVerse directly.
| 2 |
1,315 |
DM-6701
|
06/24/2016 16:21:39
|
Specify requirements for SuperTask extensions
|
Specify requirements for SuperTask extensions according to the use cases and architecture.
| 2 |
1,316 |
DM-6718
|
06/27/2016 14:20:07
|
afw table and record should have useful str() and repr()
|
To see the contents of an afw table in python, you have to do something like {code}catalog[0].extract("*"){code} which is totally not discoverable and returns a dict which doesn't print well. Much more useful would be for str() on a record to produce a pretty-printed list of the contents, and str() on a table to produce some nicely formatted summary (like a numpy recarray does, only printing a few things separated "..." for large tables). I'm not sure what the best repr() output would be (certainly for a Record it should be a full dump of the contents), but currently table.repr()==table.str(), which is equally unhelpful. Maybe this will come "for free" when we get astropy.table views, but it makes exploring the contents of a table a pain right now.
| 2 |
1,317 |
DM-6784
|
06/28/2016 16:40:08
|
Port meas_extensions_convolved from HSC
|
HSC has a new measurement extension: meas_extensions_convolved. This performs aperture photometry with the PSF degraded to nominated seeings (similar to how galaxy photometry is commonly done these days). Relevant HSC tickets are [HSC-1395|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1395] and [HSC-1408|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1408].
| 5 |
1,318 |
DM-6785
|
06/28/2016 16:44:59
|
Port parent/child measurement from HSC
|
The deblender sometimes gets into trouble with cluster galaxies, and the deblended fluxes aren't accurate. In that case it helps to have measurements on the image without any deblending having been performed. This is a feature used in HSC's mid-2016 production run afterburner, ticket [HSC-1400|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1400]. This feature should be ported for use in LSST.
| 5 |
1,319 |
DM-6788
|
06/29/2016 10:54:31
|
Document meas_extensions_ngmix
|
meas_extensions_ngmix has no useful documentation, not even a {{doc}} directory. Add some. This should include at least an overview of the package contents, a description of its capabilities, and instructions on enabling it within the meas_base framework. The package should have a README.
| 2 |
1,320 |
DM-6823
|
06/29/2016 15:59:18
|
Add new boilerplate to introduction of SQR-012
|
SQR-012 provides details of how the new unittests should be written, but it only gives an example of the old testing boilerplate in the introduction. It would be very helpful to have the first thing a reader sees be the new, correct, boilerplate, so they can immediately drop it into a new testing file.
| 2 |
1,321 |
DM-6824
|
06/29/2016 18:15:40
|
Use meas.algorithms.astrometrySourceSelector in measOptimisticB
|
Now that there is a working astrometrySourceSelector (just merged in meas_algorithms from DM-5933), we should get matchOptimisticB working with it. This would entail replacing matchOptimisticB.SourceInfo with AstrometrySourceSelectorTask and tweaking the latter to do whatever matchOptimisticB needs, and removing SourceInfo.
| 2 |
1,322 |
DM-6831
|
06/30/2016 13:50:01
|
Wrap base with pybind11
|
Split off from DM-6302.
| 2 |
1,323 |
DM-6832
|
06/30/2016 13:50:50
|
Wrap utils with pybind11
|
Split off from DM-6302.
| 2 |
1,324 |
DM-6833
|
06/30/2016 22:24:37
|
add 'placeholder' attribute to the input element
|
An attribute called placholder is available in html element <input> to give a hint to the user of what can be entered. The placeholder text must not contain carriage returns or line-feeds. Add it as proptype to <inputfield> component.
| 1 |
1,325 |
DM-6857
|
07/01/2016 11:16:00
|
Document that the catalog returned from star selectors is a view
|
Star selectors return a catalog whose records are shallow copies of the input catalog records. Document the shallow copy aspect. This is important for two reasons: - The user should know - Implementers must be told this, because if the records are deep copies then the code that sets a flag for stars will not set a flag in the input catalog, which loses most of the point of setting that flag.
| 0.5 |
1,326 |
DM-6858
|
07/01/2016 12:34:47
|
Mapper tests require modification when new datasets are added
|
[~price] [recommends|https://community.lsst.org/t/centrally-defined-butler-datasets/841] a new way to define datasets common to all cameras in daf_butlerUtils, but modifying these yaml files require explicit lists of datasets to be modified in tests/cameraMapper.py. If these tests are still useful, they need to depend on a minimal set of dataset definitions instead of the real ones.
| 2 |
1,327 |
DM-6886
|
07/05/2016 04:42:36
|
forcedPhotCoadd.py fails on CFHT data due to a CModel bug
|
Hello, forcedPhotCoadd fails while running on CFHT data due to a CModel bug. Here is an example on the error message that we get: {code} python: src/CModel.cc:1368: void lsst::meas::modelfit::CModelAlgorithm::measure(lsst::afw::table::SourceRecord&, const lsst::afw::image::Exposure<float>&, const lsst::afw::table::SourceRecord&) const: Assertion `measRecord.getFootprint()->getArea()' failed. Aborted {code} Adding the following lines in cmodel.py (in CModelForcedPlugin.measure, before the call to self.algorithm.measure) allows to go around the problem for the time being, which seems to arise for null value of the number of pixel in a given footprint: {code} if not measRecord.getFootprint().getArea(): raise ValueError("measRecord.getFootprint().getArea(): 0. No pixel in this footprint.") {code}
| 1 |
1,328 |
DM-6903
|
07/06/2016 14:04:58
|
Add an option to label ccd serial number on the showVisitSkyMap.py plot
|
(actual assignee: Samuel Piehl) Sometimes it is useful to know where the CCDs are on the plot. Add an option to label the CCD numbers.
| 0.5 |
1,329 |
DM-6905
|
07/06/2016 16:43:50
|
Locate the test dataset for PDAC
|
Locate and evaluate a dataset of SDSS Stripe82 which is going to be used for testing the prototype DAC.
| 2 |
1,330 |
DM-6909
|
07/06/2016 18:46:11
|
Filtering from expanded mode cancels expanded mode
|
When a table is filtered from the expanded mode, the layout is changed back to unexpanded. It looks like the issue is more general: table actions trigger layout changes, which are not always right. For example, TABLE_REMOVE action while in a dropdown makes the dropdown to get closed. I've traced it to FireflyLayoutManager.js:layoutManager generator function. Test sequence in firefly: - When a table is loaded, open "Charts" dropdown, select Col link for X, then select Col link for Y. (At this point the previous table is removed). - TABLE_REMOVE action on the second click triggers dropdown to go away.
| 2 |
1,331 |
DM-6910
|
07/06/2016 18:50:26
|
Tab panel issues
|
There are several issues with tab titles: - Sometimes we don't want them to be resized at all (like in Images panel since the tabs are all fixed at begining) - When titles are resized, their size is proportional to the length of the title, use fixed-size tab length instead to make sure no tab is too long. Please add other tab panel issues here.
| 3 |
1,332 |
DM-6914
|
07/07/2016 10:58:41
|
git-lfs.lsst.codes certificate is expired
|
Per reports on hipchat, the tls certifcate on git-lfs.lsst.codes was not upgraded to the new *.lsst.codes cert. {code:java} John Swinbank 9:52 AM @josh @jmatt I'm seeing the following, which I think might be the same as @srp's error above. Any ideas? Get https://git-lfs.lsst.codes/objects/24874b686b9479a823987dc2bd2700cad5b73e74a43108fb61b91d7f79f0cd99: x509: certificate has expired or is not yet valid Followed by git lfs failing. (I assumed it was user error on my part at first, but if so it's coincidence that Steve's git lfs fails at the same time.) {code}
| 1 |
1,333 |
DM-6916
|
07/07/2016 12:53:17
|
Documenteer seeds Git revision date and branch name if not present in metadata.yaml
|
If {{last_revised}} and {{version}} are not present in metadata.yaml, then the Git commit date and branch name should be used while building metadata instead. Also updates lsst-technote-bootstrap to take advantage of automated metadata for new projects.
| 0.5 |
1,334 |
DM-6922
|
07/08/2016 02:34:27
|
Upgrade to new stack install procedure for containers
|
LSST stack install has evolved: https://pipelines.lsst.io/install/newinstall.html# Release container creation script needs to be update. Latest Docker version will be tested, as [~bvan] reported cmd line options have changed.
| 2 |
1,335 |
DM-6923
|
07/08/2016 08:11:40
|
Apply distortion when searching for astrometric reference objects
|
While investigating DM-6529 I found that LSST generally finds fewer reference objects than HSC when doing astrometry. For the CCDs on the edge of the focal plane the number of stars was typically very low causing frequent failures. I found that in the HSC code, there is a distortion being applied that shifts the exposure bounding box when getting objects from the reference catalog. This distortion is not being applied in the LSST code.
| 1 |
1,336 |
DM-6929
|
07/12/2016 07:35:47
|
Image Viewer: Support circular selection
|
Support circular selection by choosing a point and dragging the mouse across the image. The callbacks and functions supported for rectangular selection should be also supported for circular selection. (Circular region selection is a part of Paul O'Connor's visualization wish list and is a long promised feature.) Copied from GitHub(XW 1/18/18) This development includes, * adding circular selection support for area selection. * change select area icon on the tool bar from on/off button to a on/off button with dropdown selection at off state. The dropdown list supports the selection for 'rectangular selection', 'elliptical section' (circular area). * add stats calculation for circular area selection on both rotated and non-rotated images. * fix stats calculation for rectangular area selection on rotated image case. * update 'select catalog' and 'filter catalog' functions for circular area selection. Test: - Do image selection: 1. Click 'select area' icon (on 'off' state) to get selection dropdown list, 2. Select either 'rectangular selection' or 'elliptical selection' (this will move the 'select area' icon into 'on' state) and draw a selected area by choosing a point over the image and dragging the mouse across the image. 3. Click 'select area' icon to move it back to 'off' state to remove the selected area. 4. Select one of the extension buttons for 'crop', 'stats', 'zoom', or 'recenter' while either 'rectangular selection' or 'elliptical selection' is selected. - Repeat the steps by rotating the image first. - Do catalog selection next: repeat the 'select area' steps done as image selection, and select one of the extension buttons for 'crop', 'stats', 'select mark data', 'filter', 'zoom' or 'recenter' while either 'rectangular selection' or 'elliptical selection' is selected.
| 8 |
1,337 |
DM-6945
|
07/13/2016 15:24:12
|
Add text to algorithmic components sections in LDM-151
|
While [~swinbank] has commented that the outlines are probably good enough for planning work (and I thnk that's broadly true), the lack of text in the algorithmic components section did occasionally lead to some misunderstandings in [~rhl]'s first review pass, so I think I should flesh that out with text sooner rather than later. In this issue, I'll stick to sections that no one else has added text for, but eventually I'll also need to work with [~krughoff] and perhaps others to ensure that section has a consistent level of detail and focus.
| 8 |
1,338 |
DM-6949
|
07/13/2016 18:22:17
|
Firefly has problem to render in other browsers than Chrome
|
Couple of problem using Firefly in Safari: * the components appears blank, in Firefox: * image and xyplot are not aligned (Gator). The alignment can be reproduced in my Chrome and Safari. Search parameters: ALLWISE source catalog, m81 100arcsec.
| 1 |
1,339 |
DM-6968
|
07/15/2016 13:43:33
|
create a shared stack on NFS for use with the current local condor pool
|
It is well known that building, setting up a stack, and interactive devel work with those operations on NFS has performance issues. Hence the official shared stack on lsstdev uses /ssd . However, a shared stack on NFS is useful and adequate for one important use case -- users need a stack that can be used for small productions on the local condor pool currently available on lsstdev. For this use case multiple "source"/"setups" on a node/against the file system can be avoidable by using a script to directly declare the environment. run_orca /ctrl_orca supports this feature. While GPFS is coming soon, there is expected to be a transition period of 2-3 months and so the NFS file system and a stack on it can serve users for an interim period. If building a shared stack on NFS is not a heavy labor, we think it is worth the effort for this interim period, and as such make this request for a shared stack on NFS.
| 1 |
1,340 |
DM-6969
|
07/15/2016 16:44:31
|
Fixes to LoadIndexedReferenceObjects
|
Bug fixes for using the new {{LoadIndexedReferenceObjectTask}} and its associated components.
| 2 |
1,341 |
DM-6972
|
07/18/2016 15:43:40
|
Fix Qserv install doc and scripts for new newinstall.sh
|
Update qserv install docs per new info at https://pipelines.lsst.io/install/newinstall.html
| 1 |
1,342 |
DM-6974
|
07/18/2016 17:33:01
|
Type of IngestIndexedReferenceTask_config wrong in obs_ paf files
|
In DM-6651 I moved the new HTM indexed reference catalog code from pipe_tasks to meas_algorithms, but didn't do a complete job. The type of IngestIndexedReferenceTask_config in obs_ paf files still must be updated.
| 1 |
1,343 |
DM-6976
|
07/19/2016 12:09:55
|
watch for Highcharts update
|
There is an issue in the density plot for displaying the legends. Highcharts does not support the setting of the symbol size in the legends. So when the symbol size is too small or too large, the legends are not displayed. We don't want to do too much workaround currently. This ticket is to watch for the Highcharts update.
| 1 |
1,344 |
DM-6978
|
07/19/2016 12:22:42
|
Update qserv for changes in Log interface
|
DM-6521 improved Log class interface by replacing some static methods with non-static. Qserv is currently using couple of static methods which were retained in Log class for the duration of this migration. Once updated log package is released update qserv code to use new non-static methods and remove static methods from Log class after that.
| 2 |
1,345 |
DM-6979
|
07/19/2016 12:26:38
|
Firefly strategy response to RFC-193 (f17)
|
RFC-193 has been adopted. "we propose to replace the current World Coordinate System handling and XYTransform code in the LSST stack with Starlink AST, using a new API that is under development in DM-3874 (that API will have its own RFC). " How does Firefly respond to this and display images as accurately as possible?
| 20 |
1,346 |
DM-6981
|
07/19/2016 18:04:11
|
Add column setters for Flag types in catalogs
|
It should be possible to set Flag columns with bool arrays or scalar values. This should just be a matter of adding a {{set}} overload or two around line 100 of {{specializations.i}}.
| 1 |
1,347 |
DM-6982
|
07/20/2016 09:58:59
|
Fix oversampling settings in psfex
|
The current settings in psfex will only turn on oversampling only if the seeing is < 0.5", even if you have configured it do oversampling. This needs to be changed so that everything is determined by the config parameters. We have also seen on HSC data that oversampling in general does not work well in psfex. We need to change the current configuration which does 2x oversampling to just use the native pixel scale.
| 1 |
1,348 |
DM-6983
|
07/20/2016 10:09:11
|
ci_hsc failure: AttributeError: 'Butler' object has no attribute 'repository'
|
Following [~npease]'s [recent changes to the Butler|https://community.lsst.org/t/im-checking-in-butler-changes-related-to-rfc-184/959], ci_hsc is failing as follows: {code} [2016-07-20T07:57:31.954576Z] Traceback (most recent call last): [2016-07-20T07:57:31.954643Z] File "/home/jenkins-slave/workspace/stack-os-matrix/compiler/gcc/label/centos-7/python/py2/lsstsw/build/ci_hsc/bin/validate.py", line 3, in <module> [2016-07-20T07:57:31.954664Z] main() [2016-07-20T07:57:31.954732Z] File "/home/jenkins-slave/workspace/stack-os-matrix/compiler/gcc/label/centos-7/python/py2/lsstsw/build/ci_hsc/python/lsst/ci/hsc/validate.py", line 53, in main [2016-07-20T07:57:31.954756Z] validator.run(dataId) [2016-07-20T07:57:31.954825Z] File "/home/jenkins-slave/workspace/stack-os-matrix/compiler/gcc/label/centos-7/python/py2/lsstsw/build/ci_hsc/python/lsst/ci/hsc/validate.py", line 155, in run [2016-07-20T07:57:31.954851Z] self.validateDataset(dataId, ds) [2016-07-20T07:57:31.954923Z] File "/home/jenkins-slave/workspace/stack-os-matrix/compiler/gcc/label/centos-7/python/py2/lsstsw/build/ci_hsc/python/lsst/ci/hsc/validate.py", line 117, in validateDataset [2016-07-20T07:57:31.954956Z] mappers = self.butler.repository.mappers() [2016-07-20T07:57:31.954991Z] AttributeError: 'Butler' object has no attribute 'repository' [2016-07-20T07:57:32.023212Z] scons: *** [.scons/ingestValidation-903342-100] Error 1 {code} See e.g. https://ci.lsst.codes/job/stack-os-matrix/13274/compiler=gcc,label=centos-7,python=py2/console. Please fix it.
| 1 |
1,349 |
DM-6984
|
07/20/2016 13:49:41
|
Suggest logging migration in daf_persistence and daf_butlerUtils
|
Use lsst::log instead of pex::logging in daf_persistence and daf_butlerUtils
| 2 |
1,350 |
DM-6987
|
07/20/2016 16:45:20
|
Write up a description of Composite Datasets based on input from KT
|
Write a description of composite datasets as I understand them based on the email KT sent on May 20 (attached), and on conversation I had with KT and Fritz on July 20.
| 2 |
1,351 |
DM-6989
|
07/20/2016 16:59:52
|
ctrl_events/tests/EventAppenderTest.py fails Jenkins run-rebuild
|
ctrl_events/tests/EventAppenderTest.py started failing on Jenkins "run-rebuild" last night: https://ci.lsst.codes/job/run-rebuild/354//console All test cases in EventAppenderTest.py did run and pass, but it failed with a Segmentation fault in the end. Jenkins "run-rebuild" uses a stack on NFS on lsst-dev (/nfs/home/lsstsw). The same test passes on regular Jenkins (stack-os-matrix).
| 3 |
1,352 |
DM-6996
|
07/20/2016 21:51:35
|
produce a draft document of SUIT requirements
|
After combing through the current SUIT requirements, we feel that we need to re-organize and re-write the SUIT requirements to be in-line with SUIT vision document. This story will be producing the first draft of the rewrite.
| 20 |
1,353 |
DM-6998
|
07/21/2016 07:07:48
|
Problems with MemoryTest ordering
|
{{MemoryTestCase}} (or a derivative thereof) must be run as the last of all tests in a module in order to properly catch leaks. [Our documentation|https://developer.lsst.io/coding/python_testing.html#memory-and-file-descriptor-leak-testing] implies, and [SQR-012 states|https://sqr-012.lsst.io/#memory-test], that this can be achieved by listing it as the last test case in the file. This works for py.test, but not when using plain old unittest: the latter does not, so far as I can see, guarantee any sort of ordering as a matter of principle, and, in practice, it sorts things lexicographically (it uses whatever order it gets from running {{dir()}} on the test module, and I don't *think* that's guaranteed to be anything in particular). For example, consider [{{testAstrometrySourceSelector.py}}|https://github.com/lsst/meas_algorithms/blob/master/tests/testAstrometrySourceSelector.py]. I made the following change to introduce a memory leak: {code} --- a/tests/testAstrometrySourceSelector.py +++ b/tests/testAstrometrySourceSelector.py @@ -70,8 +70,9 @@ class TestAstrometrySourceSelector(lsst.utils.tests.TestCase): self.sourceSelector = sourceSelector.sourceSelectorRegistry['astrometry']() def tearDown(self): - del self.src - del self.sourceSelector + pass + #del self.src + #del self.sourceSelector def testSelectSources_good(self): for i in range(5): {code} Py.test catches it: {code} $ py.test-2.7 testAstrometrySourceSelector.py [...] testAstrometrySourceSelector.py .........F [...] {code} But simply running the test suite does not: {code} $ python testAstrometrySourceSelector.py .......... ---------------------------------------------------------------------- Ran 10 tests in 0.105s {code} Rename the test case: {code} @@ -144,7 +145,7 @@ def setup_module(module): lsst.utils.tests.init() -class MyMemoryTestCase(lsst.utils.tests.MemoryTestCase): +class xMyMemoryTestCase(lsst.utils.tests.MemoryTestCase): pass if __name__ == "__main__": {code} And boom: {code} $ python testAstrometrySourceSelector.py ......... 54 Objects leaked: {code} Based on a very quick check, I think [sconsUtils runs tests by simply invoking {{python}}|https://github.com/lsst/sconsUtils/blob/f9763768d999cefa4c26b9f3418c28394dfb38df/python/lsst/sconsUtils/tests.py#L133], and I'm pretty sure that this is hard-wired into the muscle memory of many developers. In these cases, memory tests written following current guidelines won't be being properly executed.
| 3 |
1,354 |
DM-6999
|
07/21/2016 11:26:29
|
Use lsst::log in pipe_base and pipe_tasks
|
Per RFC-203, switch Task's logs from using pex.logging to lsst.log in pipe_base and pipe_tasks (stage 2) This implements the main idea of RFC-203 and migrate the logging framework used in the task framework.
| 8 |
1,355 |
DM-7008
|
07/22/2016 16:38:39
|
Check boost.python building with Python 3
|
We may want to disable boost.python in the build. There are hints that there are problems with python3.5.
| 0.5 |
1,356 |
DM-7010
|
07/25/2016 08:46:47
|
Builds should be optimised by default
|
By default, our builds are not optimised ({{-O0}}), which requires everyone who doesn't want to wait until the heat death of the universe to set {{SCONSFLAGS="opt=3"}}, but other packages that are built with scons may not recognise this. This default is also contrary to the standard practise for open-source software, which is that by default builds are optimised. I will change the default optimisation level to {{opt=3}} from the current {{opt=0}}. I will also add support for {{-Og}}. This change was approved in RFC-202.
| 0.5 |
1,357 |
DM-7014
|
07/25/2016 12:45:42
|
Memory cache leak in firefly server
|
The visualization system is not update the memory accounting for the caching system.
| 2 |
1,358 |
DM-7016
|
07/25/2016 12:54:47
|
Big image not showing working message when the load
|
This is a problem with uploads, large image loads, and Atlas. When a big image is loading the user does not get feedback. The problem is the the UI is not creating the ImageViewer soon enough.
| 2 |
1,359 |
DM-7018
|
07/25/2016 16:08:22
|
Firefly distribution build
|
We need to support regular Firefly distribution builds (with bundled tomcat server), similar to the builds we did in lsst firefly repository before the conversion. This is to get Camera team started with new API.
| 2 |
1,360 |
DM-7019
|
07/25/2016 16:24:06
|
Setup standalone Firefly build using IPAC github
|
Modify the existing Firefly-Standalone build in Jenkins to use IPAC's github. Make sure github auto-releases still works.
| 3 |
1,361 |
DM-7021
|
07/26/2016 08:53:02
|
Update pex_exceptions to support Python 3
|
{{pex_exceptions}} needs to be updated to support Python 3.
| 1 |
1,362 |
DM-7027
|
07/26/2016 13:28:19
|
Region issues
|
There are several region issues I have found when comparing old and new API: (1, 2, 3, 7, 8 are implemented in DM-7147, 4, 5, 6 are implemented in DM-7190) 1. The default coordinate system when "pure numbers" are used should be pixel positions on the original image. The [spec](http://ds9.si.edu/doc/ref/region.html) says the following: "...the default system is implicitly assumed to be PHYSICAL. In practice this means that for IMAGE and PHYSICAL systems, pure numbers are pixels." 'If no coordinate system is specified, PHYSICAL is assumed.' More explanation can be found [here](http://hea-www.harvard.edu/RD/funtools/regcoords.html) 2. PHYSICAL coordinate system does not mean screen pixels. The question is whether we can always use image pixels. _If wcs is "physical", WCS is the pixel coordinate system of the original image, which may be different from the pixel coordinate system of the current image, if the current image is the result of an imcopy or other geometric transformation operation. In the "physical" coordinate system the ltv, ltm and the axis attribute parameters wtype, axtype, units, label, and format may be edited, but the FITS parameters crval, crpix, and cd cannot_. [reference](http://stsdas.stsci.edu/cgi-bin/gethelp.cgi?wcsedit) 3. When used in API, the actions are dispatched one after another. For example, dispatchCreateRegionLayer might be issued before image plot has finished loading. Can we make regionCreateLayerActionCreator wait for image with plotId to finish loading? More details: If I create a region layer with a few regions in image coordinates right after firefly.showImage, two errors are loaded to console: doOnAppReady: uncaught TypeError: Cannot read property 'getImageCoords' of null(…), RegionFactory:602: Uncaught (in promise) TypeError: Cannot read property 'getImageCoords' of null(…) 4. When a region is selected, yellow dashed line appears around it. On zoom the line does not change color. 5. Can not add empty region. Line 124 of the test script. 6. Can not add or delete regions after the first one. (Load test script, click Show Regions, then Add Region, line 121 of the test script) When there is one region in the layer and you are adding another region with a different position but everything else the same, the added region is perceived to be the same. 7. It's possible to select regions only in in the first region layer added. In the other layer, you can sometimes see the selection blinking, but it does not stay. 8. If region format is wrong, for example 'image; box 40 400 72 72 # color=blue' instead of 'image; box 40 400 72 72 0 # color=blue', the region is silently ignored, no warning or error is logged to console. 9. We need region selection action to support callbacks on region selection. (Currently the selected region is "calculated internally based on the distance between the region and mouse readout.)
| 1 |
1,363 |
DM-7028
|
07/26/2016 14:22:55
|
Port daf_base to Python 3
|
Changes necessary to get daf_base to work with Python 3.
| 0.5 |
1,364 |
DM-7031
|
07/27/2016 06:22:33
|
Assign initial responsibilities in LDM-151
|
Assign first thoughts on responsibilities to all software primitives and algorithmic components. This is my take. Simon will have his own take.
| 2 |
1,365 |
DM-7039
|
07/27/2016 09:58:25
|
Familiarization with Footprint redesign
|
Familiarize yourself with the RFC-37 driven Footprint redesign. Start thinking about ideas for how you could implement it and what the transition plan from the current Footprints might be. A great outcome would be to propose a set of stories which would tackle the new Footprint development effort. A good outcome would not be to have the stories ready to go, but to be well prepared for a discussion with [~jbosch] & [~swinbank] where we'll come up with some stories as a group.
| 5 |
1,366 |
DM-7040
|
07/27/2016 10:30:59
|
Stars selected by starSelector change when number of cores varies
|
Sogo Mineo writes in [HSC-1414|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1414]: {quote} See the following lines: meas_algorithms/HSC-4.0.0/python/lsst/meas/algorithms/objectSizeStarSelector.py:466 in ObjectSizeStarSelector.selectStars(): {code} if psfCandidate.getWidth() == 0: psfCandidate.setBorderWidth(self._borderWidth) psfCandidate.setWidth(self._kernelSize + 2*self._borderWidth) psfCandidate.setHeight(self._kernelSize + 2*self._borderWidth) {code} In reduceFrames, these lines set the width of psfCandidate to be 21 for the first time the execution reaches there. When the first CCD image has been processed, the worker process continues to process another CCD image, and the execution reaches here again. This time, psfCandidate.getWidth() is 41, because psfexPsfDeterminer has set it to be 41, and the value has been retained because the width is a static member. And so, for the second CCD image, the width of psfCandidate is not 21 but 41. Since psfCandidates are widened, stars positioned at edges of images are rejected. It results in a smaller number of PSF candidates than expected. Only CCD images that are initially given to the worker processes are processed with psfCandidate.getWidth() == 21. The other CCD images are processed with psfCandidate.getWidth() == 41. When the number of SMP cores changes, CCD images are processed with different parameters. The change in the number of PSF candidates results in different Psf, a different result of image repair, and different catalogs. {quote} The line numbers are different on the LSST side because of refactoring (objectSizeStarSelector.py:466 has moved to starSelector.py:148), but the bug is still present. The main problem appears to be that the {{PsfCandidate}} elements are {{static}}, are being set in both the star selector and the PSF determiner and one of those is conditional on what the value is. I will investigate moving the {{static}} class variables to instance variables --- the desired size appears to vary by context, so it shouldn't be a class variable.
| 2 |
1,367 |
DM-7043
|
07/27/2016 10:51:44
|
Update SQuaSH database model and JSON API with concepts from validate_drp measurement API
|
In DM-6629, a new measurement API was introduced into validate_drp that established a JSON data model for metrics, specifications of metrics, measurements, and general blob datasets. The intent of that work is to enable rich plots in the SQUASH dashboard, with access to data behind measurements. The new data model also clarifies the subtleties of metric specifications (filter dependence, and dependence on other specifications). This ticket will incorporate validate_drp’s new data model into the SQUASH database and API. Also related to DM-7041, which will update the post-qa tool that submits validate_drp json to the SQUASH API.
| 5 |
1,368 |
DM-7044
|
07/27/2016 14:12:29
|
Additional constraints on reference band selection for multiband
|
Reference band selection currently depends on the configured band priority order, with exceptions made for sources with low signal-to-noise in the high priority bands. [HSC-1411|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1411] points out that some additional qualifications, such as success for major measurements (e.g., CModel and Kron), would be helpful.
| 3 |
1,369 |
DM-7047
|
07/27/2016 16:40:30
|
Port pex_config to Python 3
|
Work involved in ensuring that pex_config passes all tests on Python 3 and legacy Python.
| 1 |
1,370 |
DM-7048
|
07/27/2016 17:28:31
|
validate_drp is failing because it's accessing butler internals that have changed
|
need to change obs_decam's ingest task to use the newer class hierarchy to get the root of the butler's single repository. (longer term there should be a butler API for this or the task should get the value of root from somewhere else)
| 1 |
1,371 |
DM-7050
|
07/28/2016 11:59:41
|
LTD Keeper: Use Google Cloud Platform SQL
|
Currently LTD Keeper uses a sqlite DB. This ticket will migrate that DB to Google’s Cloud Platform’s managed SQL. This solution provides automatic backups, and provides flexibility to run multiple ltd-keeper pods. Google’s SQL makes sense since LTD Keeper is run on Google Cloud Platform.
| 5 |
1,372 |
DM-7058
|
07/28/2016 15:20:50
|
Generate useful plots of jointcal results (I)
|
JointcalTestBase currently generates a few different plots (old vs. new WCS quiver and heat maps, relative and absolute RMS histogram) to summarize the fitting results. After showing these to people and some discussion, we came up with a number of other plots that would be very useful to help understand the fitted WCS that jointcal produces. Since figuring out how to produce some of these plots may be tricky, or may be best done after the new WCS system is in place, I'm making separate stories for them. It also would be good to have an external plotting framework that lives outside the tests.
| 20 |
1,373 |
DM-7066
|
07/29/2016 15:10:58
|
Port pex_logging to Python 3
|
Work required to get pex_logging working on python 3. Will also include some package cleanups.
| 1 |
1,374 |
DM-7067
|
07/29/2016 15:57:41
|
Break joincal's link to upstream lsst_france repo
|
lsst/jointcal is still linked to the upstream repo at lsst_france. I believe all the relevant changes have been ported. It's time to break that upstream link, so that pull requests can be made in a more obvious fashion.
| 0.5 |
1,375 |
DM-7069
|
07/29/2016 16:52:10
|
Port daf_persistence to Python 3
|
Work relating to getting daf_persistence to run on python 3. Includes some code modernization.
| 1 |
1,376 |
DM-7070
|
07/29/2016 17:45:18
|
Move consts from top of Associations.cc into JointcalConfig
|
There are three values at the top of Associations.cc under a TODO comment that should be lifted up into JointcalConfig so they can be configured at runtime. It would be good to try to add tests to check different values for them (and possibly just remove usnoMatchCut).
| 1 |
1,377 |
DM-7080
|
08/01/2016 06:34:02
|
Doxygen isn't updating
|
The current build of our Doxygen documentation, as displayed at https://lsst-web.ncsa.illinois.edu/doxygen/x_masterDoxyDoc/index.html, is labelled "Generated on Mon Jun 27 2016 03:52:22 for LSSTApplications". At time of writing, that's more than a month ago. Important additions to the documentations made during the last month are missing.
| 0.5 |
1,378 |
DM-7090
|
08/01/2016 19:46:36
|
IrsaViewer catalog panel, labels and input fields moved as you type
|
Catalog search panel in IrsaViewer, the target panel label, feedback, and input box are jumping as input is being typed. Their position should be fixed.
| 2 |
1,379 |
DM-7091
|
08/01/2016 20:16:44
|
F16 Qserv Release Mgmt
|
Developer work to support the monthly and end-of-cycle qserv releases. Includes compiling release notes, updating package dependencies, updating installation docs, minor fixes in support of new compilers, etc.
| 20 |
1,380 |
DM-7093
|
08/02/2016 12:11:59
|
Remove unused inPlace argument from PropertyList
|
In DM-1972 [~ktl] says: {quote} It looks like we don't actually use the inPlace argument to the PropertyList add and set methods anywhere in the stack besides the daf_base unit tests. I think it was originally put in to accommodate the addition of COMMENT and HISTORY items that might want to be placed at the end of the PropertyList instead of grouped together, but the implementation actually still groups all of these items together, just at the end of the list instead of where they were. If this is not actually useful, the argument could be removed and SWIG presumably appeased. {quote} This removal is no longer needed to appease SWIG but the code can usefully be removed and a test branch for this was created as part of DM-1972. This ticket will be used for the actual removal.
| 0.5 |
1,381 |
DM-7095
|
08/02/2016 15:17:38
|
Pilot Sphinx/Breath/Doxygen-generated API docs for daf_base
|
Since daf_base is low in the dependency tree and dominated by C++ APIs, it is an excellent candidate for exploring Sphinx-based package documenation for C++ with breathe and doxygen. We will also see how astropy’s automodsumm sphinx extension works with SWIG’d Python APIs. This prototype will build upon the system developed in DM-7094. Lessons from this prototype will be fed into a "Pipelines Documentation Implementation Planning" tech note in a follow-up ticket.
| 3 |
1,382 |
DM-7104
|
08/02/2016 19:34:15
|
support PDAC Qserv deploy
|
Support John in adapting scripts and methodology as necessary to support qserv deploy on the PDAC cluster at NCSA, as is currently done at IN2P3.
| 8 |
1,383 |
DM-7106
|
08/02/2016 19:41:58
|
PDAC Qserv Deploy
|
Configure cluster and adapt scripts and methodology as necessary to support qserv deploy on the PDAC cluster at NCSA, as is currently done at IN2P3.
| 13 |
1,384 |
DM-7114
|
08/03/2016 10:25:58
|
Guard against assertion failure
|
measureCoaddSources can hit an assertion failure in GalSim: {code} python: src/hsm/PSFCorr.cpp:731: void galsim::hsm::find_ellipmom_1(galsim::ConstImageView<double>, double, double, double, double, double, double&, double&, double&, double&, double&, double&, double&, boost::shared_ptr<galsim::hsm::HSMParams>): Assertion `iy1 <= iy2' failed. {code} This is due to GalSim using asserts rather than throwing an exception. We fixed this on the HSC side ({{7a73869}}), but it didn't come over because we're using GalSim as a dependency rather than sucking it into the package. I thought I reported this upstream at one point...
| 0.5 |
1,385 |
DM-7116
|
08/03/2016 12:43:36
|
Drawing layers dialog title is not updated with context image mission
|
Before migration, layers dialog title included mission name such as for example: "Layers- IRIS: 25". Now the dialog title is a fixed string: "Drawing Layers". Make the title aware of the active image with the mission name since we know about it.
| 2 |
1,386 |
DM-7117
|
08/03/2016 13:55:30
|
measureCoaddSources fails with "RuntimeError: Unable to match sources"
|
Running measureCoaddSources.py, I'm getting a {{RuntimeError: Unable to match sources}}. The patch I'm running on doesn't have a lot of pixels illuminated, so it's not surprising that there would be no matches, but that fact shouldn't cause the operation to fail. The behaviour of the matcher has changed in this respect: before the refactoring of astrometry, {{AstrometryTask.useKnownWcs}} would not raise an exception, but log an error and return an empty list of matches (it successfully matched zero sources, which might be cause for concern). I think we should fix the matcher to return an empty list (as it did previously), but perhaps a case can be made that measureCoaddSources should catch the exception and continue. I think that's wrong because measureCoaddSources would have {{matches = None}} rather than an empty list, which communicates something different ("I have no knowledge of matches" vs "I tried to match and there's nothing"); and measureCoaddSources shouldn't simply set {{matches = \[\]}} because it's not its responsibility to guess a type for what its subtask returns (breaks encapsulation).
| 1 |
1,387 |
DM-7119
|
08/03/2016 14:19:53
|
revise the Firefly README file
|
Issues to think/discuss (in README) # mention of Firefly Tools # mention of viewer, plot (for image display) # testing data location
| 1 |
1,388 |
DM-7134
|
08/04/2016 13:47:25
|
singleFrameDriver is only running with a single process
|
singleFrameDriver.py is only using a single process. The problem appears to be the change to use a {{ButlerInitializedTaskRunner}}, which doesn't inherit from {{BatchTaskRunner}}.
| 0.5 |
1,389 |
DM-7137
|
08/04/2016 15:13:25
|
utils raDecStr delimiters are untested and don't work
|
In working on DM-6320 I noticed that there do not seem to be any tests for the {{decStrToDeg}} and related functions. When I added the following test: {code:python} def testDecStrToDegDelim(self): deg = lsstutils.decStrToDeg("+15_00_00.00", "_") self.assertAlmostEqual(deg, 15.0, 6) {code} it failed with: {code} Failed to parse +15_00_00.00 as a declination with delimiter '_' and regex '([\d]+)_(\d+)_([\d\.]+)' {code} (I added some extra information to the exception). Furthermore, {{decStrToRad}} (and the equivalent RA version) do not pass through the delimiter at all: {code:C++} double ut::decStrToRad(std::string decStr, std::string delimiter) { return degToRad( decStrToDeg(decStr) ); } {code} Please add some tests. Alternatively, we could remove the delimiter option completely. It might also be worth removing the code duplication in the RA and Dec variants.
| 2 |
1,390 |
DM-7138
|
08/04/2016 20:32:09
|
Port ndarray to Python 3
|
I just tried to build LSST ndarray on Python 3 and it does not work. It's all going wrong as {{include/ndarray/swig}} seems to not be compiling. {code} In file included from tests/ndarray-python-mod.cc:25: In file included from include/ndarray/swig.h:46: In file included from include/ndarray/swig/numpy.h:33: include/ndarray/swig/PyConverter.h:175:25: error: use of undeclared identifier 'PyString_AsString' char * cs = PyString_AsString(s.get()); ^ {code} That API changed in Python 3 and it probably should be {{PyBytes_AsString}}. http://stackoverflow.com/questions/22487780/what-do-i-use-instead-of-pystring-asstring-when-loading-a-python-module-in-3-3#22491037
| 0.5 |
1,391 |
DM-7150
|
08/06/2016 15:32:29
|
Configure a default log for tests
|
The default configurations such as format and levels are different between {{lsst.pex.logging}} and {{lsst.log}}. With DM-6999 logs of command line tasks are changed from {{lsst.pex.logging}} to {{lsst.log}}. For running command line tasks, logs are configured in {{pipe_base}}. Based on RFC-203, another main use case is debug logging by running unit tests. In this case, log are not (and cannot be) configured in {{pipe_base}} command line interface. This ticket adds a default configuration in {{lsst.utils.tests}} so the default logs will look more similar to what they have been with pex.logging when running unit tests. Developers can put customized configuration in each unit test (after DM-6999).
| 1 |
1,392 |
DM-7152
|
08/07/2016 15:15:17
|
Port afw to Python 3
|
Work required to allow AFW to work on Python 3.
| 1 |
1,393 |
DM-7156
|
08/08/2016 15:26:09
|
Linter errors in daf_persistence
|
Running {{flake8}} on {{daf_persistence}} as part of DM-7069 I find two real errors. # in {{butler.py}} the {{key}} argument was removed from {{queryMetadata}} in commit 3a169f but it is still documented as being there and is still used inside the function. # {{mapper.py}} refers to class {{RepositoryMapperCfg}} but that class is not seemingly defined anywhere.
| 1 |
1,394 |
DM-7157
|
08/08/2016 15:30:09
|
Test order in daf_persistence can cause some tests to skip
|
If all tests are run from py.test as: {code} py.test tests/*.py {code} The {{DbStorage_?.py}} tests skip. If they are run without {{DbAuth.py}} running they run and pass. Something in {{DbAuth.py}} is causing the availability test to fail.
| 2 |
1,395 |
DM-7159
|
08/08/2016 17:41:40
|
Create a Light-curve viewer prototype to display time dependent dataset and compute periodogram
|
The prototype could be considered as a sort of IRSAViewer for handling LC objects / Time dependent dataset, with extra feature that would enable the existing relationship between catalog and image, in particular for WISE, PTF, which could be a reference to single-epoch image (IBE referenced URL typically). For each observation a corresponding image should be retrieved and placed in a grid (image vs time) either in the same LC object (table) or separately. One could expect that any LC data-point (time point) would be pointing to an image (single-epoch, exposure) taken from a dataset (image axis would be a 3rd dimension or a 3rd view of LC). LC should display LC object as following views: * X-Y plot (typically flux vs time) * Table * Images (corresponding image dataset single exposure at a particular time) The high-level requirements are: # Easily plot light curve # Compute Period using Lomb-Scargle # Display folded Light Curve and Periodogram # Link Light Curve Points with Single-Epoch Images # Download Cutouts and Light Curves In order to create the Light curve viewer prototype, we need to *create a skeleton app to start adding the tri-views* (Upper: plot, Bottom left: table, bottom-right: grid image): (DM-7406) * Should handle single (one position) LC (table & plot flux or magnitud vs. time, tipically 'mjd') ** For the prototype it will be a fixed table given * Image of the single exposure to be displayed at least single page mode * Should display input for computing a periodogram (the result of an API call) ** Power spectrum (Power vs log(period) ) as table and xyplot ** Peaks as a table (Power vs. period) ** Period (first Period in peak table) as a field (editable), tipically in days. In order to connect table/plot to single exposure image, be able to compute periodogram and plot based on the table focused, we need a 2 new UI components, 3 new searches and 2 new controllers (tickets will be created separately and added here): 1. UI components: * To handle the algorithm input parameters to compute ‘periodogram’ (DM-7160) * To handle the period input (DM-7161) 2. Processors: whether it is in one search processor or in different one, we need to have the following task processor: * One to deal with API to compute periodogram that will result at least in 2 tables (periodogram and peaks table, + extra output parameters fi needed) (DM-7162) * one for getting the image cutout (single exposure) (DM-7164) * one to build the phase folded curve based on (DM-7165) ** Original table searched ** Period whether it comes from the API result or any other changes from user afterward 3. Controllers: * For image to change on row or xy plot curve clicked (DM-7166) * For plotting chart based on the type of the table (power vs period, or LC or phase folded) (DM-7167)
| 8 |
1,396 |
DM-7166
|
08/08/2016 18:34:25
|
Add new controller to react when table/xy-plot is clicked to display the observed image
|
Create new controller to deal with actions on LC or periodogram or phase folded curve table and xy-plot: * on row changed, * on plot highlight. On both actions, as time changed, the image should be updated in the image grid view with the new single exposure from the dedicated search processor (see DM-7164) Note: Take into consideration that a user could select a different flux column Fixed in DM-7167.
| 0 |
1,397 |
DM-7168
|
08/09/2016 06:13:05
|
Fix Qserv CI build w.r.t xrootd upgrade
|
Qserv can't build using xrootd version tagged "qserv-dev": {code} Compiling shared object build/qdisp/QueryResource.os In file included from core/modules/qdisp/QueryResource.cc:42:0: core/modules/qdisp/QueryRequest.h:110:20: error: 'PRD_Xeq' in 'class XrdSsiRequest' does not name a type XrdSsiRequest::PRD_Xeq ProcessResponseData(char *buff, int blen, bool last) override; ^ scons: *** [build/qdisp/QueryResource.os] Error 1 {code}
| 2 |
1,398 |
DM-7170
|
08/09/2016 07:52:59
|
Implement Interface for SpanSets
|
Building off the work done in RFC-37, design a interface for a collection of sets to be called SpanSet. This should encompass most of what currently exists in afw footprints, but contain more topological set functionality.
| 3 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.