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,499 |
DM-7526
|
09/06/2016 11:22:15
|
Python Coding Standard Copy Edits
|
Content from DM-5456 has some missing words that existed during drafts. It seems that these were lost by a Git rebase. This ticket will fix this issues.
| 0.5 |
1,500 |
DM-7531
|
09/06/2016 13:01:14
|
Jenkins is no longer displaying test failure output
|
At some point in the past week or so failures from Jenkins have stopped making available the output of test {{.failed}} files or the output of the {{_build.log}} file. This makes is almost impossible to work out why Jenkins failed. Examples: https://ci.lsst.codes/job/stack-os-matrix/label=centos-6,python=py2/15505//console and from last week: https://ci.lsst.codes/job/stack-os-matrix/label=centos-6,python=py2/15194//console
| 0.5 |
1,501 |
DM-7532
|
09/06/2016 14:38:51
|
Add "disallow if False:" note to developer docs
|
This is the implementation ticket for RFC-205. The suggested additional text is given below, which probably best fits as a subsection of section 10 of the python style guide: Code must not be placed inside `if False:` or `if True:` blocks, nor left commented out. If one has debugging code or if one is undecided about which particular implementation to use, such code must be placed inside a "named" `if` statement. Such blocks may have a comment describing the conditions under which said code can be removed (e.g. completion of a ticket, a particular date). For example, for code that will likely be removed in the future, once testing is completed: {code} # Delete old_thing() and this "if" once we have all the unittests in place (DM-123456). use_old_method = False if use_old_method: old_thing() else: new_thing() {code} Such debugging flags should usually be lifted up into the method's keyword arguments to allow users to decide which branch to run. For example: {code} def foo(x, debug_plots=False): do_thing() if debug_plots: plot_thing() {code} or, using [lsstDebug|https://lsst-web.ncsa.illinois.edu/doxygen/x_masterDoxyDoc/base_debug.html], which can be controlled as part of a commandline task: {code} import lsstDebug def foo(x): do_thing() if lsstDebug.Info(__name__).debug_plots: plot_thing() {code}
| 0.5 |
1,502 |
DM-7533
|
09/06/2016 14:53:28
|
astrometry_net log is not controllable from the command line interface
|
The external logs from astrometry_net (https://github.com/dstndstn/astrometry.net) is now passed through to {{lsst.log}} with the logger name "meas.astrom.astrometry_net". But unlike other internal logger components, the astrometry_net log is not controllable from the command line intercae. I suspect a bug in [this commit|https://github.com/lsst/meas_astrom/commit/bf568b1853fdd4f49e4fbae7f2fc731a15dc76aa].
| 1 |
1,503 |
DM-7535
|
09/06/2016 14:56:42
|
list the JS source files that need JSDoc generated for JS API
|
Please make a list of JS source files that need JSDoc content updated in order to generate the JSDoc for Firefly JS API. The update of all the source files will be separate tasks.
| 1 |
1,504 |
DM-7538
|
09/06/2016 18:19:04
|
CModel is producing SingularTransformException
|
This is running on private data because I haven't yet found a public example that produces the problem. The particular data set may be specialised, but we shouldn't be so chatty in any case. {code} pprice@tiger-sumire:/scratch/gpfs/pprice $ processCcd.py DATA --rerun cmodel --id visit=42742 ccd=49 --clobber-config /home/pprice/.local/lib/python2.7/site-packages/matplotlib/font_manager.py:273: UserWarning: Matplotlib is building the font cache using fc-list. This may take a moment. warnings.warn('Matplotlib is building the font cache using fc-list. This may take a moment.') : Loading config overrride file '/tigress/HSC/LSST/stack/Linux64/obs_subaru/12.0-16-gbc41bb6+2/config/processCcd.py' : Loading config overrride file '/tigress/HSC/LSST/stack/Linux64/obs_subaru/12.0-16-gbc41bb6+2/config/hsc/processCcd.py' : input=/scratch/gpfs/pprice/DATA : calib=None : output=/scratch/gpfs/pprice/DATA/rerun/cmodel CameraMapper: Loading registry registry from /scratch/gpfs/pprice/DATA/rerun/cmodel/_parent/registry.sqlite3 CameraMapper: Loading calibRegistry registry from /scratch/gpfs/pprice/DATA/CALIB/calibRegistry.sqlite3 processCcd: Processing {'taiObs': '2015-10-15', 'pointing': 1383, 'visit': 42742, 'dateObs': '2015-10-15', 'filter': 'HSC-I', 'field': 'U105A_CEN', 'ccd': 49, 'expTime': 250.0} processCcd.isr: Performing ISR on sensor {'taiObs': '2015-10-15', 'pointing': 1383, 'visit': 42742, 'dateObs': '2015-10-15', 'filter': 'HSC-I', 'field': 'U105A_CEN', 'ccd': 49, 'expTime': 250.0} processCcd.isr.crosstalk: Applying crosstalk correction processCcd.isr: Applying brighter fatter correction processCcd.isr: Finished brighter fatter in 6 iterations processCcd.isr: Set 0 BAD pixels to 3199.49 processCcd.isr: Flattened sky level: 3200.822754 +/- 38.878743 processCcd.isr: Measuring sky levels in 8x16 grids: 3196.589865 processCcd.isr: Sky flatness in 8x16 grids - pp: 0.151048 rms: 0.022820 processCcd.isr: Setting rough magnitude zero point: 34.594850 processCcd.charImage: Processing {'taiObs': '2015-10-15', 'pointing': 1383, 'visit': 42742, 'dateObs': '2015-10-15', 'filter': 'HSC-I', 'field': 'U105A_CEN', 'ccd': 49, 'expTime': 250.0} processCcd.charImage.repair: Identified 831 cosmic rays. processCcd.charImage.detection: Detected 664 positive sources to 50 sigma. processCcd.charImage.detection: Resubtracting the background after object detection processCcd.charImage.measurement: Measuring 664 sources (664 parents, 0 children) processCcd.charImage.measurePsf: Measuring PSF processCcd.charImage.measurePsf: PSF star selector found 303 candidates processCcd.charImage.measurePsf: Reserved 75 candidates from the fitting processCcd.charImage.measurePsf: PSF determination using 205/303 stars. processCcd.charImage: iter 1; PSF sigma=1.26, dimensions=(41, 41); median background=3196.07 processCcd.charImage.repair: Identified 799 cosmic rays. processCcd.charImage.detection: Detected 743 positive sources to 50 sigma. processCcd.charImage.detection: Resubtracting the background after object detection processCcd.charImage.measurement: Measuring 743 sources (743 parents, 0 children) processCcd.charImage.measurement WARNING: Error in modelfit_CModel.measure on record 36715308886523905: File "src/geom/LinearTransform.cc", line 66, in const lsst::afw::geom::LinearTransform lsst::afw::geom::LinearTransform::invert() const Could not compute LinearTransform inverse {0} lsst::afw::geom::SingularTransformException: 'Could not compute LinearTransform inverse' processCcd.charImage.measurement WARNING: Error in modelfit_CModel.measure on record 36715308886523906: File "src/geom/LinearTransform.cc", line 66, in const lsst::afw::geom::LinearTransform lsst::afw::geom::LinearTransform::invert() const Could not compute LinearTransform inverse {0} lsst::afw::geom::SingularTransformException: 'Could not compute LinearTransform inverse' [many, many more follow...] processCcd.charImage.measureApCorr: Measuring aperture corrections for 7 flux fields /tigress/HSC/LSST/stack/Linux64/meas_algorithms/12.0-24-g3f92e4c+6/python/lsst/meas/algorithms/measureApCorr.py:226: RuntimeWarning: invalid value encountered in greater fluxes > 0.0, processCcd.charImage.measureApCorr: Aperture correction for modelfit_CModel_exp: RMS 0.073826 from 253 processCcd.charImage.measureApCorr: Aperture correction for base_PsfFlux: RMS 0.074407 from 255 processCcd.charImage.measureApCorr: Aperture correction for modelfit_CModel: RMS 0.073742 from 253 processCcd.charImage.measureApCorr: Aperture correction for modelfit_CModel_initial: RMS 0.072894 from 254 processCcd.charImage.measureApCorr: Aperture correction for ext_photometryKron_KronFlux: RMS 0.062862 from 255 processCcd.charImage.measureApCorr: Aperture correction for base_GaussianFlux: RMS 0.086553 from 255 processCcd.charImage.measureApCorr: Aperture correction for modelfit_CModel_dev: RMS 0.073533 from 253 processCcd.charImage.applyApCorr: Applying aperture corrections to 7 flux fields processCcd.charImage.applyApCorr: Use naive flux sigma computation processCcd.calibrate: Processing {'taiObs': '2015-10-15', 'pointing': 1383, 'visit': 42742, 'dateObs': '2015-10-15', 'filter': 'HSC-I', 'field': 'U105A_CEN', 'ccd': 49, 'expTime': 250.0} processCcd.calibrate.detection: Detected 4386 positive sources to 5 sigma. processCcd.calibrate.detection: Resubtracting the background after object detection processCcd.calibrate.deblend: Deblending 4386 sources processCcd.calibrate.deblend: Deblended: of 4386 sources, 1006 were deblended, creating 3754 children, total 8140 sources processCcd.calibrate.measurement: Measuring 8140 sources (4386 parents, 3754 children) processCcd.calibrate.applyApCorr: Applying aperture corrections to 2 flux fields processCcd.calibrate.applyApCorr: Use naive flux sigma computation [...] {code}
| 1 |
1,505 |
DM-7539
|
09/07/2016 09:30:09
|
"Docstrings SHOULD NOT be preceded or followed by a blank line" needs update
|
The nicely updated Python style guide version 6.0 has a small error in "Docstrings SHOULD NOT be preceded or followed by a blank line". It's a nice simple rule, and one I followed for years, but autopep8 adds a blank line after the doc string for a class, so apparently PEP8 has slightly different requirements. I hope fixing this won't require an RFC.
| 0.5 |
1,506 |
DM-7542
|
09/07/2016 12:59:16
|
Renew TLS certificate for community.lsst.org (2016)
|
Renew *.lsst.org certificate and install on community.lsst.org. Procedure at https://meta.discourse.org/t/allowing-ssl-https-for-your-discourse-docker-setup/13847
| 0.5 |
1,507 |
DM-7543
|
09/07/2016 14:50:37
|
Change background and text color in image toolbar and label (left)
|
compared to before migration, a blue background and transparent icon toolbar appears on top of the image viewer. Blue background and zoom number is not readable enough. The color is not consistent with the rest of the application neither. Change blue to same transparency as the toolbar icon (right hand) or change to black on white if doesn't improve.
| 1 |
1,508 |
DM-7546
|
09/07/2016 15:10:53
|
create a shared stack in GPFS for Verification Cluster
|
Analogous to the work of DM-6968 for NFS, we request a shared stack within the GPFS file system for lsst-dev7 and the Verification Cluster (48 nodes, 1152 cores). The familiar NFS home directories are available on the front end system lsst-dev7, but are not mounted on the compute nodes of the Verification Cluster. As such, the NFS stack of DM-6968 is not usable for computation on the Verification Cluster. Initial testing shows computation against a stack in GPFS can execute at least 300+ simultaneous tasks/pipelines without significant slowdown, suggesting a wide range of work can be performed with a stack in the shared GPFS space on the >~ 1000 cores of the Verification Cluster. The suggested location for the GPFS stack is under /software/lsstsw , reachable on lsst-dev7 (i.e., the build of the stack would be done on lsst-dev7, running CentOS 7.2.1511 ). The /software space is considered a location where various reference software stacks might be made available to the team. In addition to /software/lsstsw , the 'lsstsw' user does have a 'GPFS home' directory /gpfs/fs0/home/lsstsw that could also be used, though the organization offered by /software appears preferable. (The 'lsstsw' user would continue to have a home directory in NFS for the time being, with an eventual transition to that on GPFS. )
| 1 |
1,509 |
DM-7547
|
09/07/2016 15:20:01
|
Remove the extra column on far right-hand side of a table when no description is available
|
An empty column seems to be visible on the right-hand side of a table when no description is available in option panel of the XY-plot column setting, table option and fits header table.
| 2 |
1,510 |
DM-7548
|
09/07/2016 16:11:20
|
constructBias.py crashes with errors about log
|
[~aritter] got this error when running {{constructBias.py}}. It seems {{pipe_drivers}} needs changes following the logging framework transition in {{pipe_base}}. {code:java} bias WARN: Unable to process DataId(initialdata={'category': 'A', 'taiObs': '2015-12-04', 'visit': 6301, 'dateObs': '2015-12-04', 'site': 'S', 'filter': 'r', 'field': 'BIAS', 'spectrograph': 2, 'ccd': 5, 'arm': 'r'}, tag=set([])): Wrong number or type of arguments for overloaded function 'Log_log'. Possible C/C++ prototypes are: lsst::log::Log::log(lsst::log::Log,log4cxx::LevelPtr,log4cxx::spi::LocationInfo const &,char const *,...) lsst::log::Log::log(log4cxx::LevelPtr,log4cxx::spi::LocationInfo const &,char const *,...) NotImplementedError on tiger1:27163 in map: Wrong number or type of arguments for overloaded function 'Log_log'. Possible C/C++ prototypes are: lsst::log::Log::log(lsst::log::Log,log4cxx::LevelPtr,log4cxx::spi::LocationInfo const &,char const *,...) lsst::log::Log::log(log4cxx::LevelPtr,log4cxx::spi::LocationInfo const &,char const *,...) Traceback (most recent call last): File "/tigress/HSC/LSST/stack/Linux64/ctrl_pool/12.0+45/python/lsst/ctrl/pool/pool.py", line 89, in wrapper return func(*args, **kwargs) File "/tigress/HSC/LSST/stack/Linux64/ctrl_pool/12.0+45/python/lsst/ctrl/pool/pool.py", line 207, in wrapper return func(*args, **kwargs) File "/tigress/HSC/LSST/stack/Linux64/ctrl_pool/12.0+45/python/lsst/ctrl/pool/pool.py", line 524, in map return self._processQueue(context, func, zip(range(num), dataList), *args, **kwargs) File "/tigress/HSC/LSST/stack/Linux64/ctrl_pool/12.0+45/python/lsst/ctrl/pool/pool.py", line 421, in _processQueue return [func(self._getCache(context, i), data, *args, **kwargs) for i, data in queue] File "/tigress/HSC/LSST/stack/Linux64/pipe_drivers/12.0-3-g33a9219+35/python/lsst/pipe/drivers/constructCalibs.py", line 459, in process exposure = self.processSingle(sensorRef) File "/tigress/HSC/LSST/stack/Linux64/pipe_drivers/12.0-3-g33a9219+35/python/lsst/pipe/drivers/constructCalibs.py", line 477, in processSingle return self.isr.runDataRef(dataRef).exposure File "/tigress/HSC/LSST/stack/Linux64/obs_subaru/12.0-18-gb01a726+1/python/lsst/obs/subaru/isr.py", line 268, in runDataRef ccdExposure = self.assembleCcd.assembleCcd(ccdExposure) File "/tigress/HSC/LSST/stack/Linux64/ip_isr/12.0-7-ga6ffce9+2/python/lsst/ip/isr/assembleCcdTask.py", line 229, in assembleCcd self.postprocessExposure(outExposure=outExposure, inExposure=getNextExposure(ccd[0])) File "/tigress/HSC/LSST/stack/Linux64/ip_isr/12.0-7-ga6ffce9+2/python/lsst/ip/isr/assembleCcdTask.py", line 243, in postprocessExposure self.setWcs(outExposure = outExposure, inExposure = inExposure) File "/tigress/HSC/LSST/stack/Linux64/ip_isr/12.0-7-ga6ffce9+2/python/lsst/ip/isr/assembleCcdTask.py", line 280, in setWcs self.log.log(self.log.WARN, "No WCS found in input exposure") File "/tigress/HSC/LSST/stack/Linux64/log/12.0-5-g1df3bbf/python/lsst/log/logLib.py", line 249, in log return _logLib.Log_log(self, *args) NotImplementedError: Wrong number or type of arguments for overloaded function 'Log_log'. Possible C/C++ prototypes are: lsst::log::Log::log(lsst::log::Log,log4cxx::LevelPtr,log4cxx::spi::LocationInfo const &,char const *,...) lsst::log::Log::log(log4cxx::LevelPtr,log4cxx::spi::LocationInfo const &,char const *,...) application called MPI_Abort(MPI_COMM_WORLD, 1) - process 0 {code}
| 5 |
1,511 |
DM-7549
|
09/07/2016 16:51:54
|
afw:testGaussianProcess has an intermittent test failure
|
Sometimes the {{afw}} test {{testGausisianProcess.py}} can fail: {code} ... ====================================================================== FAIL: testTooManyNeighbors (__main__.GaussianProcessTestCase) ---------------------------------------------------------------------- Traceback (most recent call last): File "./tests/testGaussianProcess.py", line 62, in testTooManyNeighbors gg.selfInterpolate(sigma, -1, nData-1) AssertionError: Exception not raised ---------------------------------------------------------------------- Ran 11 tests in 1.992s FAILED (failures=1) {code} This is a very rare failure. It ran 102 times on my laptop before it stopped with this failure. So far we have only seen reports of this failure on Python 3.
| 3 |
1,512 |
DM-7553
|
09/07/2016 18:06:32
|
Merge XRootD plugin link changes from upstream and adapt Qserv
|
Changes to plugin linking have been made upstream in XRootD (plugins now to link against import library). This ticket is to update the lsst-dev XRootD branch from upstream and make the necessary parallel change to the Qserv build scripts.
| 1 |
1,513 |
DM-7555
|
09/07/2016 22:05:06
|
Ad-hoc developer requests Part II
|
This is a bucket epic for ad-hoc developer requests that cannot be postponed till the next planning cycle. In the event that it is underutilised for this purpose, it will be assigned to technical debt DM-5850
| 8 |
1,514 |
DM-7558
|
09/08/2016 07:16:56
|
Create dependency map for Calibration Products Production
|
Identify the relationships that the Calibration Products Pipeline have with other parts of LDM-151 (chiefly algorithmic components) and with external deliverables, and record these appropriately.
| 3 |
1,515 |
DM-7560
|
09/08/2016 07:21:00
|
Audit Calibration Products Pipeline section of LDM-151
|
Detailed read-through of the CPP section of LDM-151. Identify areas of uncertainty, resolve them with stakeholders (ie, [~mfisherlevine], at least initially). Make copious notes.
| 5 |
1,516 |
DM-7561
|
09/08/2016 07:21:39
|
Audit Data Release Production section of LDM-151
|
Detailed read-through of the CPP section of LDM-151. Identify areas of uncertainty, resolve them with stakeholders (ie, [~jbosch], at least initially). Make copious notes.
| 5 |
1,517 |
DM-7562
|
09/08/2016 07:23:24
|
Take part in 2016-09-08 planning meeting
|
Participate in the meeting called by [~mjuric]: {quote} Just confirming we’ll meet for an initial planning meeting tomorrow at 10am PT. Roughly, the goal is to make sure we’re on the same page on the principles for the deployment plan you guys have started developing, and to begin putting together a Gantt chart and milestones for what we believe thePipelines groups will deliver (and need) based on what we know is in LDM-151. {quote}
| 1 |
1,518 |
DM-7563
|
09/08/2016 07:28:19
|
Produce straw-man plan for DRP
|
Using the - Understanding developed in DM-7561; - Dependency map developed in DM-7557; - Responsibility assignments developed in DM-7031; - Rough resource requirements developed in DM-7032, DM-7034; - Tooling decided in DM-7559; develop an outline of a plan for Data Release Production.
| 8 |
1,519 |
DM-7567
|
09/08/2016 12:14:23
|
Butler Repository fails to import mapper module
|
when a mapper is specified to the butler as a dot-delimited string (i.e. the module is part of the mapper specification), the importer fails. For example if you use {code} RepositoryArgs(mapper='lsst.daf.persistence.CameraMapper')}} You get the output {{Traceback (most recent call last): File "tests/testImportMapper.py", line 52, in test butler = dafPersist.Butler(outputs=repositoryArgs) File "/Users/n8pease/2/lsstsw/build/daf_persistence/python/lsst/daf/persistence/butler.py", line 285, in __init__ self._addRepo(args, inout='out', defaultMapper=defaultMapper, butlerIOParents=butlerIOParents) File "/Users/n8pease/2/lsstsw/build/daf_persistence/python/lsst/daf/persistence/butler.py", line 382, in _addRepo repo = Repository(cfg) File "/Users/n8pease/2/lsstsw/build/daf_persistence/python/lsst/daf/persistence/repository.py", line 88, in __init__ self._initMapper(repositoryCfg) File "/Users/n8pease/2/lsstsw/build/daf_persistence/python/lsst/daf/persistence/repository.py", line 108, in _initMapper module = __import__(module) ImportError: No module named CameraMapper {code} The module that contains the CameraMapper ({{lsst.daf.persistence}}) should be imported, not the module+class name.
| 1 |
1,520 |
DM-7576
|
09/08/2016 16:00:24
|
Set default detection threshold to 5.0-sigma if decorrelation is turned on
|
The current logic to set detection.thresholdValue to 5.0 if doDecorrelation == True is set in setDefaults(), and so never runs. This block needs to be moved elsewhere (doValidate, perhaps?) so that it runs correctly.
| 2 |
1,521 |
DM-7578
|
09/08/2016 16:59:02
|
Create obs_base and make obs_test work with it
|
To support broad testing of obs packages, with minimal configuration, we will add an {{obs_base}} package that all obs packages will depend on. It will contain a test suite for them to derive from, plus frameworks for other modules (e.g. {{makeSomeCameraRepository.py}}). {{obs_test}} will be the demo for how this new module works. Implementation details will be worked out along the way.
| 8 |
1,522 |
DM-7584
|
09/09/2016 13:49:22
|
Fix missing code lines in doxygen page on using masked image locators
|
The doxygen page https://lsst-web.ncsa.illinois.edu/doxygen/xlink_master_2015_11_10_02.53.27/masked_image_locators.html describes how to use image locators to move around images. Unfortunately, the page is missing the actual code lines that are being discussed. Fix the broken/missing code lines on this page.
| 0.5 |
1,523 |
DM-7586
|
09/10/2016 08:31:20
|
add lsst_py3 job to jenkins
|
The new {{lsst_py3}} metapackage enumerates eups products known to be compatible with python3. A new dedicated jenkins job has been requested to catch regressions.
| 0.5 |
1,524 |
DM-7587
|
09/12/2016 09:44:36
|
Add timesys argument to DateTime constructor to toString (implement RFC-219)
|
Implement RFC-219 as follows: - DateTime(string, timescale) with "Z" required for UTC and forbidden for TAI. Ideally forbid "23:59:60" leap seconds for TAI as well. - DateTime.toString(timescale) with "Z" produced for UTC and not for TAI. Require the timescale argument, unless it proves to be a major headache by affecting too much code, in which case default to UTC for backwards compatibility. Additional tests that verify that "23:59:60" strings are not produced by toString(TAI) at actual leap seconds.
| 3 |
1,525 |
DM-7588
|
09/12/2016 09:46:13
|
Update MPICH
|
Version 3.2 of MPICH fails multiple tests on OS X and does not integrate well with mpi4py. Presently the newer 3.3a development version performs better and when the stable version 3.3 is released we should upgrade the stack.
| 2 |
1,526 |
DM-7590
|
09/12/2016 11:35:52
|
SUIT vision document
|
SUIT vision document work, review, revision, and submission for approval by TCT.
| 2 |
1,527 |
DM-7593
|
09/12/2016 15:43:28
|
Make use of the phase folded code
|
Now that DM-7165 is done, use the code in the LC handler to complete the processor added [DM-7162]
| 1 |
1,528 |
DM-7594
|
09/12/2016 17:46:23
|
Extra phase column is displayed with too few precision
|
DM-7165 allow to add an extra column ('phase') to the raw LC table, which result in the phase folded table. This is done using DataType object. When the result is shown in table view, the display format is '0.0' which is not enough. The phase column should be displayed as double precision with at least 8 significant digits Also, add attribute to the extra phase column so a comment or some description appears in the ipac table header when is saved by the user if possible.
| 2 |
1,529 |
DM-7595
|
09/12/2016 17:59:21
|
Extra column doesn't appear in the header description when saving ipac table
|
Add attribute to the extra phase column so a comment or some description appears in the ipac table header when is saved by the user if possible NOTE: this ticket is combined with DM-7594.
| 0 |
1,530 |
DM-7604
|
09/13/2016 13:07:07
|
file() in lsst.cat should be open()
|
The lsst.cat package has a reference to file(), which is not supported in Python 3. Updating this to use open().
| 1 |
1,531 |
DM-7608
|
09/13/2016 15:33:04
|
testSelectSdssImages.py broken: "noConnectionStr" not defined
|
A recent change to testSelectSdssImages.py broke the test for those who could connect to the database. The symptom is: {code} NameError: name 'noConnectionStr' is not defined {code} and is self descriptive. I have a fix ready to go.
| 0 |
1,532 |
DM-7610
|
09/13/2016 15:49:54
|
Implement Target Panel resolve option (ned then simbad or simbad then ned)
|
We have not implement the target panel resolve option. When is there in the search panels now are dummy ui components.
| 1 |
1,533 |
DM-7614
|
09/14/2016 11:13:28
|
Support pytest in coadd_chisquared tests
|
Modernize the test file to be compatible with pytest.
| 0 |
1,534 |
DM-7615
|
09/14/2016 11:15:54
|
Update tests in shapelet to support pytest
|
The tests in {{shapelet}} need to be modernized to support pytest and to drop {{suite}}.
| 1 |
1,535 |
DM-7622
|
09/14/2016 14:55:48
|
DateTime rejects an acceptable date
|
The following fails for reasons I do not understand: {code} from lsst.daf.base import DateTime # for most versions of daf_base DateTime("1969-12-31T23:59:59Z") # if using the latest master of daf_base DateTime("1969-12-31T23:59:59Z", DateTime.UTC) {code} The error is: {code} File "src/DateTime.cc", line 391, in lsst::daf::base::DateTime::DateTime(int, int, int, int, int, int, lsst::daf::base::DateTime::Timescale) Unconvertible date: 1969-12-31T23:59:59 {0} lsst::pex::exceptions::DomainError: 'Unconvertible date: 1969-12-31T23:59:59' {code} and comes from this code: {code} dafBase::DateTime::DateTime(int year, int month, int day, int hr, int min, int sec, Timescale scale) { struct tm tm; tm.tm_year = year - 1900; tm.tm_mon = month - 1; tm.tm_mday = day; tm.tm_hour = hr; tm.tm_min = min; tm.tm_sec = sec; tm.tm_wday = 0; tm.tm_yday = 0; tm.tm_isdst = 0; tm.tm_gmtoff = 0; time_t secs = timegm(&tm); // long long nsecs will blow out beyond sep 21, 1677 0:00:00, and apr 12 2262 00:00:00 // (refering to the values of EPOCH_IN_MJD +/- MAX_DAYS ... exceeds 64 bits.) // However, a tm struct is only 32 bits, and saturates at: // low end - Dec 13 1901, 20:45:52 // hi end - Jan 19 2038, 03:14:07 if (secs == -1) { throw LSST_EXCEPT( lsst::pex::exceptions::DomainError, (boost::format("Unconvertible date: %04d-%02d-%02dT%02d:%02d:%02d") % year % month % day % hr % min % sec).str()); } {code}
| 2 |
1,536 |
DM-7626
|
09/14/2016 16:31:55
|
Modernize dax_webservcommon tests to work with pytest
|
Support pytest.
| 0.5 |
1,537 |
DM-7629
|
09/14/2016 16:35:11
|
Modernize dax_metaserv to support pytest
|
Support pytest.
| 1 |
1,538 |
DM-7630
|
09/14/2016 18:46:19
|
Dispaly "null" when a value "null" is in the data
|
Allow null values to display as "null", currently a value of null is left blank.
| 2 |
1,539 |
DM-7651
|
09/15/2016 12:14:18
|
Clarify in dm_dev_guide that SSH keys must be in one-line format
|
The [instructions for using public-key authentication with lsst-dev|https://developer.lsst.io/services/lsst-dev.html#lsst-dev-ssh-keys] assume the user has OpenSSH. While this does not prevent users from translating the instructions to their own SSH software, it does cause a confusing bug if the user isn't aware that OpenSSH (or, specifically, the {{~/.ssh/authorized_keys}} file) only accepts one-line keys and not the more common multi-line PEM format. I propose that a note be added to the end of "1. Generate a key pair" warning non-OpenSSH users to make sure their public key is in the one-line format.
| 1 |
1,540 |
DM-7652
|
09/15/2016 13:00:54
|
Replace usage of execfile in astrometryNetDataConfig.py
|
{{astrometryNetDataConfig.py}} gained a {{from past.builtins import execfile}} during the python3 conversion. We should replace this with a more modern syntax.
| 1 |
1,541 |
DM-7655
|
09/16/2016 11:28:34
|
The region with semicolon inside text property is not displayed
|
Region description is not parsed well in case there is character ';' contained in 'text', 'tag' (the property which has text string value).
| 3 |
1,542 |
DM-7662
|
09/17/2016 13:09:34
|
Prepare and deliver a documentation/technical writing talk at the invitation of NCSA.
|
The talk is archived at https://zenodo.org/record/153867#.V92VODvsXPg and was given on September 12, 2016.
| 1 |
1,543 |
DM-7665
|
09/18/2016 15:46:46
|
plan to choose the context background image for LSST data
|
As we search and display the LSST sources/objects, the SUIT should be able to choose a sensible background image to overlay the sources/objects on. We need to come up with a strategy and the potential images to choose from at different stages: * PDAC v1 (end of F16): Current method that Firefly employs to choose. Depending on size needed, it will pick one from 2MASS, WISE, SDSS, IRAS. * PDAC v2 (end of S17) * Ready ComCAM
| 2 |
1,544 |
DM-7668
|
09/19/2016 08:08:08
|
Remove shapelet code from meas_algorithms
|
Implement RFC-223.
| 2 |
1,545 |
DM-7669
|
09/19/2016 08:09:16
|
Remove GPU warping, convolution, and support code
|
Implement RFC-224.
| 2 |
1,546 |
DM-7674
|
09/19/2016 11:35:39
|
New workflow for onboarding DM members into community.lsst.org groups
|
Previously we made every T/CAM a community.lsst.org admin so that they could add their team members to the LSST and LSSTDM groups to access private community categories. Discourse now has the concept of Group owners, who can add/remove members from individual groups. I’d like to limit the number of people with Admin credentials since it poses a security risk; especially considering our responsibility to support private Science Collaboration categories. This ticket will update community configurationg and Developer Guide documentation to implement this.
| 0.5 |
1,547 |
DM-7676
|
09/19/2016 14:22:10
|
lsof used by setup.csh not always in /usr/sbin
|
The {{setup.csh}} script uses {{/usr/sbin/lsof}} to detect the location of the script if indirectly sourced. On a stock Ubuntu 14.04 system (which is not an officially supported platform but on which the stack works otherwise), it appears that this utility is installed as {{/usr/bin/lsof}} instead. Making this usage slightly more generic should help improve portability.
| 1 |
1,548 |
DM-7677
|
09/19/2016 14:33:24
|
Create RFC documents for changes to Mapper.paf files
|
In DM-7049, an set of datasets were moved from the HSC mapper to daf_butlerUtils. These are in exposures.yaml and datasets.yaml, and are now available to all cameraMapper subclasses (provided that there is an exposures or datasets section in their own Mapper.paf file.) An RFC will be published for each Mapper describing possible additional changes: 1. Additional cleanup is required in each of the obs_*/policy/*Mapper.paf files to fully implement this move. Datasets which are not consistent with the new "shared" datasets need to be altered before they can be removed, but carefully, so as not to disturb the code which utilizes the mapper. 2. Identify datasets in each mappers which have the same function as a shared dataset, but a different name. If possible, these should be renamed and made consistent with the shared dataset. 3. Attempt discover datasets which are no longer in use and could be deleted.
| 3 |
1,549 |
DM-7679
|
09/19/2016 16:56:57
|
XrdSsiClient library compilation error with gcc -v 6.2 in Ubuntu 16.10
|
[~speckins] tried building qserv under Ubuntu 16.10, which ships with gcc -v 6.2 . I was able to reproduce the error with cmake on the xrdssi branch as follows: {code} Scanning dependencies of target XrdSsiLib [ 77%] Building CXX object src/CMakeFiles/XrdSsiLib.dir/XrdSsi/XrdSsiClient.cc.o In file included from /home/qserv/src/xrootd/src/XrdSsi/XrdSsiClient.cc:42:0: /home/qserv/src/xrootd/src/XrdSsi/XrdSsiClient.cc: In member function 'virtual XrdSsiService* XrdSsiClientProvider::GetService(XrdSsiErrInfo&, const char*, int)': /home/qserv/src/xrootd/src/./XrdSsi/XrdSsiAtomics.hh:45:34: error: request for member 'load' in 'XrdSsi::initDone', which is of non-class type 'bool' #define Atomic_GET(x) x.load(std::memory_order_relaxed) ^ /home/qserv/src/xrootd/src/XrdSsi/XrdSsiClient.cc:122:8: note: in expansion of macro 'Atomic_GET' if (!Atomic_GET(initDone)) ^~~~~~~~~~ src/CMakeFiles/XrdSsiLib.dir/build.make:62: recipe for target 'src/CMakeFiles/XrdSsiLib.dir/XrdSsi/XrdSsiClient.cc.o' failed make[2]: *** [src/CMakeFiles/XrdSsiLib.dir/XrdSsi/XrdSsiClient.cc.o] Error 1 CMakeFiles/Makefile2:1224: recipe for target 'src/CMakeFiles/XrdSsiLib.dir/all' failed make[1]: *** [src/CMakeFiles/XrdSsiLib.dir/all] Error 2 Makefile:127: recipe for target 'all' failed make: *** [all] Error 2 {code}
| 1 |
1,550 |
DM-7681
|
09/19/2016 17:42:52
|
Begin the documentaiton process of visualization
|
Begin the visualization documentation process. This is the first step of probably much more documentation. However, some needs to be put into jsdocs soon so this ticket should be that documentation.
| 2 |
1,551 |
DM-7687
|
09/20/2016 10:41:49
|
Split HSC comparison/QA script into separate package
|
Currently, it lives as all the scripts starting with {{hsc}} in branch {{u/lauren/working}} of {{pipe_tasks:bin.src}}. These should all move to a new package in the lsst-dm organization.
| 1 |
1,552 |
DM-7691
|
09/20/2016 13:48:14
|
Shared stack in NFS /lsst4 shows error at initialization
|
The NFS stack created in DM-6968 today shows an error upon initialization : {code} % cd /lsst4/lsstsw/stack/ % source loadLSST.bash setup: [Errno 13] Permission denied: '/nfs/lsst4/lsstsw/stack/.lockDir/shared-daues.801175' You are attempting to run "setup" which requires administrative privileges, but more information is needed in order to do so. Authenticating as "root" Password: {code} This may be occurring due to the existence of a lock and .lockDir : {code} % ls -ld /nfs/lsst4/lsstsw/stack/.lockDir/ drwxr-xr-x 2 lsstsw ac 4096 Sep 19 04:49 /nfs/lsst4/lsstsw/stack/.lockDir/ % ls -ld /nfs/lsst4/lsstsw/stack/.lockDir/* -rwxr-xr-x 1 lsstsw ac 0 Sep 14 00:36 /nfs/lsst4/lsstsw/stack/.lockDir/shared-lsstsw.2531683 {code} Could this be investigated ? Greg
| 0.5 |
1,553 |
DM-7693
|
09/21/2016 10:20:22
|
fix premature merge of previous ctrl_orca ticket
|
When I went to look for the pull for ctrl_orca on Monday for ticket DM-7183, I didn't see one; I made changes to the "is True", "is False", and list(keys()) issues, and then didn't look again on Tuesday when I saw the "Review complete", so I thought it had been done, which is was not. This is to look at those issue and fix them.
| 2 |
1,554 |
DM-7694
|
09/21/2016 10:24:04
|
Restore a couple of datasets from DM-7049
|
DM-7049 removed at least one dataset which might be in use. Restore any doubtful datasets to the Mappers and move them to the DM-7677 RFC.
| 1 |
1,555 |
DM-7700
|
09/21/2016 17:10:25
|
Atlas table filtering doesn't work properly
|
Atlas result page is using Firefly table component but couple of problems have been detected: - Filtering the table doesn't work properly. Step to reproduce: Go to http://irsawebdev1.ipac.caltech.edu/applications/Atlas, do a search on SEIP. Then try to filter 'Instruments' column on 'mips'. The result is wrong. I see 'IRAC' rows.
| 2 |
1,556 |
DM-7701
|
09/21/2016 17:18:25
|
conda-lsst ndarray test failure
|
The conda-lsst build log for the test failure can be found here: https://gist.github.com/jmatt/dcb6ce8312aac1ff81cbb923703d8430 {code} Running tests... Test project /Users/square/dev/conda-lsst/miniconda/conda-bld/work/build Start 1: test_ndarray 1/5 Test #1: test_ndarray ..................... Passed 0.01 sec Start 2: test_views 2/5 Test #2: test_views ....................... Passed 0.01 sec Start 3: test_ndarray-fft 3/5 Test #3: test_ndarray-fft .................***Exception: Other 0.00 sec Start 4: test_ndarray_eigen 4/5 Test #4: test_ndarray_eigen ............... Passed 0.01 sec Start 5: swig_test 5/5 Test #5: swig_test ........................ Passed 0.11 sec 80% tests passed, 1 tests failed out of 5 Total Test time (real) = 0.14 sec The following tests FAILED: 3 - test_ndarray-fft (OTHER_FAULT) Errors while running CTest make: *** [test] Error 8 {code}
| 1 |
1,557 |
DM-7702
|
09/21/2016 18:14:13
|
stretch dropdown feature is currently broken
|
The stretch feature is broken. The log shown are related to getRangeValues error: Uncaught TypeError: (0 , _PlotViewUtil.primePlot)(...).plotState.getRangeValues is not a function Please investigate and fix. Thanks.
| 0.5 |
1,558 |
DM-7706
|
09/22/2016 10:04:39
|
Fix issues related to tomcat8 and ipv6. Also add firefly.war into firefly release page.
|
- Fix duplicate nom.tam.fits classes during build - Add preferIPv4Stack to tomcat env. - Add firefly.war to Firefly Standalone release page.
| 3 |
1,559 |
DM-7710
|
09/22/2016 11:34:30
|
afw.display.makeMosaic doesn't understand self.images
|
The routine makeMosaic doesn't work if you pass in a list of images (as opposed to appending images to self)
| 1 |
1,560 |
DM-7716
|
09/22/2016 16:59:10
|
Fix dataset lookup in multibandDriver.py
|
{{MultibandDriver}} builds a patch reference list by checking for the existence of {{self.config.coaddName + "Coadd"}}. However, when coadd assembly is performed by running {{coaddDriver}}, this coadd is not persisted in favor of only persisting the updated calexp version. Thus, currently {{MultibandDriver}} ends up with and empty patch list and exits quietly. The existence check should be on the {{self.config.coaddName + "Coadd_calexp"}}.
| 0.5 |
1,561 |
DM-7725
|
09/23/2016 13:35:35
|
Fix missing lsst.log update and build dependencies
|
There was one missed instance of updating to the new {{lsst.log}} system and the remaining {{pex_logging}} dependencies are not reflected in the {{ups/}} table and cfg files (but are being pulled in by {{meas_algorithms}}).
| 0.5 |
1,562 |
DM-7726
|
09/23/2016 15:05:45
|
Fix MySQL Incorrect date time value warning in ctrl_stats
|
in Mysql 5.7, the warning /home/srp/lsstsw27/lsstsw/stack/Linux64/cat/12.1.rc1-3-g00b8a9c+1/python/lsst/cat/MySQLBase.py:158: Warning: Incorrect datetime value: '0000-00-00 00:00:00' for column 'executionStartTime' at row 1 is emitted. This is because of a change in MySQL 5.7 about how '0000-00-00 00:00:00" dates are handled.
| 1 |
1,563 |
DM-7738
|
09/26/2016 11:51:28
|
Remove outdated instructions in obs_decam README
|
{{obs_decam}} README has outdated information, leading to confusion like [this|https://community.lsst.org/t/error-of-using-obs-decam/1181/1]. Remove the outdated instructions to avoid confusion. For example, {{processCcdDecam.py}} is no longer used since DM-4692 (https://community.lsst.org/t/backward-incompatible-changes-to-processccdtask-and-subtasks/581)
| 0.5 |
1,564 |
DM-7739
|
09/26/2016 12:32:17
|
Docstring improvements in Firefly Python API
|
The docstrings for FireflyClient are very helpful overall. That said, I found myself tripping over a few items that could be clarified for users. In add_mask: * It would be helpful to mirror the order of the parameters with the function signature, i.e. in the Parameters section, please list bit_number first and then image_number. * Please indicate that image_number is zero-based, e.g. for a file of image, mask, variance, the user will want to specify image_number=1. In show_fits: * Under additional_params, it would be helpful to note that the user can supply MultiImageIdx to display a particular image extension from the file, and that this is a zero-based index. (The link to parameters does not list MultiImageIdx btw.)
| 1 |
1,565 |
DM-7741
|
09/26/2016 13:51:27
|
Missed incompatible logging changes in Python + migrate meas_astrom
|
Since DM-6999, Python codes using Task/CmdLineTask are converted to use {{lsst.log}} instead of {{lsst.pex.logging}}. Codes like {{self.log.log(self.log.WARN, "messages")}} should be changed to {{self.log.warn("messages")}} because that API is no longer supported. Many places need such changes but were missed. This ticket is to go through the Python codes of pipe_\*, ip_\*, meas_\* and obs_\* and correct them.
| 1 |
1,566 |
DM-7745
|
09/26/2016 17:34:26
|
enum constants in daf_base.DateTime can cause confusion
|
Whilst looking at DM-7742 I started to wonder why the {{DateTime}} constructor did not complain when it was given an MJD time system instead of a UTC time scale. It seems we have two issues with {{DateTime}} that can lead to subtle bugs not being caught: # Both the TimeScale and DateSystem enums share values in Python land. This means that in Python you can pass in an MJD but C++ will treat it as UTC. We should ensure that both these enums convert to different sets of integers in Python so that we can trap system/scale confusion. # The DateTime constructor does not check all cases. It assumes that if the scale is not TT or TAI then the user probably meant UTC. The code in DateTime should never use an {{else}} to assume UTC but should always check and trigger and exception if the value is not recognized.
| 1 |
1,567 |
DM-7754
|
09/27/2016 08:54:46
|
Can't use simple afwImage primitives without explicitly initialising log4cxx
|
This simple script: {code} import lsst.afw.image as afwImage exp = afwImage.ExposureF(1, 1) {code} generates the error: {quote} log4cxx: No appender could be found for logger (afw.image.Mask). log4cxx: Please initialize the log4cxx system properly. {quote} I'd expect to be able to use LSST primitives without explicitly setting up the logging.
| 1 |
1,568 |
DM-7756
|
09/27/2016 09:30:43
|
Port pipe_drivers to Python 3
|
{{pipe_drivers}} needs to be converted to python 3.
| 0.5 |
1,569 |
DM-7760
|
09/27/2016 11:38:16
|
WCS match does not work right when the images are not initially locked
|
WCS match is not working immediately when the images start out as not locked. It requires a second uncheck and check to make it work. Bug was found with following description below. This ticket fixes the WCS matching part of the problem. The rotation not centering is another problem that I can't quite repeat but is probably not related to WCS-match. We have other work for the rotation (DM-7336) that might help. ----------------------------------------------------------- 1. Go to the Spitzer Enhanced Imaging Products: http://irsawebdev1.ipac.caltech.edu/data/SPITZER/Enhanced/SEIP/ 2. Try the last example, CGCG 036-024, with size = 0.1 and images must cover coordinate checked. 3. In the results, I cannot seem to sort by distance. However, I can now filter by wavelength. Filter wavelength = 24 and type of data = science. Only 2 results should remain. Send both to the IRSA Viewer. 4. On the second image, zoom in 6x and center target in display. Click WCS Match. Nothing happens. (I waited 6 minutes.) 5. Turn WCS Match off and on again. It works. 6. Turn WCS Match off. Rotate the second image using 30 degrees. The target moves off the display instead of just rotating. 7. Recenter the target. Works. 8. Click WCS Match on again. The first image target goes off the screen instead of just rotating. 9. Click on the first image, and recenter target. Works.
| 0.5 |
1,570 |
DM-7762
|
09/27/2016 12:02:32
|
Understand PDAC data base enough to determine the queries we need to do.
|
This story involves understanding the data we need to access for the PDAC UI. * Understand the two applications we want to make for the PDAC: general catalog search and light curve viewer * Understand the data base searches we need to do. * Analyze the tables and data we need for the two applications. * Come up with example select statements for each search. * Try to make the the related DAX URL for each search. (We might need to make a second ticket to really work this last issue) * Get some example fits files and put the into firefly_test_data The scope grew and more work in documenting the difference of qserv_* functions and scisql_* functions.
| 20 |
1,571 |
DM-7765
|
09/27/2016 12:53:07
|
Rendering region text on PNG
|
The region text defined with region object (not text region) is not shown on PNG.
| 2 |
1,572 |
DM-7769
|
09/27/2016 15:25:50
|
duplicate imports in CharacterizeImageTask
|
A few duplicate imports snuck into CharacterizeImageTask in a recent change. It's a one-liner to fix. However, pep8 also picked up the fact that lines 565-569 are indented too far. Might as well fix that as well and run flake8 on all python code.
| 1 |
1,573 |
DM-7770
|
09/28/2016 09:44:32
|
RingsSkyMap.findAllTracts fails with wcslib error
|
Johnny Greco (Princeton) points out an exception when using {{RingsSkyMap.findTractPatchList}}: {code} RuntimeError Traceback (most recent call last) <ipython-input-95-53f3ab207e06> in <module>() ----> 1 skymap.findTractPatchList(coordlist) /Users/protostar/anaconda/envs/lsst/opt/lsst/skymap/python/lsst/skymap/ringsSkyMap.pyc in findTractPatchList(self, coordList) 211 retList = [] 212 for coord in coordList: --> 213 for tractInfo in self.findAllTracts(coord): 214 patchList = tractInfo.findPatchList(coordList) 215 if patchList and not (tractInfo, patchList) in retList: /Users/protostar/anaconda/envs/lsst/opt/lsst/skymap/python/lsst/skymap/ringsSkyMap.pyc in findAllTracts(self, coord) 194 for entry in [0,len(self)-1]: 195 tract = self[entry] --> 196 if tract.getBBox().contains(afwGeom.Point2I(tract.getWcs().skyToPixel(coord.toIcrs()))): 197 tractList.append(tract) 198 /Users/protostar/anaconda/envs/lsst/opt/lsst/afw/python/lsst/afw/image/imageLib.pyc in skyToPixel(self, *args) 8691 skyToPixel(Wcs self, Coord coord) -> Point2D 8692 """ -> 8693 return _imageLib.Wcs_skyToPixel(self, *args) 8694 8695 def skyToIntermediateWorldCoord(self, *args): RuntimeError: File "src/image/TanWcs.cc", line 313, in virtual geom::Point2D lsst::afw::image::TanWcs::skyToPixelImpl(geom::Angle, geom::Angle) const Error: wcslib returned a status code of 9 at sky 30.18, -3.8 deg: One or more of the world coordinates were invalid {0} lsst::pex::exceptions::RuntimeError: 'Error: wcslib returned a status code of 9 at sky 30.18, -3.8 deg: One or more of the world coordinates were invalid' {code} I believe it's because wcslib can fail nastily if coordinates are well off an image (e.g. [here|https://github.com/lsst/pipe_tasks/blob/master/python/lsst/pipe/tasks/selectImages.py#L196-L199]).
| 0.5 |
1,574 |
DM-7781
|
09/28/2016 17:40:46
|
JUnit Test for Zscale
|
The Zscale class is used by FitsRead. Therefore, it is important to make sure it works correctly all the time. The unit test is needed to identify any bugs introduced by changing this class.
| 8 |
1,575 |
DM-7784
|
09/29/2016 01:30:38
|
WISE single exposure image fails sometime to be plotted in LC viewer
|
in the LC prototype, once the phase folded table is displayed, one can highlight a row and the corresponding single exposure will be plotted based on the 'frame_id'. For some reason, the plot request fails on 'frame_id' starting with 09xx in the example used. Step to reproduce: Go to LC viewer (lc.html) and use raw table from: http://web.ipac.caltech.edu/staff/ejoliet/demo/OneTarget-27-AllWISE-MEP-m82-2targets-10arsecs.tbl Then, click for example on the row where 'frame_id' == 09401b071, see plot fails. Although FITS exists in IBE: http://irsa.ipac.caltech.edu/ibe/data/wise/merge/merge_p1bm_frm/1b/09401b/071/09401b071-w1-int-1b.fits Please investigate and fix.
| 3 |
1,576 |
DM-7798
|
09/29/2016 14:25:09
|
Add remote launch capabilities to the Time Series viewer
|
Do the following: * Add hooks so the time series tool to be able to be launched externally * Gator or the triview (or something else) should be able to launch the LC with search parameters (see my comment below about initial values for IRSA)
| 2 |
1,577 |
DM-7801
|
09/29/2016 14:31:32
|
Wrap afw::cameraGeom with pybind11
|
The generated wrappers will live parallel to the Swig wrappers. This ticket only covers the C++ wrappers themselves, not the Python layer on top (which will continue to use the old wrappers) all work will stay on a separate branch and will not be merged to master until DM-6168 is complete. The tests included in this ticket are: # testDetector.py # testMakePixelToTanPixel.py # testExposure.py # testCamGeomFitsUtils.py # testCameraGeom.py # testDistortedTanWcs.py # testCameraTransformMap.py # testColor.py # testOrientation.py # testCameraSys.py # testWarper.py (moved to DM-8619)
| 8 |
1,578 |
DM-7805
|
09/29/2016 16:40:25
|
Changing column to plot doesn't reset the 'flip' option to unchecked state
|
When doing a catalog search (or Gator), the x-axis in the xy-plot comes in 'reverse' direction which is wanted for plotting ra vs. dec. But when the column is changed, the option should be reset to regular x-axis direction ('reverse' checkbox to be unchecked). Please fix.
| 1 |
1,579 |
DM-7811
|
09/29/2016 22:13:08
|
WBS restructure discussion
|
participate discussion of WBS restructuring, review and edit
| 2 |
1,580 |
DM-7812
|
09/29/2016 22:19:32
|
2D plotting package design discussion
|
Participate in the 2-day discussion of 2D plotting package design, functions supported, and strategy for introducing new 3rd party software packages,
| 2 |
1,581 |
DM-7813
|
09/29/2016 22:20:18
|
Organize the 2D plotting package design discussion
|
Organize in the 2-day discussion of 2D plotting package design, functions supported, and strategy for introducing new 3rd party software packages,
| 3 |
1,582 |
DM-7814
|
09/29/2016 22:22:10
|
2D plotting package design discussion
|
Participate in the 2-day discussion of 2D plotting package design, functions supported, and strategy for introducing new 3rd party software packages,
| 3 |
1,583 |
DM-7815
|
09/29/2016 22:23:24
|
2D plotting package design discussion
|
Participate in the 2-day discussion of 2D plotting package design, functions supported, and strategy for introducing new 3rd party software packages,
| 3 |
1,584 |
DM-7816
|
09/29/2016 22:24:02
|
2D plotting package design discussion
|
Participate in the 2-day discussion of 2D plotting package design, functions supported, and strategy for introducing new 3rd party software packages,
| 3 |
1,585 |
DM-7817
|
09/29/2016 22:25:29
|
2D plotting package design discussion
|
Participate in the 2-day discussion of 2D plotting package design, functions supported, and strategy for introducing new 3rd party software packages,
| 1 |
1,586 |
DM-7818
|
09/29/2016 22:26:10
|
2D plotting package design discussion
|
Participate in the 2-day discussion of 2D plotting package design, functions supported, and strategy for introducing new 3rd party software packages,
| 1 |
1,587 |
DM-7819
|
09/29/2016 22:26:45
|
2D plotting package design discussion
|
Participate in the 2-day discussion of 2D plotting package design, functions supported, and strategy for introducing new 3rd party software packages,
| 1 |
1,588 |
DM-7820
|
09/29/2016 22:27:20
|
2D plotting package design discussion
|
Participate in the 2-day discussion of 2D plotting package design, functions supported, and strategy for introducing new 3rd party software packages,
| 1 |
1,589 |
DM-7823
|
09/30/2016 10:39:43
|
meeting with SLAC camera team for visualization discussion
|
SUIT team members Trey, Tatiana, Loi, and Gregory traveled to SLAC to meet with Tony and Stuart for a 2-day discussion of the relevant issues in using Firefly for camera I&T visualization support. We came up with a rough design which defines the interface between the camera diagnostic cluster and Firefly server, the services that camera team will provide so Firefly can display the images at different resolutions as needed.
| 8 |
1,590 |
DM-7824
|
09/30/2016 11:20:36
|
Document the Histogram API and fix some minor bugs
|
When exposing Histogram React Component to API and writing the demo, I found the following bugs: - log scale for y axis fails - tooltip might be misaligned with bin boundaries
| 2 |
1,591 |
DM-7825
|
09/30/2016 11:35:18
|
Large catalog fail to completely load after filter was applied.
|
MAJOR: imposing filters on the catalog makes the plot go away. (1) Gator. Search in WISE. All WISE. M16. 30 arcmin (2) In the data table, enable filters. Type “>10” in each of the w1snr, w2snr, w3snr, w4snr column filter boxes. do NOT tab across to get them; it messes up the column headings. (3) the plot never comes back, the overlays never update on the image, and the “circular cyclical dots” indicating “I’m thinking” never stops. As in, I did this, reproduced this, typed this up, got distracted by a text, checked email in different accounts, came back to this, and still no updates. Reproducibility: restarted tool both platforms. WISE/AllWISE/M16/30 arcmin cone. both come back with 17,816 sources. impose filters. plot vanishes as soon as first filter imposed. never returns from all four filters being imposed. Firefox is tilling me 695 sources are left (with the “circular cyclical dots” still spinning) and Chrome is telling me 979 sources are left (with the “circular cyclical dots” still spinning). another test: restarted tool both platforms. WISE/AllWISE/M16/30 arcmin cone. both come back with 17,816 sources. impose JUST filter on w1snr. >10 Firefox: 3823 sources, plot vanishes, overlay doesn’t update, “circular cyclical dots” still spinning Chrome: 3609 sources, plot vanishes, overlay doesn’t update, “circular cyclical dots” still spinning So, this problem exists for one filter AND more than one filter. *Copied from the pull request by Loi (9/30/2016)* We were using cookies to pass websocket connection info to the server. This approach does not work in and embedded mode, ie. Gator. I've converted to use custom http headers instead. This also affects python api. I've modified the code to reflect the changes. This change fixed the above problem and should not have any regression issue
| 2 |
1,592 |
DM-7830
|
09/30/2016 12:38:30
|
display single exposure from raw table as well as the phase folded curve table
|
Please, add the same feature to the raw-table highlight as the phase folded table. When the raw-table LC is loaded and a row is highlighted, display the image single exposure.
| 2 |
1,593 |
DM-7840
|
09/30/2016 18:22:29
|
Change the way the single exposure request is built from LC table to be generic
|
Right now, the LC viewer knows how to fetch the single exposure by hard-coding a WebPlot request (plus some column to use) which is specific to WISE and has a particular image set that doesn't necessarily correspond to the time of the observation (see problem describe in DM-7784. The single exposure to be displayed should come from and contained by the table itself. The LC viewer shouldn't be aware about the mission, image set or any other specific logic. Change the way to fetch the single exposure by reading out the URL from the table (a column for each time identified by the flux as a prefix of the column name will be present in the table) and build a WebPlotRequest based on a URL fetch instead. This method is generic for any data-set such as PTF, WISE, IRTF, etc. The generator of the table is responsible for giving the unique way to fetch the single exposure for a particular time and band. For example, in case of WISE MEP table, it will contain 4 columns, each of them will have a name such as 'w1_url', 'w2_url', etc. When the user select the flux column to be used by the periodogram/xy-plot, for example 'w1mpro_ep', the image URL request to be used will come from the column which prefix name matches the user selected flux column, in the example, it will be 'w1_url'. The url will be an IBE call to WISE like: http://irsa.ipac.caltech.edu/ibe/data/wise/allsky/4band_p1bm_frm/7b/00717b/102/00717b102-w2-int-1b.fits
| 8 |
1,594 |
DM-7844
|
10/01/2016 08:01:48
|
cmd-line tasks should log the command being executed
|
When a command-line task is executed it would be very helpful to have the command logged. This helps diagnose issues with packages such as {{ci_hsc}} and {{validate_drp}}. This is trivial when the task is executed from the command line, e.g. add the following to {{ArgumentParser}}: {code} log.info("Running: {}".format(" ".join(sys.arvg))) {code} It is a bit trickier if the command is executed by code that calls {{CmdLineTask.parseAndRun}} directly; the arguments are readily available but determining the task will require introspection.
| 1 |
1,595 |
DM-7855
|
10/03/2016 12:59:07
|
Propose new WBS breakdown for 02C.04
|
Develop a new WBS describing work to be undertaken in 02C.04.
| 2 |
1,596 |
DM-7858
|
10/03/2016 13:05:44
|
Develop DRP planning packages
|
Develop planning packages suitable for loading into PMCS which reflect the DRP plan.
| 8 |
1,597 |
DM-7860
|
10/03/2016 13:08:52
|
Produce straw-man plan for Calibration Products Pipeline
|
Using the * Understanding developed in DM-7560; * Dependency map developed in DM-7558; * Responsibility assignments developed in DM-7031; * Rough resource requirements developed in DM-7032, DM-7034; * Tooling decided in DM-7559; develop an outline of a plan for Calibration Products Production.
| 5 |
1,598 |
DM-7862
|
10/03/2016 15:21:25
|
Update StarFast functionality
|
A few components and functions of the StarFast simulator have fallen behind the needs of DM-6245. In particular, the exposures created by the simulator are missing needed metadata. This ticket is to clean up the interface to better support the current uses, and to supply the missing metadata.
| 2 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.