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
|
|---|---|---|---|---|---|
999 |
DM-5182
|
02/18/2016 17:15:33
|
Hook up help system
|
We need to help system like we have in GWT.
| 8 |
1,000 |
DM-5187
|
02/18/2016 19:02:07
|
Set Qserv master in env variable for Docker containers
|
This would allow use of pre-configured container on all clusters, indeed the only parameter which currently change in cluster install is master fqdn. See http://xrootd.org/doc/dev42/Syntax_config.htm and {code} if defined ?~EXPORTPATH set exportpath = $EXPORTPATH else set exportpath = /tmp fi all.export $exportpath {code}
| 3 |
1,001 |
DM-5196
|
02/19/2016 11:49:49
|
swift API availability?
|
The downtime announcement email for {{Nebula unavailable Feb 9-10}} mentioned a "roadmap" for swift. I have checked and post maintenance, there is not a swift endpoint available in the catalog. Is there a time line for availability?
| 1 |
1,002 |
DM-5197
|
02/19/2016 12:34:00
|
Test and robustify shapelet PSF approximations
|
The CModel code ported from HSC only works as well as the ShapeletPsfApproximation algorithm that runs before it, but we've switched on the LSST side to a more flexible algorithm that isn't as nearly as battle-tested as what's been running on the HSC side, and there are some concerning indications from [~pgee]'s work that it can be catastrophically slow on some reasonable PSFs. On this issue, I'll run it on some real HSC data and try to improve it, even if that means reducing the flexibility back to what was on the HSC side in some ways.
| 8 |
1,003 |
DM-5198
|
02/19/2016 13:14:41
|
FITS Visualizer porting: Statistics - part 2 - drawing overlay & 3 color support
|
drawing overlay 3 Color Support
| 8 |
1,004 |
DM-5200
|
02/19/2016 15:57:33
|
instance I/O errors
|
The kernel dmesg for Instance {{bbfd7458-6dd6-4412-a8ba-8d417c3df56b}} has started reporting thousands of block I/O errors and these are starting to trickle up as a filesystem I/O errors. I suspect this is likely a hypervisor I/O issue. {code} [687301.556430] Buffer I/O error on device dm-3, logical block 3768490 [687301.556433] Buffer I/O error on device dm-3, logical block 3768491 [687301.556436] Buffer I/O error on device dm-3, logical block 3768492 {code} {code} $ openstack server show bbfd7458-6dd6-4412-a8ba-8d417c3df56b +--------------------------------------+-----------------------------------------------------------------------+ | Field | Value | +--------------------------------------+-----------------------------------------------------------------------+ | OS-DCF:diskConfig | MANUAL | | OS-EXT-AZ:availability_zone | nova | | OS-EXT-STS:power_state | 1 | | OS-EXT-STS:task_state | None | | OS-EXT-STS:vm_state | active | | OS-SRV-USG:launched_at | 2016-02-11T23:36:25.000000 | | OS-SRV-USG:terminated_at | None | | accessIPv4 | | | accessIPv6 | | | addresses | LSST-net=172.16.1.115, 141.142.209.121 | | config_drive | | | created | 2016-02-11T23:36:12Z | | flavor | m1.xlarge (5) | | hostId | f7fbf308022d02f52e1111c91cf578d852784d290d0e0ddb0d69635c | | id | bbfd7458-6dd6-4412-a8ba-8d417c3df56b | | image | centos-7-docker-20151116230205 (59a2a478-11ab-41c5-affc-29706d38d65a) | | key_name | vagrant-generated-comshorc | | name | el7-docker-jhoblitt | | os-extended-volumes:volumes_attached | [] | | progress | 0 | | project_id | 8c1ba1e0b84d486fbe7a665c30030113 | | properties | | | security_groups | [{'name': 'default'}, {'name': 'remote SSH'}] | | status | ACTIVE | | updated | 2016-02-11T23:36:25Z | | user_id | 83bf259d1f0c4f458e03f9002f9b4008 | +--------------------------------------+-----------------------------------------------------------------------+ {code}
| 1 |
1,005 |
DM-5202
|
02/19/2016 17:54:03
|
Remove LOGF macros from log package
|
We have removed all uses of LOGF macros from qserv and as far as I know no other clients use those macros. It's time to clean up log package itself from those macros.
| 1 |
1,006 |
DM-5204
|
02/19/2016 18:13:36
|
Remove remaining LOGF macros from qserv
|
There are still few cases of LOGF macros in qserv, have to replace them all.
| 1 |
1,007 |
DM-5206
|
02/20/2016 11:21:58
|
Please do not write garbage to the FITS EQUINOX
|
The equinox is not relevant when dealing with ICRS coordinates. When {{afw}} manipulates {{Wcs}} objects, it simply doesn't bother initializing the {{equinox}} field of its {{_wcsInfo}} struct when dealing with an ICRS system. When {{afw}} persists the {{Wcs}} to FITS, it blindly writes whatever happens to be in that uninitialized field to the FITS header. Thus, we end up with something like: {code} EQUINOX = 9.87654321E+107 / Equinox of coordinates {code} This should be no problem, since, per the [FITS standard|http://fits.gsfc.nasa.gov/standard30/fits_standard30aa.pdf] (page 30), the {{EQUINOX}} is "not applicable" if they {{RADESYS}} is {{ICRS}}. The reader should thus ignore this value. However, [SAOimage DS9|http://ds9.si.edu] version 7.4.1 (the latest release at time of writing) does _not_ ignore the {{EQUINOX}}. Rather, it refuses to handle the WCS for the image. Note that version 7.3 of DS9 does not seem to have the same issue. While this does seem to be a bug in DS9, it's easy enough to work around by simply not writing {{EQUINOX}}.
| 0.5 |
1,008 |
DM-5247
|
02/26/2016 12:01:14
|
Segfault in shapeHSM centroid extractor
|
[~boutigny] reports a segfault in {{meas_extenstions_shapeHSM}}. He provides the following backtrace: {code} Program received signal SIGSEGV, Segmentation fault. 0x00007fffe7043156 in lsst::afw::table::BaseRecord::getElement<lsst::afw::table::Flag> (this=0x21c8d60, key=...) at include/lsst/afw/table/BaseRecord.h:61 61 typename Field<T>::Element * getElement(Key<T> const & key) { (gdb) bt #0 0x00007fffe7043156 in lsst::afw::table::BaseRecord::getElement<lsst::afw::table::Flag> (this=0x21c8d60, key=...) at include/lsst/afw/table/BaseRecord.h:61 #1 0x00007fffdc8775f2 in set<lsst::afw::table::Flag, bool> (value=<synthetic pointer>, key=..., this=0x21c8d60) at /home/boutigny/CFHT/lsstsw/stack/Linux64/afw/11.0-8-g38426eb/include/lsst/afw/table/BaseRecord.h:137 #2 setValue (value=true, i=0, record=..., this=0x1da2500) at include/lsst/meas/base/FlagHandler.h:73 #3 lsst::meas::base::SafeCentroidExtractor::operator() (this=<optimized out>, record=..., flags=...) at src/InputUtilities.cc:134 #4 0x00007fffd03655c6 in lsst::meas::extensions::shapeHSM::HsmPsfMomentsAlgorithm::measure (this=0x1da2410, source=..., exposure=...) at src/HsmMoments.cc:115 #5 0x00007fffd06708d5 in _wrap_HsmPsfMomentsAlgorithm_measure (args=0x7fffccc67b90) at python/lsst/meas/extensions/shapeHSM/hsmLib_wrap.cc:14337 #6 0x00007ffff7aee37f in ext_do_call (nk=-859407472, na=<optimized out>, flags=<optimized out>, pp_stack=0x7fffffff7d18, func=0x7fffd0c21878) at Python/ceval.c:4345 #7 PyEval_EvalFrameEx (f=<optimized out>, throwflag=<optimized out>) at Python/ceval.c:2720 #8 0x00007ffff7aefdbe in PyEval_EvalCodeEx (co=0x7fffd0a9ceb0, globals=<optimized out>, locals=<optimized out>, args=<optimized out>, argcount=3, kws=0x7fffccd43b08, kwcount=0, defs=0x0, defcount=0, closure=0x0) at Python/ceval.c:3267 {code} See the discussion at DM-4780.
| 2 |
1,009 |
DM-5251
|
02/26/2016 12:35:45
|
lsstsw breakage with spaces in paths
|
There are still some issues relating to using {{lsstsw}} to build the stack when spaces are in the path to the {{$LSSTSW}} location. This is a fine thing to sort out on Rodeo Day...
| 1 |
1,010 |
DM-5252
|
02/26/2016 13:21:52
|
Base "bright star" cut on S/N instead of magnitudes
|
The astrometry histogram generated by validateDrp.py conflates astrometric and photometric calibration because it uses magnitude for brightness, and this relies on the accuracy of the photometric calibration. [~ctslater] suggests (and I agree) that brightness should be based on signal to noise ratio, thus making the astrometry histogram independent of photometric calibration.
| 2 |
1,011 |
DM-5264
|
02/26/2016 15:41:01
|
Modernize python in lsst_build
|
The python in {{lsst_build}} uses old-style print and exception handling. These should be updated to the current standard.
| 1 |
1,012 |
DM-5265
|
02/26/2016 15:47:11
|
Turn on bias-jump fix for all CCDs
|
The overscan fix to handle bias jump in an amplifier done in DM-4366 introduced a new config parameter {{overscanBiasJumpBKP}}, and the fix is applied for CCDs on the backplanes specified in {{overscanBiasJumpBKP}}. Previously, the default is to only fix CCDs on backplanes next to the focus chips. But [~mfisherlevine] also see the bias jump features in other CCDs. It would make more sense to turn it on for all CCDs by default.
| 0.5 |
1,013 |
DM-5275
|
02/29/2016 17:17:05
|
make floating point exception handling cross-platform (or remove it)
|
jointcal currently has a couple of trapfpe() functions that wrap feenableexcept, which doesn't exist on OSX. Were these an important part of error handling in meas_simastrom, or can I just remove them?
| 2 |
1,014 |
DM-5277
|
03/01/2016 08:30:39
|
replace buildbot with jenkins job(s)
|
Removing buildbot and replacing it with jenkins would provide a number of benefits * one less dashboard for developers to know about / interact with * one less system for SQRE to maintain * lessening the cost of refactoring the CI drivers scripts as synchronized updates to two CI system configurations would no longer be necessary It should also be easy to go one step further and try to eliminate the need for developers to manually log into the {{lsstsw}} account on {{lsst-dev}} to publish eups distrib packages.
| 3 |
1,015 |
DM-5279
|
03/01/2016 10:09:57
|
arrays not properly transmitted
|
Sending a property set with an array as one of the entries only passes the last element of the array.
| 1 |
1,016 |
DM-5281
|
03/01/2016 11:20:16
|
Port HSC skymap, shapelet changesets to LSST
|
We identified in DM-5162 some changesets that still need to be ported from HSC to LSST: * skymap: ** f83f71718eac5307d575d3113ee3757a63a16de2: Set vertex list in ExplicitTractInfo. * shapelet: ** bb928df3fc2fafe5183e0d075da19994f0af4fc7: Let the value to normalize to be specified in [Multi]ShapeletFunction
| 0.5 |
1,017 |
DM-5283
|
03/01/2016 11:24:33
|
Port HSC daf_butlerUtils changesets to LSST
|
We identified in DM-5162 several changesets that still need to be ported from HSC to LSST: * daee24edba01b01a0412df7f9b4cf70be5b10860: CameraMapper: allow a default filter name to be provided * e3fee95d6a1850dd2309d3ebe4e3ef3ffe38eef0: CameraMapper: normalize path names, and remove leading double slash * 476b6ddccd9d0cceb2b89ca34bee7d0fdcd70694: preserve timestamps in cameraMapper.backup() * b2491ef60e5e23afa7d9f0297f257e694aa1af35: Only attempt to update Wcs if it's available * 9f62bcce588fa9abc8e1e44ff2f0275e5230f629: Registry: hold registry cache for a single thread only (HSC-1035) * 412f03b95b7a5e82003ab33a61bd43adbf465188: Registry: use a pool of registries to avoid having too many open files
| 2 |
1,018 |
DM-5284
|
03/01/2016 11:27:32
|
Port HSC meas_extensions_simpleShape package to LSST
|
HSC uses a package, meas_extensions_simpleShape, which needs to be ported to LSST. The package is used for basic shape measurements for determining focus, and also serves as a simple guide for writing measurement plugins.
| 3 |
1,019 |
DM-5286
|
03/01/2016 11:32:39
|
Port HSC meas_deblender changesets to LSST
|
We identified in DM-5162 a few changesets that still need to be ported from HSC to LSST: * a8cf6c22df14494d6dcf2d7354c695cba9506301: Clarify tiny footprint limit * 624790aa63a38fb7a328ebc21abfd1b10503aa26: config: change default strayFluxRule * db7d705de93b43a5f32f771c716b1c5c7368d124: consolidate failed peak logic and downgrade warning We also identified a few differences that should be resolved: * clipStrayFluxFraction defaults to 0.01 for LSST, 0.001 for HSC * Stray file, src/Baseline.cc.orig, on LSST side
| 1 |
1,020 |
DM-5287
|
03/01/2016 11:34:32
|
Port HSC ip_isr changesets to LSST
|
We identified in DM-5162 some changesets that still need to be ported from HSC to LSST: * f1cee734998f1faf86c02af42ea599b077847eeb: IsrTask: allow fallback to a different filter when loading calibrations * 89cd629bb8e1a72a545176311b1ef659358d95af: saturationDetection: apply to overscan as well as image
| 1 |
1,021 |
DM-5288
|
03/01/2016 11:38:22
|
Port HSC pipe_tasks changesets to LSST
|
We identified in DM-5162 some changesets that still need to be ported from HSC to LSST: * 31ab5f02f7722650ad0a0eb4e2f7f8b3e0073366, 0c9a4a06bfb34ed26c72109131ef9f4a8c8f237a: multiBand: save background-subtracted coadd as deepCoadd_calexp * e99e140feafe28e6f034143e8ee2ae58e9a9358d: Rejig interface for DetectCoaddSourcesTask to provide non-dataRef-centric API * 829ee0cdd605ed027af1fada4446b715d9a5180d: multiband: activate sky objects * MeasureMergedCoaddSources.doMatchSources defaults to False * ProcessImageConfig.doWriteHeavyFootprintsInSources defaults to False ? * 56666e8feba6893ac95fd4982d3e0daf6baf2d34: WcsSelectImagesTask: catch imagePoly is None We also noticed some differences: * * CalibrateConfig.setDefaults doesn't call parent * CalibrateTask.run isn't returning apCorrMap * reserveFraction=-1 instead of 0.2
| 3 |
1,022 |
DM-5289
|
03/01/2016 11:45:57
|
Port HSC obs_subaru changesets to LSST
|
We identified in DM-5162 several changesets that still need to be ported from HSC to LSST: * 8948917de4579e032c7bbb2c8316014446e3841b: config: add astrometry filter map for HSC narrow-band filters * 69d35a890234e37c1142ddbeff43e62fe36e6c45: Set radius for flux.naive, adjust comment for flux.sinc * 8ea54d10f5ae56f8b6f244bca76d5796ae015216: config: disable sigma clipping in coadd assembly * 8d2f4a02d0d668fc82e853b633444d8e0fe80010: config: reduce coadd subregionSize * e36bd1b4410812ca314f50c01f899d92acc0e7a5: config: set pixelScale for jacobian correction * Remove processCcdOnsiteDb.py, processStack.py * Rename stacker.py to coaddDriver.py or whatever Nate chooses in DM-3369 * 49e9f5dcf16490f6be6438b89b17911a0cd35fb2: Fixed obvious errors caused by introducing VignetteConfig * 8948917de4579e032c7bbb2c8316014446e3841b: config: add astrometry filter map for HSC narrow-band filters * daa43eeac46e8708de6f37feeb5d5d16a3caca11: HscMapper: set unit exposure time for dark * 77ff7c89d56bed94bca4f320f839dbd20fbab641: Set BAD mask for dead amps instead of SAT We also noticed the following need to be done: * Forced photometry configuration (CCDs and Coadds) * Sanitize config of OBS_SUBARU_DIR (use getPackageDir) * multiband config files need "root" --> "config" * No astrometry in measureCoaddSources * Narrow bands missing from priority list * detectCoaddSources removed from multiband * Move filterMap from config/processCcd.py into own file
| 5 |
1,023 |
DM-5290
|
03/01/2016 13:37:42
|
Add z-index for dialogs components
|
Some of the outside modules that we have brought in have a z-index. We need to make sure that our dialog components stay on top of them.
| 2 |
1,024 |
DM-5291
|
03/01/2016 13:44:37
|
Docker-ready configuration system for LTD Keeper
|
To deploy LTD Keeper in a Docker container (DM-5194), it’s best practice to handle all configurations through environment variables. In DM-4950, LTD Keeper was configured through files for test and dev/deployment profiles. What we should do is continue to allow hard-coded configurations for test and dev environments, but have a third fully fledged configuration environment that’s driven entirely by environment variables. The environment variables should allow fine grained configuration (for example, to turn off calls to individual external services for testing). This should also resolve how to deal with Google Container Engine/Kubernetes auth flow works with environment variables, config files, and profiles.
| 1 |
1,025 |
DM-5298
|
03/01/2016 16:54:28
|
Document simple simulator
|
Document the simple simulator produced in DM-4899. This will also involve some refactoring and adding unit tests to make it usable by others in the group.
| 8 |
1,026 |
DM-5302
|
03/02/2016 11:03:46
|
manage jenkins core + plugin versions
|
There have been a couple of issues that have arisen when deploying test instances vs updating an existing instance due to slight differences between plugin versions. This would be avoided by putting all plugin versions under change control. Including: * The versions of all jenkins components need to be explicitly specified * The stored job {{config.xml}}'s should be updated to reflect plugin version changes * The hipchat notification configuration should be updated to fix breakage caused by the production core/plugin update earlier this week
| 5 |
1,027 |
DM-5312
|
03/02/2016 15:12:36
|
Additional vertical partitioning tests
|
Test potential improvements in many-vertical-shards test (20,50) run-times with query optimizer settings.
| 5 |
1,028 |
DM-5319
|
03/03/2016 07:45:00
|
Fix mariadb CI
|
patch package is missing in docker container used by travis-CI.
| 1 |
1,029 |
DM-5320
|
03/03/2016 08:04:34
|
Make Bright Object Masks compatible with all cameras
|
Currently all of the logic that goes into using bright object masks falls into obs_subaru and pipe_tasks. This ticket should move parts (such as the bright object mask class) out of obs_subaru, into a camera agnostic location. The work should also duplicate relevant camera configurations and parameter overrides in the other camera packages. Bright object masks were originally introduced in DM-4831
| 2 |
1,030 |
DM-5321
|
03/03/2016 09:22:08
|
MeasureApCorrTask should use slot_CalibFlux as default ref flux
|
{{MeasureApCorrTask}} uses "base_CircularApertureFlux_17_0" as its default reference flux. It should use "slot_CalibFlux" instead. Also check obs_sdss packages for overrides that can be removed; obs_sdss certainly has one in {{config/processCcdTask.py}}
| 0.5 |
1,031 |
DM-5324
|
03/03/2016 13:13:09
|
Convert GWT code to pure JavaScript (X16, part2, basic)
|
Continue to work on the GWT code conversion to JavaScript.
| 100 |
1,032 |
DM-5336
|
03/04/2016 08:25:53
|
Fix minor issues in docker procedure
|
- params.sh was missing at configuration - startup.py wasn't importing correctly module "utils" - remove unused parameters in params.sh
| 1 |
1,033 |
DM-5348
|
03/04/2016 12:07:31
|
Get rid of ProcessCcdSdssTask and ProcessCcdDecamTask
|
Update {{ProcessCcdTask}} so that it can be used with different datasete types as appropriate for the ISR task. This will allow us to get rid of obs-specific variants {{ProcessCcdSdssTask}} and {{ProcessCcdDecamTask}} The plan is to change {{ProcessCcdTask}} as follows: - set {{doMakeDataRefList=False}} in the call to {{add_id_argument}} - get the dataset type from the ISR task (default to "raw") and set it in data container - make the dataRef list by calling {{makeDataRefList}} on the data container Question for DECam folks: do you want two executable scripts for DECam (one that processes data from the community pipeline and one that performs ISR)? Or do you prefer one exectutable (in which case you switch between performing ISR and reading the output of the community pipeline output by retargeting the ISR task)? If you prefer one binary, then which should be the default: perform ISR or read the output of the community pipeline?
| 2 |
1,034 |
DM-5349
|
03/04/2016 12:15:18
|
Revise LSE-140 to account for recent changes to calibration instrumentation
|
Produce a revision of LSE-140, the DM - to - auxiliary instrumentation ICD, taking into account recent changes to the calibration instrumentation.
| 5 |
1,035 |
DM-5350
|
03/04/2016 12:20:25
|
Establish goals and create EA framework for LSE-140 update
|
Deliverable: together with [~pingraham], identify the changes needed and develop initial content in EA.
| 2 |
1,036 |
DM-5351
|
03/04/2016 12:27:24
|
Create change request for LSE-140
|
Deliverable: change request and document diffs for LSE-140
| 1 |
1,037 |
DM-5355
|
03/04/2016 16:45:18
|
meas_algorithms uses packages that are not listed in table file
|
{{meas_algorithms}} directly uses the following packages not expressed in the table file: * Minuit2 * daf_persistence * daf_base * pex_config * pex_exceptions * pex_policy
| 0.5 |
1,038 |
DM-5356
|
03/05/2016 10:37:51
|
Test consistency of Shear Measurements with different Psfs
|
DM-1136 was done with a single Psf, partly to avoid some of the problems we found with PsfShapeletApprox. In this issue, I will look at consistency of the measurement for different Psfs.
| 8 |
1,039 |
DM-5359
|
03/05/2016 22:53:37
|
Update DMTN-002 to reflect last changes
|
Need to update documentation with latest changes on {{pipe_base}}, {{pipe_supertask}} and {{pipe_flow}}
| 1 |
1,040 |
DM-5364
|
03/06/2016 17:53:15
|
Image Select Panel: Support add or modify of plot
|
previously the image select panel would only modify a plot. Now give it the ability to add a plot.
| 8 |
1,041 |
DM-5370
|
03/07/2016 13:56:37
|
Create lsst_ci package as a continuous integration build target
|
Create an {{lsst_ci}} package to be built for the continuous integration testing. Plan: 1. Create empty package that has dependencies on {{obs_cfht}}, {{obs_decam}}, {{obs_subaru}}, {{testdata_cfht}}, {{testdata_decam}}, {{testdata_subaru}}. (/) 2. Ensure above builds. (/) 3. Add {{obs_lsstSim}} and ensure that it builds. (/) The following were moved to DM-5381: [ [~tjenness] : How can I get strikethrough to work in the following list?] 3. Add dependencies on {{validation_data_cfht}} and {{validation_data_decam}}, and {{validate_drp}}. 4. Run CFHT, DECam quick examples in {{validate_drp}}. 5. Test for successful running of the above examples. Fail and trigger Jenkins FAILURE message if these examples fail. 6. Check performance of CFHT, DECam runs against reference numbers. Fail if there is a significant regression. 7. Decide how to include {{ci_hsc}}, which currently can take at least 30 minutes to process the image data.--
| 1 |
1,042 |
DM-5372
|
03/07/2016 18:06:30
|
Fix obs_* packages and ci tests broken by DM-4683
|
The butler changes in DM-4683, in particular the removal of {{.mapper}} from the interface exposed by a {{Butler}} object, broken {{obs_cfht}}, {{obs_decam}}, and {{ci_hsc}}. This issue will fix those changes, and search for additional broken things. This work is proceeding in conjunction with DM-5370 to test that the CI system, e.g. {{lsst_ci}}, is sensitive to these breakages and fixes.
| 1 |
1,043 |
DM-5384
|
03/08/2016 12:28:38
|
Port SdssShape changes from HSC meas_algorithms to LSST meas_base
|
In porting {{meas_algorithm}} changes from HSC to LSST, modifications to the {{SdssShape}} algorithm were discovered. These changes should be transferred to LSST.
| 3 |
1,044 |
DM-5385
|
03/08/2016 13:55:47
|
calib_psfReserved is only defined when candidate reservation is activated
|
The schema should in general not be a function of whether particular features are enabled or disabled so that users can have confidence looking for columns. However, {{MeasurePsfTask}} only creates the {{calib_psfReserved}} column when {{reserveFraction > 0}}. This causes warnings when attempting to propagate flags from calibration catalogs to deep catalogs.
| 1 |
1,045 |
DM-5390
|
03/08/2016 21:22:32
|
JavaScript loading/caching plan
|
We need to ensure that the latest version of the application(javascript) is loaded. Conditions: 1. once loaded, it should be cached by the browser. 2. name of the script has to be a static, so it can be referenced by api user. 3. it also has to load dependencies(gwt scripts) after the main script is loaded. To do this, we created a tiny firefly_loader.js script whose role is to load the main script and then its dependencies. firefly_loader.js is configured to never cache so that the latest main script is always picked up. The main script is appended with a unique hash on every build. This ensures that the browser will pick up the new script the very first time, and then cache it for future use.
| 2 |
1,046 |
DM-5392
|
03/09/2016 09:53:03
|
Please stop leaving repoCfg.yaml files around
|
After a recent change to {{daf_persistence}} and possibly other packages I'm finding that many packages leave {{repoCfg.yaml}} files lying around after they run unit tests. I'm not sure what is best to do about these files. If they are temporary, as I am guessing, then I think we need some way to clean them up when the tests that generated them have run. If they are intended to be permanent (which would be surprising for auto-generated files) then they should probably be committed? I hope we can do better than adding them to .gitignore.
| 1 |
1,047 |
DM-5394
|
03/09/2016 11:41:15
|
Investigate boost compiler warnings and update boost to v1.60
|
As reported in comments in DM-1304 clang now triggers many warnings with Boost v1.59: {code} /Users/rowen/UW/LSST/lsstsw/stack/DarwinX86/boost/1.59.lsst5/include/boost/archive/detail/check.hpp:148:5: warning: unused typedef 'STATIC_WARNING_LINE148' [-Wunused-local-typedef] BOOST_STATIC_WARNING(typex::value); ^ /Users/rowen/UW/LSST/lsstsw/stack/DarwinX86/boost/1.59.lsst5/include/boost/serialization/static_warning.hpp:100:33: note: expanded from macro 'BOOST_STATIC_WARNING' #define BOOST_STATIC_WARNING(B) BOOST_SERIALIZATION_BSW(B, __LINE__) ^ /Users/rowen/UW/LSST/lsstsw/stack/DarwinX86/boost/1.59.lsst5/include/boost/serialization/static_warning.hpp:99:7: note: expanded from macro 'BOOST_SERIALIZATION_BSW' > BOOST_JOIN(STATIC_WARNING_LINE, L) BOOST_STATIC_ASSERT_UNUSED_ATTRIBUTE; ^ /Users/rowen/UW/LSST/lsstsw/stack/DarwinX86/boost/1.59.lsst5/include/boost/config/suffix.hpp:544:28: note: expanded from macro 'BOOST_JOIN' #define BOOST_JOIN( X, Y ) BOOST_DO_JOIN( X, Y ) ^ /Users/rowen/UW/LSST/lsstsw/stack/DarwinX86/boost/1.59.lsst5/include/boost/config/suffix.hpp:545:31: note: expanded from macro 'BOOST_DO_JOIN' #define BOOST_DO_JOIN( X, Y ) BOOST_DO_JOIN2(X,Y) ^ /Users/rowen/UW/LSST/lsstsw/stack/DarwinX86/boost/1.59.lsst5/include/boost/config/suffix.hpp:546:32: note: expanded from macro 'BOOST_DO_JOIN2' #define BOOST_DO_JOIN2( X, Y ) X##Y ^ <scratch space>:25:1: note: expanded from here STATIC_WARNING_LINE148 ^ {code} v1.60 is the current version so we should see if these warnings have been fixed in that version.
| 2 |
1,048 |
DM-5402
|
03/09/2016 14:25:39
|
Make cluster deployment scripts more generic and enable ccqserv100...124
|
These scripts will be improved (i.e. more genericity) and integrated inside Qserv code. Qserv will be deployed on ccqserv100 to ccqserv125
| 3 |
1,049 |
DM-5406
|
03/09/2016 18:13:18
|
Require fields listed in icSourceFieldsToCopy to be present
|
{{CalibrateTask}} presently treats config field {{icSourceFieldsToCopy}} as a list of fields to copy *if present*. This was required because one of the standard fields to copy was usually missing. However, [~price] fixed that problem in DM-5385. Now we can raise an exception if any field listed is missing (though I propose to continue ignoring {{icSourceFieldsToCopy}} if isSourceCatalog is not provided).
| 1 |
1,050 |
DM-5410
|
03/10/2016 10:18:51
|
DecamIngestTask is mis-calling openRegistry
|
`DecamIngestTask` is mis-calling `lsst.pipe.tasks.RegistryTask`. Line 59: {code} with self.register.openRegistry(args.butler, create=args.create, dryrun=args.dryrun) as registry: {code} {{openRegistry}} is expecting a directory name, not a butler object for the first argument Thanks to [~wmwood-vasey] for diagnosing this.
| 1 |
1,051 |
DM-5416
|
03/10/2016 15:27:11
|
Ci Deploy and Distribution Improvements part IV
|
This is a bucket epic for ongoing improvements to the CI system
| 8 |
1,052 |
DM-5419
|
03/10/2016 15:45:31
|
ci_hsc fails test requiring >95% of PSF stars to be stars on the coadd
|
Since the first week of March 2016, ci_hsc fails its test that requires that >95% of the PSF stars be identified as stars in the coadd. I suspect this is related to the DM-4692 merge. Here is a sample job that fails: https://ci.lsst.codes/job/stack-os-matrix/9084/label=centos-6/console The relevant snippet of the failure is: {code} [2016-03-10T17:12:06.667778Z] : Validating dataset measureCoaddSources_config for {'filter': 'HSC-R', 'tract': 0, 'patch': '5,4'} [2016-03-10T17:12:06.697383Z] CameraMapper: Loading registry registry from /home/build0/lsstsw/build/ci_hsc/DATA/registry.sqlite3 [2016-03-10T17:12:06.697615Z] CameraMapper: Loading calibRegistry registry from /home/build0/lsstsw/build/ci_hsc/DATA/CALIB/calibRegistry.sqlite3 [2016-03-10T17:12:07.716310Z] CameraMapper: Loading registry registry from /home/build0/lsstsw/build/ci_hsc/DATA/registry.sqlite3 [2016-03-10T17:12:07.716443Z] CameraMapper: Loading calibRegistry registry from /home/build0/lsstsw/build/ci_hsc/DATA/CALIB/calibRegistry.sqlite3 [2016-03-10T17:12:08.663566Z] : measureCoaddSources_config exists: PASS [2016-03-10T17:12:08.721051Z] : measureCoaddSources_config readable (<class 'lsst.pipe.tasks.multiBand.MeasureMergedCoaddSourcesConfig'>): PASS [2016-03-10T17:12:08.721077Z] : Validating dataset measureCoaddSources_metadata for {'filter': 'HSC-R', 'tract': 0, 'patch': '5,4'} [2016-03-10T17:12:08.721249Z] : measureCoaddSources_metadata exists: PASS [2016-03-10T17:12:08.721663Z] : measureCoaddSources_metadata readable (<class 'lsst.daf.base.baseLib.PropertySet'>): PASS [2016-03-10T17:12:08.721715Z] : Validating dataset deepCoadd_meas_schema for {'filter': 'HSC-R', 'tract': 0, 'patch': '5,4'} [2016-03-10T17:12:08.721878Z] : deepCoadd_meas_schema exists: PASS [2016-03-10T17:12:08.726703Z] : deepCoadd_meas_schema readable (<class 'lsst.afw.table.tableLib.SourceCatalog'>): PASS [2016-03-10T17:12:08.726834Z] : Validating source output for {'filter': 'HSC-R', 'tract': 0, 'patch': '5,4'} [2016-03-10T17:12:10.203469Z] : Number of sources (7595 > 100): PASS [2016-03-10T17:12:10.204166Z] : calib_psfCandidate field exists in deepCoadd_meas catalog: PASS [2016-03-10T17:12:10.204772Z] : calib_psfUsed field exists in deepCoadd_meas catalog: PASS [2016-03-10T17:12:10.205468Z] : Aperture correction fields for base_PsfFlux are present.: PASS [2016-03-10T17:12:10.206159Z] : Aperture correction fields for base_GaussianFlux are present.: PASS [2016-03-10T17:12:10.207193Z] FATAL: 95% of sources used to build the PSF are classified as stars on the coadd (0 > 0): FAIL [2016-03-10T17:12:10.207455Z] scons: *** [.scons/measure-HSC-R] AssertionError : Failed test: 95% of sources used to build the PSF are classified as stars on the coadd (0 > 0) [2016-03-10T17:12:10.207481Z] Traceback (most recent call last): [2016-03-10T17:12:10.207525Z] File "/home/build0/lsstsw/stack/Linux64/scons/2.3.5/lib/scons/SCons/Action.py", line 1063, in execute [2016-03-10T17:12:10.207556Z] result = self.execfunction(target=target, source=rsources, env=env) [2016-03-10T17:12:10.207593Z] File "/home/build0/lsstsw/build/ci_hsc/python/lsst/ci/hsc/validate.py", line 133, in scons [2016-03-10T17:12:10.207611Z] return self.run(*args, **kwargs) [2016-03-10T17:12:10.207646Z] File "/home/build0/lsstsw/build/ci_hsc/python/lsst/ci/hsc/validate.py", line 122, in run [2016-03-10T17:12:10.207663Z] self.validateSources(dataId) [2016-03-10T17:12:10.207732Z] File "/home/build0/lsstsw/build/ci_hsc/python/lsst/ci/hsc/validate.py", line 191, in validateSources [2016-03-10T17:12:10.207749Z] 0.95*psfStars.sum() [2016-03-10T17:12:10.207786Z] File "/home/build0/lsstsw/build/ci_hsc/python/lsst/ci/hsc/validate.py", line 52, in assertGreater [2016-03-10T17:12:10.207816Z] self.assertTrue(description + " (%d > %d)" % (num1, num2), num1 > num2) [2016-03-10T17:12:10.207853Z] File "/home/build0/lsstsw/build/ci_hsc/python/lsst/ci/hsc/validate.py", line 43, in assertTrue [2016-03-10T17:12:10.207877Z] raise AssertionError("Failed test: %s" % description) [2016-03-10T17:12:10.207919Z] AssertionError: Failed test: 95% of sources used to build the PSF are classified as stars on the coadd (0 > 0) [2016-03-10T17:12:10.209935Z] scons: building terminated because of errors. {code} This is the test that fails https://github.com/lsst/ci_hsc/blob/74303a818eb5049a2015b5e885df2781053748c9/python/lsst/ci/hsc/validate.py#L169 {code} class MeasureValidation(Validation): _datasets = ["measureCoaddSources_config", "measureCoaddSources_metadata", "deepCoadd_meas_schema"] _sourceDataset = "deepCoadd_meas" _matchDataset = "deepCoadd_srcMatch" def validateSources(self, dataId): catalog = Validation.validateSources(self, dataId) self.assertTrue("calib_psfCandidate field exists in deepCoadd_meas catalog", "calib_psfCandidate" in catalog.schema) self.assertTrue("calib_psfUsed field exists in deepCoadd_meas catalog", "calib_psfUsed" in catalog.schema) self.checkApertureCorrections(catalog) # Check that at least 95% of the stars we used to model the PSF end up classified as stars # on the coadd. We certainly need much more purity than that to build good PSF models, but # this should verify that flag propagation, aperture correction, and extendendess are all # running and configured reasonably (but it may not be sensitive enough to detect subtle # bugs). psfStars = catalog.get("calib_psfUsed") extStars = catalog.get("base_ClassificationExtendedness_value") < 0.5 self.assertGreater( "95% of sources used to build the PSF are classified as stars on the coadd", numpy.logical_and(extStars, psfStars).sum(), 0.95*psfStars.sum() ) {code} Note that the assertion failure messages is a bit confusing. It should say "Fewer than 95% of the sources used to build the PSF are classified as stars on the coadd."
| 1 |
1,053 |
DM-5421
|
03/10/2016 17:57:52
|
Add --show history option to cmdLineTask
|
{{pex_config}} is able to report where a config parameter is set. Please add a command line option {{--show history=config.parameter.name}} to the cmdLineTask parser. The implementation will probably want to use something like: {code:python} import lsst.pex.config.history as pch pch.Color.colorize(False) print pch.format(config.calibrate.astrometry.solver, "matchingRadius") {code}
| 2 |
1,054 |
DM-5424
|
03/11/2016 10:11:50
|
Switch PropagateVisitFlags to use src instead of icSrc
|
On DM-5084 [~jbosch] switched PropagateVisitFlags to match against icSrc instead of src because we weren't yet matching `icSrc` to `src` in ProcessCcdTask. That's now been done on DM-4692, so we can revert this. After doing so, please verify with ci_hsc that this is working, as that's where the only test of this feature lives.
| 2 |
1,055 |
DM-5427
|
03/11/2016 13:11:00
|
SingleFrameVariancePlugin can give numpy warnings
|
SingleFrameVariancePlugin can produce the following numpy warning, with no hint as to where the problem is coming from: {code} /Users/rowen/UW/LSST/lsstsw/miniconda/lib/python2.7/site-packages/numpy/core/_methods.py:59: RuntimeWarning: Mean of empty slice. warnings.warn("Mean of empty slice.", RuntimeWarning) {code} I tracked it down by adding the following code to the calling code: {code} import warnings with warnings.catch_warnings(): warnings.filterwarnings('error') {code} It would be nice if the measurement plugin handled this situation more gracefully, such as turning the warning into an exception or testing for it and handling it. One way to reproduce this problem is to run {{tests/testProcessCcd.py}} in {{pipe_tasks}}. However, it is commonly seen when running {{processCcd}} on other data, as well.
| 2 |
1,056 |
DM-5428
|
03/11/2016 13:16:32
|
ObjectSizeStarSelector can produce numpy warnings
|
`ObjectSizeStarSelector` can produce the following numpy warning: {code} RuntimeWarning: invalid value encountered in less {code} This occurs at the following point in the code: {code} for i in range(nCluster): # Only compute func if some points are available; otherwise, default to NaN. pointsInCluster = (clusterId == i) if numpy.any(pointsInCluster): centers[i] = func(yvec[pointsInCluster]) {code} where `func` has been assigned to `numpy.mean`. When I have seen this occur I have found that `dist` is an array of `nan` I suggest that the star selector handle this situation more gracefully, e.g. by reporting an appropriate exception or handling the data in an appropriate way. If logging a message would be helpful, then please do that (and if RFC-154 is adopted, a log will be available). One way to reproduce this is to run `tests/testProcessCcd.py` in `pipe_tasks`. However, I often see it when running `processCcd.py` on other data, as well.
| 2 |
1,057 |
DM-5431
|
03/11/2016 14:51:34
|
Changes to galaxy_shear_experiments Python code
|
This ticket describes changes which were made to the test runner and analysis scripts during the Dec 2015 - Feb 2016 period. Most of these changes were made as a part of moving to a large computing cluster, where both the units of work and the output file organization had to be changed to make parallelization possible. The large number of tests run during this period and the need to more efficiently analyze and compare also introduced some changed to the analysis and plot modules. Since these changes do not pertain to any single test (though many were done during Dm-1136), I have put them on a separate ticket.
| 5 |
1,058 |
DM-5435
|
03/13/2016 14:27:25
|
Provide a shared stack on lsst-dev & other relevant systems
|
Following the discussion in RFC-156, ensure that a documented, fast, easy to initialize shared stack is available for developers to use on shared systems, certainly to include {{lsst-dev}}.
| 3 |
1,059 |
DM-5447
|
03/14/2016 16:15:19
|
Write technical note describing galaxy shear fitting experiments
|
Through S15 (DM-1108) and W16 (DM-3561), [~pgee] has conducted a large-scale investigation into galaxy shear fitting. Please summarize the motivation, methodology and results of this study as a [technical note|http://sqr-000.lsst.io/en/master/].
| 8 |
1,060 |
DM-5448
|
03/14/2016 16:22:50
|
Familiarization with ngmix codebase
|
Download the ngmix codebase from https://github.com/esheldon/ngmix. Install it and its dependencies in the same environment as the LSST stack. Experiment with using it and understanding how it works
| 3 |
1,061 |
DM-5449
|
03/14/2016 16:34:37
|
Convert GWT code to pure JavaScript (F16)
|
The remaining work for converting GWT code to pure JavaScript
| 100 |
1,062 |
DM-5463
|
03/15/2016 15:39:43
|
Don't restore the mask in CharacterizeImageTask.characterize
|
CharacterizeImageTask.characterize presently restores the mask from a deep copy for each iteration of the loop to compute PSF. This is unnecessary because repair and detection both clear the relevant mask planes before setting new values.
| 1 |
1,063 |
DM-5472
|
03/16/2016 05:47:26
|
Update meas_mosaic for compatibility with new single frame processing
|
Following [recent changes to single frame processing|https://community.lsst.org/t/backward-incompatible-changes-to-processccdtask-and-subtasks/581], {{icSrc}} no longer includes celestial coordinates and {{icMatch}} is no longer being written. {{meas_mosaic}} requires this information. Provide a work-around.
| 3 |
1,064 |
DM-5473
|
03/16/2016 07:30:59
|
Jenkins/ci_hsc failure: 'base_PixelFlags_flag_clipped' already present in schema
|
Since 15 March, the {{ci_hsc}} build in Jenkins has been failing as follows: {code} [2016-03-16T14:23:13.548928Z] Traceback (most recent call last): [2016-03-16T14:23:13.548956Z] File "/home/build0/lsstsw/stack/Linux64/pipe_tasks/2016_01.0-23-gcf99090/bin/measureCoaddSources.py", line 3, in <module> [2016-03-16T14:23:13.548969Z] MeasureMergedCoaddSourcesTask.parseAndRun() [2016-03-16T14:23:13.548999Z] File "/home/build0/lsstsw/stack/Linux64/pipe_base/2016_01.0-6-g7751869/python/lsst/pipe/base/cmdLineTask.py", line 450, in parseAndRun [2016-03-16T14:23:13.549011Z] resultList = taskRunner.run(parsedCmd) [2016-03-16T14:23:13.549040Z] File "/home/build0/lsstsw/stack/Linux64/pipe_base/2016_01.0-6-g7751869/python/lsst/pipe/base/cmdLineTask.py", line 192, in run [2016-03-16T14:23:13.549048Z] if self.precall(parsedCmd): [2016-03-16T14:23:13.549076Z] File "/home/build0/lsstsw/stack/Linux64/pipe_base/2016_01.0-6-g7751869/python/lsst/pipe/base/cmdLineTask.py", line 279, in precall [2016-03-16T14:23:13.549087Z] task = self.makeTask(parsedCmd=parsedCmd) [2016-03-16T14:23:13.549115Z] File "/home/build0/lsstsw/stack/Linux64/pipe_base/2016_01.0-6-g7751869/python/lsst/pipe/base/cmdLineTask.py", line 369, in makeTask [2016-03-16T14:23:13.549132Z] return self.TaskClass(config=self.config, log=self.log, butler=butler) [2016-03-16T14:23:13.549160Z] File "/home/build0/lsstsw/stack/Linux64/pipe_tasks/2016_01.0-23-gcf99090/python/lsst/pipe/tasks/multiBand.py", line 1008, in __init__ [2016-03-16T14:23:13.549179Z] self.makeSubtask("measurement", schema=self.schema, algMetadata=self.algMetadata) [2016-03-16T14:23:13.549206Z] File "/home/build0/lsstsw/stack/Linux64/pipe_base/2016_01.0-6-g7751869/python/lsst/pipe/base/task.py", line 226, in makeSubtask [2016-03-16T14:23:13.549846Z] subtask = configurableField.apply(name=name, parentTask=self, **keyArgs) [2016-03-16T14:23:13.549901Z] File "/home/build0/lsstsw/stack/Linux64/pex_config/2016_01.0+1/python/lsst/pex/config/configurableField.py", line 77, in apply [2016-03-16T14:23:13.549915Z] return self.target(*args, config=self.value, **kw) [2016-03-16T14:23:13.549943Z] File "/home/build0/lsstsw/stack/Linux64/meas_base/2016_01.0-12-gf26bc28+1/python/lsst/meas/base/sfm.py", line 248, in __init__ [2016-03-16T14:23:13.549954Z] self.initializePlugins(schema=self.schema) [2016-03-16T14:23:13.549985Z] File "/home/build0/lsstsw/stack/Linux64/meas_base/2016_01.0-12-gf26bc28+1/python/lsst/meas/base/baseMeasurement.py", line 298, in initializePlugins [2016-03-16T14:23:13.550004Z] self.plugins[name] = PluginClass(config, name, metadata=self.algMetadata, **kwds) [2016-03-16T14:23:13.550032Z] File "/home/build0/lsstsw/stack/Linux64/meas_base/2016_01.0-12-gf26bc28+1/python/lsst/meas/base/wrappers.py", line 15, in __init__ [2016-03-16T14:23:13.550616Z] self.cpp = self.factory(config, name, schema, metadata) [2016-03-16T14:23:13.550647Z] File "/home/build0/lsstsw/stack/Linux64/meas_base/2016_01.0-12-gf26bc28+1/python/lsst/meas/base/wrappers.py", line 223, in factory [2016-03-16T14:23:13.550660Z] return AlgClass(config.makeControl(), name, schema) [2016-03-16T14:23:13.550688Z] File "/home/build0/lsstsw/stack/Linux64/meas_base/2016_01.0-12-gf26bc28+1/python/lsst/meas/base/baseLib.py", line 3401, in __init__ [2016-03-16T14:23:13.552891Z] this = _baseLib.new_PixelFlagsAlgorithm(*args) [2016-03-16T14:23:13.552924Z] lsst.pex.exceptions.wrappers.InvalidParameterError: [2016-03-16T14:23:13.552967Z] File "src/table/Schema.cc", line 563, in lsst::afw::table::Key<lsst::afw::table::Flag> lsst::afw::table::detail::SchemaImpl::addField(const lsst::afw::table::Field<lsst::afw::table::Flag>&, bool) [2016-03-16T14:23:13.552986Z] Field with name 'base_PixelFlags_flag_clipped' already present in schema. {0} [2016-03-16T14:23:13.553012Z] lsst::pex::exceptions::InvalidParameterError: 'Field with name 'base_PixelFlags_flag_clipped' already present in schema.' [2016-03-16T14:23:13.553014Z] [2016-03-16T14:23:13.613484Z] scons: *** [.scons/measure] Error 1 [2016-03-16T14:23:13.617577Z] scons: building terminated because of errors. {code} Please fix it.
| 1 |
1,065 |
DM-5474
|
03/16/2016 10:37:43
|
Bugs in obs_subaru found by PyFlakes
|
I ran pyflakes on the code in obs_subaru and found a few bugs (beyond a few trivial ones that I am fixing as part of DM-5462) {{ingest.py}} has undefined name {{day0}} {{ccdTesting.py}} has at least three undefined variables: {{x}}, {{y}} and {{vig}} in the following: {code} ngood += pupilImage[y[good], x[good]].sum() vig[i] = float(ngood) {code} {{crosstalkYagi.py}} has many undefined names, starting with {{makeList}}, {{estimateCoeffs}}
| 1 |
1,066 |
DM-5478
|
03/16/2016 12:35:13
|
Write script to derive and collate QA metrics from data repository of processed data
|
I wrote a python script using stack components to derive QA metrics and collate other QA-relevant information for a data repository of processed data. This is currently output to a CSV file that can be loaded into a SQL database.
| 20 |
1,067 |
DM-5479
|
03/16/2016 12:37:07
|
Wrote script to print the names of all visits that overlap a patch
|
In order to finish the IDL workflow module for makeCoaddTempExp I needed a program to say which visits overlap a given path. That's what this script does.
| 5 |
1,068 |
DM-5480
|
03/16/2016 12:40:18
|
Processing of COSMOS data - Part II
|
Continued work on processing and QA work on the COSMOS verification dataset. Running processCcDecam, making diagnostic plots, and nvestigating the results. Most recently I've reprocessed the COSMOS data through processCcdDecam using SDSS as the astrometric and photometric reference catalog and am redoing the QA work on those results.
| 20 |
1,069 |
DM-5482
|
03/16/2016 12:45:20
|
Write presentation on verification datasets for AAS
|
Prepared and gave a talk at the NSF booth at the Florida AAS meeting on the progress of the verification datasets effort.
| 5 |
1,070 |
DM-5483
|
03/16/2016 12:47:11
|
Work on script to test the astrometric matcher
|
We encouraged astrometric matching problems for the Bulge verification dataset. Therefore, I wrote a script that tests the matcher by systematically shifting the coordinates of one sets of the data to see if the matcher still works. It worked well until ~80 arcsec.
| 5 |
1,071 |
DM-5484
|
03/16/2016 12:48:05
|
SdssMapper.paf has wrong python type for processCcd_config
|
[~npease] reports that {{Sdssmapper.paf}} has the wrong python data type for the dataset {{processCcd_config}}: it is {{lsst.obs.sdss.processCcdSdss.ProcessCcdSdssConfig}} instead of {{lsst.pipe.tasks.processCcd.ProcessCcdConfig}}
| 0.5 |
1,072 |
DM-5485
|
03/16/2016 12:48:48
|
Work on plan to test specific algorithmic components of the stack
|
After working on a script to test the astrometric matcher, I decided to put together a plan to run similar tests on our algorithmic code. The rough plan is here: https://confluence.lsstcorp.org/display/SQRE/Stack+Testing+Plan
| 2 |
1,073 |
DM-5486
|
03/16/2016 12:51:15
|
Work on putting together page of "tips and tricks for using the stack"
|
Due to the incomplete state of the stack documentation and tutorials, I decided to write down various "tips and tricks" for using the stack as I learn them. https://confluence.lsstcorp.org/display/SQRE/Tips+and+Tricks+for+using+the+Stack
| 2 |
1,074 |
DM-5487
|
03/16/2016 14:34:54
|
Revise operations concept for Observation Processing System
|
Turn the L1 ConOps document into appropriate sections of LDM-230, specifying automated operations sequences, how human intervention can occur, and processes to handle changes and updates. (Story points are for KTL drafting and initial contributions)
| 2 |
1,075 |
DM-5488
|
03/16/2016 14:36:42
|
Field group updates
|
After some work we have realized that the following needs to be done to field groups: * Tabs group should have a field group smart wrapper component * field group needs to reinit on id change * remove mixin, use Higher-Order Components instead * support a function for a value, this function will return a value or a promise * hidden fields - init field group with key/value object * Sub-field groups? study only, unless it is easy to implement. * maintain an option to keep unmount field value available * determine if InitValue needs to be passed around * passing fieldState around too much * find reason for react warning every time popup is raised * look at promise code make sure it is working the way we think * if practical, remove all export default FieldGroupConnector. It is the high order component that replaces the mixin. FieldGroupUtils.js: (~line 33): The field value would be a function on the file upload case. Therefore the upload does not activate until validation. In the upload case the function would return a promise. However, It could return a value or an object with a value and a valid status. Now the value key of a field can contain a promise or function or primitive. The function can return a primitive, a promise, or an object with primitive and status. fftools.js lines 102-158 you can see my experimenting with taking out the connector. It works fine and does eliminate one of the warning messages.
| 8 |
1,076 |
DM-5489
|
03/16/2016 14:37:23
|
improvement of the north/east arrow on image
|
make the compass sticky when scroll the image
| 1 |
1,077 |
DM-5490
|
03/16/2016 14:38:54
|
Develop operations concept for Batch Processing System
|
Develop a ConOps document that can be included as appropriate sections of LDM-230 describing the batch processing environment, specifying automated operations sequences, how human intervention can occur, and processes to handle changes and updates. (Story points are for KTL drafting and initial contributions)
| 3 |
1,078 |
DM-5491
|
03/16/2016 14:39:35
|
Develop operations concept for Data Backbone
|
Develop a ConOps document that can be included as appropriate sections of LDM-230 describing the Data Backbone that contains, manages, and provides access to the Science Data Archive, specifying automated operations sequences, how human intervention can occur, and processes to handle changes and updates. (Story points are for KTL drafting and initial contributions)
| 3 |
1,079 |
DM-5492
|
03/16/2016 14:40:35
|
Develop operations concept for Data Access Processing System
|
Develop a ConOps document that can be included as appropriate sections of LDM-230 describing the Data Access Processing System that manages L3 computing in and interfaces to the Data Access Center, specifying automated operations sequences, how human intervention can occur, and processes to handle changes and updates. (Story points are for KTL drafting and initial contributions)
| 3 |
1,080 |
DM-5493
|
03/16/2016 14:47:26
|
Develop functional breakdown for Observation Processing System
|
Write sections that can be incorporated into LDM-148 describing the functional breakdown of the Observation Processing System, including, for each major element: * overall function * inputs, outputs, and control interfaces * components used * descriptions of functions to be performed (Story points are for KTL drafting and initial contributions)
| 3 |
1,081 |
DM-5494
|
03/16/2016 14:47:51
|
Develop functional breakdown for Batch Processing System
|
Write sections that can be incorporated into LDM-148 describing the functional breakdown of the Batch Processing System, including, for each major element: * overall function * inputs, outputs, and control interfaces * components used * descriptions of functions to be performed (Story points are for KTL drafting and initial contributions)
| 2 |
1,082 |
DM-5495
|
03/16/2016 14:48:13
|
Develop functional breakdown for Data Backbone
|
Write sections that can be incorporated into LDM-148 describing the functional breakdown of the Data Backbone, including, for each major element: * overall function * inputs, outputs, and control interfaces * components used * descriptions of functions to be performed (Story points are for KTL drafting and initial contributions)
| 2 |
1,083 |
DM-5496
|
03/16/2016 14:48:41
|
Develop functional breakdown for Data Access Center Processing System
|
Write sections that can be incorporated into LDM-148 describing the functional breakdown of the Data Access Center Processing System, including, for each major element: * overall function * inputs, outputs, and control interfaces * components used * descriptions of functions to be performed (Story points are for KTL drafting and initial contributions)
| 2 |
1,084 |
DM-5498
|
03/16/2016 15:24:44
|
Coordinate completion of operations concepts
|
Coordinate the creation of a new version of LDM-230 incorporating DPS-WG-generated operations concepts.
| 2 |
1,085 |
DM-5499
|
03/16/2016 15:25:35
|
Coordinate completion of functional breakdowns
|
Coordinate the creation of a new version of LDM-148 incorporating DPS-WG-generated functional breakdowns.
| 2 |
1,086 |
DM-5501
|
03/16/2016 15:42:57
|
Solve the metadata sanitization problem
|
Applications need access to visit specific metadata: e.g. pointing, airmass, exposure length. This information is typically carried around in a FITS header, but there are no conventions on spelling or even necessarily units of these metadata key, value pairs. There needs to be a easy to use metadata sanitization process that allows data from many different systems to present a standardized interface to observation metadata to the algorithm code.
| 100 |
1,087 |
DM-5502
|
03/16/2016 15:47:20
|
Collect usage of header metadata
|
Collect a comprehensive set of exposure oriented metadata used by science code. This should also include metadata that is not currently needed but that could be utilized in the future. In practice, I suspect this will involve looking for all calls to PropertySet.get since that is how FITS header metadata is currently passed around.
| 5 |
1,088 |
DM-5515
|
03/17/2016 00:48:50
|
prepare Slack RFC
| ERROR: type should be string, got " https://jira.lsstcorp.org/browse/RFC-140" | 1 |
1,089 |
DM-5530
|
03/17/2016 11:48:24
|
Documentation of Firefly functions and API (F16)
|
We are concentrating on the coding in X16. This epic will be capture the effort to write the document for using Firefly functions and API.
| 40 |
1,090 |
DM-5542
|
03/17/2016 14:33:15
|
AFW rgb.py has undefined variable that breaks a test in some situations
|
The {{rgb.py}} test is failing for me with current AFW master: {code} tests/rgb.py .E............ ====================================================================== ERROR: testMakeRGBResize (__main__.RgbTestCase) Test the function that does it all, including rescaling ---------------------------------------------------------------------- Traceback (most recent call last): File "tests/rgb.py", line 313, in testMakeRGBResize with Tempfile(fileName, remove=True): NameError: global name 'Tempfile' is not defined ---------------------------------------------------------------------- Ran 16 tests in 7.296s FAILED (errors=1) {code} {{Tempfile}} is definitely only used in line 313. It was introduced with commit c9864f49. I'm not entirely sure how this is not picked up by Jenkins as the test will run if matplotlib and scipy are installed and Jenkins does have those.
| 0.5 |
1,091 |
DM-5552
|
03/17/2016 15:18:14
|
Add renderer option to js table
|
TablePanel and BasicTable now accept optional renderers. For each column, you can set a custom renderer for the header, cell, or both. Also, created several commonly used renderer for images, links, and input field.
| 2 |
1,092 |
DM-5553
|
03/17/2016 15:36:05
|
Z-scale stretch for image display
|
The z-scale stretch in current system is different from the one in OPS
| 8 |
1,093 |
DM-5560
|
03/18/2016 13:29:55
|
Participate in October 2015 OCS-subsystems teleconference
|
Prepare for, attend, and follow up on the OCS-subsystems teleconference on October 8, 2015.
| 2 |
1,094 |
DM-5563
|
03/18/2016 13:43:09
|
Participate in November 2015 OCS-subsystems teleconference (LSE-74)
|
Prepare for, attend, and follow up on the OCS-subsystems teleconference on November 11, 2015. This story covers work related to LSE-74; LSE-70 and LSE-209 work was also done under a separate epic.
| 1 |
1,095 |
DM-5564
|
03/18/2016 13:57:43
|
Participate in December 2015 OCS-subsystems teleconference (LSE-70, LSE-209)
|
Prepare for, attend, and follow up on the OCS-subsystems teleconference on December 9, 2015. This story covers work related to LSE-70 and LSE-209; LSE-74 work was also done under a separate epic.
| 2 |
1,096 |
DM-5565
|
03/18/2016 14:01:43
|
Participate in December 2015 OCS-subsystems teleconference (LSE-74)
|
Prepare for, attend, and follow up on the OCS-subsystems teleconference on December 9, 2015. This story covers work related to LSE-74; LSE-70 and LSE-209 work was also done under a separate epic.
| 1 |
1,097 |
DM-5566
|
03/18/2016 14:16:47
|
Review of LSE-70 and LSE-209 drafts, September 2015
|
Arrange, prepare for, and attend a joint call with the Camera team to review the end-of-summer-2015 drafts of LSE-70 and LSE-209 from the OCS group.
| 3 |
1,098 |
DM-5567
|
03/18/2016 14:25:26
|
CCB review of LCR-567 (LSE-70) and LCR-568 (LSE-209)
|
Review the LSE-70 and LSE-209 drafts submitted with change requests LCR-567 and LCR-568 in January 2016.
| 2 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.