udaykiran19491/user-stories-from-tawos-for-llm-fine-tuning huggingface dataset:
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "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."
Answer: 51575.0

User story: "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."
Answer: 40274.0

User story: 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
Answer: 18647.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "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  "
Answer: 44567.0

User story: "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  "
Answer: 18518.0

User story: "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  "
Answer: 18702.0

User story: "We identified in DM-5162 a few changesets that still need to be ported from HSC to LSST:    * bf5f753133ae4b41357f9789ff4763949ebb6ffb: FitPsf: reduce outerOrder to 1  * a54d6cbd41baf916fac2a1bb235a8502af14edfd: Provide explicit instantiations for the sake of clang 6.0 on os/x 10.9  * a53ac9e5cdb678a3f8ef633110d7d4cc5ac84f15: FitProfileAlgorithm: bail if the PSF flux failed  "
Answer: 21582.0

User story: "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."
Answer: 43382.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "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"
Answer: 14372.0

User story: "We identified in DM-5162 several changesets that still need to be ported from HSC to LSST:    * 1293a31c19c238ba2c2acd8f67ec1be742764b66: BinnedWcs  * 9f392b134502f6e4fbbd8759806b15f89a267e5a: detection: additional debugging plots for background  * ad74fe8595ec523d6269e36ec2db051534bf3e9a: Add initial.flags.pixel.interpolated.any to ObjectSizeStarSelectorConfig.badFlags  * 69f5db0eba69225cff917fa4c96a94dc8b765aa0, 4a0d59e191fc40d3091b56b20cf27ede4e0c23ab: Check for bad PSF measurements (HSC-1153)  * a54b1ac52678025d3317e8a379c2849d3eb567ba: pcaPsfDeterminer: catch case of no good PSF candidates in debugging  * c4fcab3251e6f41da2248d63fdf28c0bf80e30f8: Indent seems to be wrong for debug display  * 2a889c17d47c879dbb4345bafba6aed9869b5984, f3e42cc03ab8a4f1b28d9e0852619cbdbf3b7018: Make IdSpanCompar more deterministic  * f99eb46f484609673b45290eaaba47688d7b4a24: CR code has to take care of 'NO_DATA' mask  * 6f6b786bce8ca34bf4c67f75f965130dea027147: Handle small numbers of psfCandidates (HSC-1176)  * d744e6514feaf67b87068ac502bca677306f9fc2: tests: add test for MeasureApCorrTask  * 65f617089038fe19179fca4f959bf23ea061a6b8, 1b7e3cc48ed347b0afa31e81c821b38f87d18d64: Test case for measurement of negative objects    There are also a couple of issues that were identified in the DM-5162 review:  * Delete tests/config/MeasureSources.py --- mere configuration, old-style measurement  * testPsfDetermination has method 'xtestRejectBlends'"
Answer: 23065.0

User story: "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  "
Answer: 18642.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "We identified in DM-5162 several changesets that still need to be ported from HSC to LSST:    * 2c12255372bde846ba0429b5b542960e57d169f0, 0aec617e0ea604cde85105de3dade279a4fe10df: Footprint::overlapsMask  * 76f3706f6688b23d5b0c71e66af3e94095a9f821: copyWithinFootprint: respect image size  * f49676d7f1348f9de8ca21ee633e0c25473251ae: Implemented Linear and ZScale transformations, HSC-1206, 08a7740ed756ee7b2c845b4ce6aed8d9a0f50d04  * c369a8ad53962aba950f7710210be4b23f45a523: utils: make Mosaic.nImage a property  * Maybe 0a2647a4f57addc3b3adb347da995fa0d36b43cb: Add display.utils function to plot the bboxes of inputs to a coadd in ds9  * 386a4b71d974d9e5672fe8690d0db3e56c9fb40f: Box2?.getCorners  * f3d3029c561b957069cbf280b62ea8e37447c068: Calib: add operator*= for scaling zeropoint  * 6c1845474f28f528a95190eeb88f095b11999078: Check in #3092 (iterable coord) directly on master  * f3d3029c561b957069cbf280b62ea8e37447c068: Calib: add operator*= for scaling zeropoint  * 5d1934cc9fe7d8c43aa8f9318a1ac9a3ce85e94e, 0d1ab12db604d5e42a5d72f028411a64294283ce: Footprint merging  * b8578746d69920bc1e1089cca4b4acb230f0e8d5: Interpolate: add support for ndarray  * 3de3339aa075f869d73a5bc66fc65dbee8ae3d16: Fix unit test fallout from Interpolate std::vector change  * 08a7740ed756ee7b2c845b4ce6aed8d9a0f50d04, f73544e15abd2760bf84794798cf4b84e97e938d: Added xSize, ySize, and rescaleFactor arguments to {make,write}RGB; HSC-1207  * 88d838b74898d9572bbc8c46121da029958c1c72: rgb: fix makeRGB so it can replace saturated pixels and produce an image  * 254d7248ea20d98de481d968f6503d1610b16ae7: Remove tests of writing rgb images to jpeg and tiff  * 3252a40ad55222b882acf14d2f7cf0f3fe80f585: Added MatchControl and implemented it for matchXY and MatchRaDec  * 81c6063a32883b748f3770b7124d74ced7b480f5: Implement and test includeMismatches option in MatchControl object  * fd4c0baec617155fac0816607a5acba88e8970f5: Add support for renaming without replacing the full field in SchemaMapper  * 79337bb6d1ee3a0b73bcd2b2d0ca506a44d3fa56: Handle empty Footprints when normalising  "
Answer: 18694.0

User story: "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. "
Answer: 1925.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: The following packages need to be reviewed and maybe upgraded.      "babel"     : "5.8.34",                           6.5.2 (M)      "history"   : "1.17.0",                           2.0.0 (M)      "icepick"   : "0.2.0",                            1.1.0 (M)                "react-highcharts": "5.0.6",                      7.0.0 (M)      "react-redux": "3.1.2",                           4.4.0 (M)      "react-split-pane": "0.1.22",                     2.0.1 (M)      "redux-thunk": "0.1.0",                           1.0.3 (M)      "redux-logger": "1.0.9",                          2.6.1 (M)      "validator" : "4.5.0",                            5.1.0 (M)      "chai": "^2.3.0",                                 3.5.0 (M)      "esprima-fb": "^14001.1.0-dev-harmony-fb",        15001.1001.0-dev-harmony-fb (M)      "babel-eslint"      : "^4.1.3",                   5.0.0 (M)      "babel-loader"      : "^5.3.2",                   6.2.4 (M)      "babel-plugin-react-transform": "^1.1.0",         2.0.0 (M)      "babel-runtime"     : "^5.8.20",                  6.6.0 (M)      "eslint"            : "^1.10.3",                  2.2.0 (M)      "eslint-config-airbnb": "0.1.0",                  6.0.2 (M) works with eslint 2.2.0      "eslint-plugin-react": "^3.5.1",                  4.1.0 (M)  works with eslint 2.2.0      "extract-text-webpack-plugin": "^0.8.0",          1.0.1 (M)      "html-webpack-plugin": "^1.6.1",                  2.9.0 (M)      "karma-sinon-chai": "^0.3.0",                     1.2.0 (M)      "redux-devtools"    : "^2.1.2",                   3.3.1 (M)      "webpack": "^1.8.2"                               1.12.14, 2.1.0 beta4 (M)      As of 9/6/2016, the content of dependencies in package.json is listed below:            "babel-core": "6.14.0",        "babel-loader"      : "6.2.5",        "babel-polyfill"    : "6.13.0 ",        "babel-preset-es2015": "6.14.0",        "babel-preset-react": "6.11.1",        "babel-preset-stage-2": "6.13.0",        "babel-runtime"     : "6.9.2",        "babel-plugin-react-transform": "2.0.2",        "enum": "2.3.0",        "fixed-data-table": "0.6.3",        "isomorphic-fetch": "2.2.1",        "local-storage": "1.4.2",        "lodash": "4.6.1",        "numeral": "1.5.3",        "react": "15.3.1",        "react-dom": "15.3.1",        "react-addons-pure-render-mixin": "15.3.1",        "react-addons-shallow-compare": "15.3.1",        "react-addons-update": "15.3.1",        "react-addons-perf" : "15.3.1",        "react-component-resizable": "1.0.1",        "react-grid-layout": "0.13.3",        "react-highcharts": "10.0.0",        "react-split-pane": "0.1.44",        "redux": "3.5.2",        "redux-thunk": "2.1.0",        "redux-logger": "2.6.1",        "redux-saga": "0.11.1",        "underscore.string": "3.2.3",        "uniq": "1.0.1",        "validator": "4.5.0",        "whatwg-fetch": "0.10.1",        "react-color": "2.2.6",        "shallowequal": "0.2.2"     
Answer: 272899.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "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?"
Answer: 12633.0

User story: "Allow to filter in a selected area from XY Plot."
Answer: 5491.0

User story: "Moving meas_simastrom from lsst_france/ to lsst/ also resulted in a name change per RFC-123, and a namespace flattening: it's not derived from meas; it's a task. This is the necessary first step in getting it integrated into the stack."
Answer: 11857.0

User story: "{{obs_subaru}}'s {{policy/SuprimecamMapper.paf}} contains a number of entries that look wrong (e.g. {{deep_forcedPhotCoadd_metadata}} should be {{deepCoadd_forced_config}}) or do not apply to LSST (e.g. {{stack_config}}) and doesn't contain a number of entries that might be expected (e.g. {{transformed_src}}).    Please ensure that this file is updated to comply with current expectations."
Answer: 1957727.0

User story: "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 [~<USER> also see the bias jump features in other CCDs.  It would make more sense to turn it on for all CCDs by default. "
Answer: 1188.0

User story: "Per RFC-145, let's go through the stories in DM and assign Team to each of them. To see these stories, you can use https://jira.lsstcorp.org/issues/?filter=14106    I am expecting each tcam to go through the list and deal with stories that fall into your wbs.     (you might want to sort by reported or assignee to quickly identify most of them)"
Answer: 153140.0

User story: "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. [~<USER> suggests (and I agree) that brightness should be based on signal to noise ratio, thus making the astrometry histogram independent of photometric calibration.  "
Answer: 35972.0

User story: "Add a linear background gradient fit to the integrated pre-subtraction and dipole fitter (for testing).  This will eventually be implemented in the measurement plugin."
Answer: 10229.0

User story: "The DRP meta-epics currently have associated time estimates that are used for resource loading. Please extract them and ensure they are recorded elsewhere."
Answer: 145125.0

User story: "Each tcam should have a resource loaded plan, ready to load to PMCS by 3/10"
Answer: 154210.0

User story: "Summer --> Fall, Winter --> Sprint, add X16"
Answer: 146993.0

User story: "We need a list of who works for DM, % of time, and role for each person."
Answer: 14535.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "It would be extremely useful to have a developer OSX bootstrapping guide starting from a bare OSX image.  Covering cli based Xcode installation, home brew packages, etc. that can be essentially cut'n'pasted."
Answer: 1862340.0

User story: "1. Add pass/fail routine to report success/fail against metrics.  Do this for    * SRD  (/)    * Configured metrics  (/)    2. Add pass/fail reporting to running of `validate.drp.run`  (/)"
Answer: 52244.0

User story: "This aims at preparing integration of this procedure inside Jenkins CI"
Answer: 30949.0

User story: "There is a request to provision ls.st short links for Technotes. E.g. ls.lst/sqr-000 links to sqr-000.lsst.io."
Answer: 244760.0

User story: "Configuration on the worker is done by setting environment variables in a script, which is lacking in flexibility, but there is a question of if it is worth changing to some form of text configuration file. The code that reads the configuration could be improved in either case."
Answer: 96312.0

User story: "As a follow-on to DM-4315, deploy the new [Maria DB GSSAPI Authentication Plugin|https://mariadb.com/kb/en/mariadb/gssapi-authentication-plugin/] in the IAM testbed for Kerberos ticket-based authentication, to provide single sign-on access."
Answer: 14698.0

User story: 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}}.
Answer: 8977.0

User story: "AstroUtils.cc has code for loading USNO catalog which is used by Associations:CollectRefStars to build a reference list. We should replace this with  LoadReferenceObjectsTask from meas_algorithms to both make it more generic, and to remove problematic endian handling in AstroUtils."
Answer: 512353.0

User story: "Most of this is done.  I just need to plot a few 3 color images and work out the bugs."
Answer: 14478.0

User story: "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."
Answer: 427.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "drawing overlay 3 Color Support"
Answer: 24714.0

User story: "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 [~<USER>'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."
Answer: 120701.0

User story: 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?
Answer: 1136135.0

User story: "Now that XML is being generated by doxygen (DM-4900) we need to prevent developers from accidentally committing the generated XML. This ticket will systematically go through all stack packages and add `doc/xml/` to .gitignore files."
Answer: 2396634.0

User story: "ltd-keeper should be deployed as a Docker container as a best practice for maintainable cloud microservices.    This involves writing a Dockerfile committed to the ltd-keeper repo and demonstrating that the container can be stood up on Google Container Engine.    I plan on use data-containers attached to the service’s container to maintain the sqlite DB. This ticket should document how to operate ltd-keeper and apply updates to both the ltd-keeper app *and* DB migrations..    This ticket also involves initial overhead in researching Docker/Kubernetes."
Answer: 79889.0

User story: "attend the bi-weekly meeting authentication and authorization discussion. provide input and feedback to IAM. "
Answer: 18363.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "The python interface needs to be ported.  This involves the following:    * Modify FireflyClient.py  * Change all the API to work by dispatching remote actions. There is currently a dispatchRemoteAction method in  FireflyClient.py  * On the server side clean up file PushCommands.java, PushJob.java and ServerParams to remove the old api.  * Move the fftools/python to firefly/python  * clean up the test notebooks.  There are currently several, some don't work and should be removed.  Others should be clean test cases.  * Make sure the python support for RangeValues is consistent with the Java and JavaScript. I suspect it is not.  * Make sure events can be received into the python.    *API functions:*  * FireflyClient: class to use dispatch Firefly actions remotely  * Public functions provided by FireflyClient (1-13: general usage, 14-26: dispatch actions usage)  # add_listener  # remove_listener  # launch_browser  # wait_for_events  # get_firefly_url  # stay_connected  # disconnect  # upload_file  # upload_fits_data  # upload_text_data  # upload_data  # dispatch_remote_action  # dispatch_remote_action_by_post  # show_fits  # show_table  # show_xyplot  # add_extension  # set_zoom  # set_pan  # set_stretch  # overlay_region_layer  # delete_region_layer  # add_region_data  # remove_region_data  # add_mask  # remove_mask"
Answer: 247086.0

User story: "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}"
Answer: 75368.0

User story: "* Write a button on the toolbar that monitors the active plot view's group and shows the locked or unlocked icons  * Add an action and reducer functions the will toggle the lock state of the group."
Answer: 107653.0

User story: "We need to help system like we have in GWT."
Answer: 15537.0

User story: "Some tables int the integration tests need to be flagged as needing to be locked in memory and given a scan rating."
Answer: 11952.0

User story: "To record the changes made to W16 and S16 epics and stories.    2/17/2016  Moved the following epics to F16:        DM-3594,  DM-3604,     2/18/2016  Moved the following epics to X16:       DM-3625 DM-3647    2/18/2016  Moved the following stories to F16:      DM-2783,     2/17/2016  Moved the following stories to F16 (nov. 2016)       DM-3643    TODO:   check with Kevin when epic 4681 is closed re. epic 3594. "
Answer: 464985.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Using Fastly’s API, have ltd-keeper setup new builds and editions:    - Add {{Surrogate-Key}} to headers of objects uploaded to S3 (happens on ltd-mason side)  - Configure Varnish to serve specific bucket directories as specific domains (DM-4951 has added Route 53 interactions to ltd-keeper)  - Purge content when editions switch or content is deleted.    DM-5167 is covering non-API driven work to configure fastly.    See https://www.hashicorp.com/blog/serving-static-sites-with-fastly.html for a write-up on serving static site via fastly. See also http://sqr-006.lsst.io for an overview of LSST the Docs."
Answer: 112372.0

User story: "LSST the Docs will use Fastly to serve docs out of an S3 bucket with well-formatted URLs thanks to routing at the Varnish layer. See https://www.hashicorp.com/blog/serving-static-sites-with-fastly.html for an overview of the desired setup and http://sqr-006.lsst.io for an overview of LSST the Docs. Specific outcomes are:    * Create S3 bucket for LTD  * Create Fastly account (may be a demo account pending negotiations with Fastly)  * Basic configurations for Fastly account  * Research pricing/configure a TLS certificate for *.lsst.io domains  * Set up base VCL configuration on Fastly.  "
Answer: 102081.0

User story: "Analyze the QA CmdLineTask collection being generated by [~<USER> sufficiently well to determine the interface requirements needed to represent them as Supertasks.    Does not include actually designing that interface."
Answer: 42894.0

User story: "Each of the visualizers needs to expand to full screen.  We need to modify our current layout system so each and expand and collapse so that the old view is restored. The system needs to be flexible enough so an 'expanded version' of the component can be used."
Answer: 29331.0

User story: "We've already merged a lot of code from HSC to LSST, and are optimistic that we've captured most of the big ticket items. However, we need to perform a thorough comparison of the codebases to check there's nothing we're missing. Please do that, and file tickets in the DM-3560 and DM-3568 epics to describe outstanding work."
Answer: 33032.0

User story: "{{lsst.utils.tests.MemoryTestCase}} is used extensively throughout our test suite, but it is lacking in documentation and it's not clear under what circumstances its use is required or encouraged. Please add appropriate documentation to the [Software Unit Test Policy |http://developer.lsst.io/en/latest/coding/unit_test_policy.html].    See also [this thread on clo|https://community.lsst.org/t/what-is-the-policy-for-using-lsst-utils-tests-memorytestcase]."
Answer: 115739.0

User story: "Local LSST meetings, postdoc meetings, NCSA All hand meetings, RFDs, NCSA software meeting, astronomy events, workshops, travel to JTM, other local meetings. "
Answer: 21521.0

User story: "Ramp up with the middleware status and development. Look into packages pipe_base, pex_config, pex_logging. "
Answer: 21518.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Process some DECam data to gain familiarity with process execution and learn to debug issues"
Answer: 21508.0

User story: "verification dataset meetings"
Answer: 21504.0

User story: "DM3733,DM4825"
Answer: 20731.0

User story: "Create a single file where tests for validating source can be added. The tests will be duck typed to a class method and be registered to the corresponding validation class with a decorator."
Answer: 417427.0

User story: "Plumbing and/or documentation additions necessary for another SQRE member to use {{packer-newinstall}} to test the {{w_2016_07}} weekly tag for this week and to build the binary products. "
Answer: 34924.0

User story: Re-interpreted ticket:  1. Provide already-initialized repositories in the `validation_data_cfht`, `validation_data_decam`, and `validation_data_hsc` packages alongside the raw data.  The goal is to allow both easy quick-start analyses as well as comparisons of output steps from processCcd.py and friends at each step of the processing. (/)  2. Add (Cfht,Decam,HSC).list files to provide for easy processing of the available dataIds in the example data. (/)  3. Update README files to explain available data.  (/)    [Original request:]  In validation_drp when I run examples/runXTest.sh I find that any data I had saved in CFHT or DECam is lost, even if I have carefully renamed it. This is very dangerous and I lost a lot of work due to it. At a bare minimum please do NOT touch any directories not named "input" or "output".    Lower priority requests that I hope you will consider:  - Have the the input repo be entirely contained in the validation_data_X packages, ready to use "as is". That would simplify the use of those packages by other code. It would also simplify validate_drp, and it would just leave the output repo to generate (which already has a link back to the input repo).  - Have runXTest.sh accept a single argument: the path to the output. (The path to the input is not necessary if you implement the first suggestion).
Answer: 54599.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: When launching a query which require an aggregation/merge, Qserv first creates a result_m table to collect chunk query results and then a result table. On the other hand, for a query which doesn't require a merge, only result table is created.    If merge query was send to mysql-proxy right after query parsing (like it is currently done with "order by" clause only, this would be then generalized to all merge queries), creation of result_m table could be avoided. This would lead to simpler C++ code, and aggregation would be performed at the same time that returning result, which may lead to better performance. Queries wich requires or not aggregation step would be processed exactly the same way on the C++ side (store results of chunk queries), and mysql-proxy would release lock on result table when running aggregation/merge query (here, one can consider that simply concatening results of query would also be a kind of aggregation).    Please not that removal of result_m table would also free some space on master, which is a bottleneck.    [~<USER>, I propose you to plan this interesting feature for next sprint, feel free to postpone it. I think that intersection with "Query coverage" story might not be empty.
Answer: 1770621.0

User story: "Learning DM stack deployment and layout, reading on redesign of butler 1.5"
Answer: 29905.0

User story: "Weeks 1&2 - Interviews, Team mtgs, uptime institute tier discussions: 1.5 pts  Weeks 3&4 - Team mtgs, ICI meetings, set/prioritize IT goals 4 pts"
Answer: 29910.0

User story: "New installation (as of 2/12 -- all the way from newinstall.sh, so it grabs the new eups 2.0.1)  Error is:   {code}  [ewok:~/lsst] lynnej% source loadLSST.csh  DYLD_LIBRARY_PATH: Undefined variable.  setup: Command not found.  {code}  This is new for me. (note that I do not have a DYLD_LIBRARY_PATH variable set before doing loadLSST.csh)  If I do the following:  {code}  [ewok:~/lsst] lynnej% setenv DYLD_LIBRARY_PATH   [ewok:~/lsst] lynnej% source loadLSST.csh  {code}  "
Answer: 131033.0

User story: "We no longer need luaxmlrpc because we run czar inside proxy. We should move it to lsst-dm/legacy-, and remove mentioning it in readme."
Answer: 1820430.0

User story: "Attend the weekly meeting and answer questions as needed.  Help with the Python and JS debug "
Answer: 24714.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: 1. Make sure {{ci_hsc}} is buildable by {{lsstsw}} / {{lsst_build}}  (/)  2. Add {{ci_hsc}} to lsstsw/etc/repos.yaml so that one can request that Jenkins builds it.  (/)  3. Verify that the test in {{ci_hsc}} fails on known broken tags and passes on known successful tags. (/)    No dependencies will be added to {{lsst_sims}} or {{lsst_distib}}.  This is meant to provide the ability to request that Jenkins do these builds and to fail if something has broken them.    This will later be expanded to new packages {{ci_cfht}}, {{ci_decam}}, and {{ci_sim}}.    The key goal is to make sure one hasn't broken obs_ packages in their butler interface or in their processCcd    Additional Notes and Thoughts from HipChat Discussion  [~<USER>  Sounds good to me; we might have an "lsst_ci" top-level metapackage depending on all of them which is what Jenkins would run regularly.     If the goal is to test obs_ packages, then my first instinct would be to put that in the obs_ package.  Longer term goal to test the stack with different precursor datasets.  If this is testing obs_ packages on a slower cadence than the built-in tests, it's OK for that to be a separate package.    [~<USER>  Eventually, I think we need to run a CI dataset for each camera, then run some camera generic tests on each of those, then run some camera-specific tests on each of those.  So we don't want to go too far down a road in which all tests are camera-specific, but maybe we don't have a choice until we have some better unifying framework for them.  I've certainly been putting some checks in {{ci_hsc}} that would be valid for all other cameras, if we had a CI package for them that went through to coadd processing.
Answer: 15941.0

User story: According to the [Developer Guide|http://developer.lsst.io/en/latest/build-ci/new_package.html], when new packages are added to the build "access must be granted to the appropriate teams". It turns out this is important not just for access control but also because it relates the to tagging and release process, so it really does matter.    However, at time of writing we have [nine teams|https://github.com/orgs/lsst/teams] defined, and no obvious guide to what they're for or which are "appropriate" for what (we might guess that "Data Management" was a good team to add packages to, but ... who really knows?).    Please update the documentation so it's clear where new packages should be added.
Answer: 1770941.0

User story: "Currently the simastrom code is sitting outside LSST which makes it not very visible and does not get built regularly making it sensitive to bitrot.  Before we can really continue to gather requirements and develop the system, we need to bring it inside the fence.    This should make the package located [here|https://github.com/lsst-france/meas_simastrom] buildable and usable in the LSST system with a minimum of external dependencies.  By usable, I mean that it should be callable as a task.  This does not need to solve the problem of persistence."
Answer: 99169.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Create a composable, validating InputField so it can use outside of the form/submit use-case."
Answer: 8753.0

User story: "Per RFC-133, we should support Object / DiaObject joins. That requires changes to query analyzer (and possibly elsewhere), currently we only support self-joins on objectId for director table. We'd need to either make DiaObject a director table and allow director-director joins, or allow director-child joins. This story involves costing how much effort it will be to implement it (and making a straw-man proposal how to implement it)"
Answer: 1491177.0

User story: "Instead of using the {{miniconda2}} EUPS product.  {{newinstall.sh}} should directly install the conda env similar to {{lsstsw/bin/deploy}}.    This will solve multiple problems:    * Removes the requirement that the installation env already has a working python installation regardless of whether or not we are installing miniconda.  * Removes the need for the {{miniconda2/3}} EUPS products which need to be manually updated and are not tagged as part of a regular release as they are outside the dep chain.  * Works around py2 packages leaking into the EUPS python env, which has been observed to cause a failure when installing py2 tarball products into an EUPS env running under py3."
Answer: 611927.0

User story: "In the [HSC CCD layout|http://www.naoj.org/Observing/Instruments/HSC/CCDPosition_20150804.png], approximately half of the HSC CCDs are rotated 180 deg with respect to the others, two others have 90 deg rotations and another two have 270 deg rotations.  The HSC camera geometry defined a coordinate system where pixel (0, 0) is always the lower-left corner.  However, the new camera geometry in the LSST stack does not use this interpretation, preferring to maintain the coordinate system tied to the electronics.  As such, accommodations have had to be made for the rotated CCDs on {{obs_subaru}}.  See DM-4998 and DM-5107 in particular for details.  The need for these accommodations, and the accommodations themselves, should be removed.  This entails a re-ingestion of the HSC calibration data files (BIAS, DARK, FLAT, etc.) as well as a redefinition of the defects files in {{obs_subaru}}."
Answer: 109541.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: Per discussion with [~<USER> and a bit of symbol table inspection, the root cause of the issue observed in DM-5105 is likely due to the Intel MKL library duplicating symbols which are present in fftw, blas, etc..  Eg.,    https://software.intel.com/en-us/node/522277    After discussion with CA sales, it has been clarified that the new mkl conda packages are under different terms than the previous MKL Optimized "add-ons".      http://docs.continuum.io/anaconda/eula    The new license is permissive and allows redistribution.  It is reasonable to assume that MKL will be present on more LSST enduser's  systems in the future and we need a strategy for managing linking to prevent symbol conflicts.  A few possibilities are:    * remove fftw, openblas, etc. from the stack and link solely with MKL (unknown if it is a 100% replacement and this would tie us to the conda package with the permissive eula)  * officially declare MKL as unsupported   * create library stubs (ie., symlinks) so that {{-lfftw}}/etc. will continue to work and re-plumb how EUPS handles optional dependencies so we can switch between openblas/fftw and MKL  * modify our scons probing logic to be able to select between the various library options and re-plumb EUPS optional dependency handling    
Answer: 551700.0

User story: "Design and refactor `validate_drp` to produce results for multiple filters.    1. Decide on the syntax for the YAML configuration file that denotes the multiple filters.  E.g., which visit goes with what filter? (/)  2. Organize the running of multiple filters in `validate.run` to sequentially generate statistics and plots for each filter. (/)  3. Add a filter designation to the default output prefix. (/)    Note: matching objects *across* filters is out-of-scope for this ticket."
Answer: 14808.0

User story: "validate_drp current takes as input both a repository and a configuration file.  The configuration file contains information to construct the list of dataIds to analyze.    However, these dataIds could be extracted from the repo itself, in cases where the desired is to analyze the entire repo.      1.  Add a function that loads the set of dataIds from the repo. (/)  2.  Select reasonable defaults for the additional parameters specified in the config file. (/)  3.  Design how to handle multiple filters. (/)"
Answer: 30733.0

User story: "Per RFC-133, we need to support scans on DiaObject table, possibly Dia*Source tables as well. This story involves adding it to the model, costing it and adding it to the baseline."
Answer: 1493198.0

User story: "Per RFC-134 we need to support scans for DRx-1. This story involves building this into the model, costing it, and changing the baseline."
Answer: 1493206.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: The required '^' convention for lists of things, e.g. {{ccd}}, {{filter}}, {{visit}} and such is surprising.  But, worse, the documentation is currently wrong in its examples and presents several {{ccd=1,2}}, {{patch=1,2}} examples.    * Fix the {{--id}} examples in {{pipe_tasks}} and other uses of processCcd.py in obs_* packages to correctly match the required syntax.    Here's the current list in {{pipe_tasks}}, but check other packages as well.    {code}  [serenity tasks] grep '[0-9],[0-9]' *.py | grep '"'  assembleCoadd.py:                               help="data ID, e.g. --id tract=12345 patch=1,2",  coaddBase.py:        parser.add_id_argument("--id", "deepCoadd", help="data ID, e.g. --id tract=12345 patch=1,2",  imageDifference.py:        parser.add_id_argument("--id", "calexp", help="data ID, e.g. --id visit=12345 ccd=1,2")  makeDiscreteSkyMap.py:            boxI = afwGeom.Box2I(afwGeom.Point2I(0,0), afwGeom.Extent2I(md.get("NAXIS1"), md.get("NAXIS2")))  multiBand.py:        parser.add_id_argument("--id", "deepCoadd", help="data ID, e.g. --id tract=12345 patch=1,2 filter=r",  multiBand.py:                               help="data ID, e.g. --id tract=12345 patch=1,2 filter=g^r^i")  multiBand.py:        parser.add_id_argument("--id", "deepCoadd", help="data ID, e.g. --id tract=12345 patch=1,2 filter=r",  processCoadd.py:        parser.add_id_argument("--id", "deepCoadd", help="data ID, e.g. --id tract=12345 patch=1,2",  {code}
Answer: 114150.0

User story: "Create a documentation project within ltd-keeper that documents the RESTful API while it is being developed. This will allow the [SQR-006|http://sqr-006.lsst.io] technote to have a place to link to for detailed information."
Answer: 1549.0

User story: "Currently validate_drp uses some manual crude addition of calibration information and constructs new schemas to store this information.  This is essentially what TransformTask is meant for.  Using this would simplify the code, make it less fragile, and ideally eventually integrate more transparently with future calibration improvements or redefinitions of how zeropoints are tracked..    1. Learn how to use TransformTask.  Note DM-4948 is the doc task for this.  2. Adapt the code.  3. Verify unchanged results on existing validation_data_decam and validation_data_cfht."
Answer: 1595416.0

User story: "Delete and apply redirects to all migrated pages in old Confluence-based Developer Guide"
Answer: 1138.0

User story: "This is a port of [HSC-1095|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1095] and a leftover commit from [HSC-1231|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1231]: [isr: don't perform overscan subtraction on bad amps|https://github.com/HyperSuprime-Cam/obs_subaru/commit/d6fe6cf5c4ecadebd5a344d163e1f1e60137c7e4] (noted in DM-3942)."
Answer: 11368.0

User story: "Renewal of the LSST security plan.  Starts with DM."
Answer: 40153.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "I'll make sure I explored other alternatives before creating a RFC for adding networkx which by itself require other packages. This is needed for the pipe_flow_x work. I tried one stand-alone package before pygraphviz but then decided to migrate to networkx as it is more complete and allow other possible future features"
Answer: 38696.0

User story: "I'll add a way to specify on the command line the path or the package to discover for CmdLineTask or SuperTasks"
Answer: 51328.0

User story: "Add the auto play to expanded mode.  Add the choose which dialog to expanded mode. Make close button work.    I am breaking this up the expanded mode ticketa because the task is getting so big and ticket DM-5019 involved reducer refactoring.  Also the refactoring needs to get into the dev branch."
Answer: 8548.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "I am seeing a number of {{RuntimeWarnings}} coming out of tests. They have the form:  {code}  RuntimeWarning: invalid value encountered in less  RuntimeWarning: invalid value encountered in greater  RuntimeWarning: invalid value encountered in true_divide  {code}  [~<USER> speculates that these are coming from {{numpy}} 1.10 when {{NaN}} values are encountered. The warning should probably just be disabled.    Full details:  {code}  ip_diffim/tests/.tests/ImagePsfMatch.py:ip_diffim/python/lsst/ip/diffim/diffimTools.py:73: RuntimeWarning: invalid value encountered in less  ip_diffim/tests/.tests/ImagePsfMatch.py:ip_diffim/python/lsst/ip/diffim/diffimTools.py:73: RuntimeWarning: invalid value encountered in greater  ip_diffim/tests/.tests/SnapPsfMatch.py:ip_diffim/python/lsst/ip/diffim/diffimTools.py:73: RuntimeWarning: invalid value encountered in less  ip_diffim/tests/.tests/SnapPsfMatch.py:ip_diffim/python/lsst/ip/diffim/diffimTools.py:73: RuntimeWarning: invalid value encountered in greater  meas_algorithms/tests/.tests/testPsfDetermination.py:meas_algorithms/python/lsst/meas/algorithms/objectSizeStarSelector.py:156: RuntimeWarning: invalid value encountered in less  meas_deblender/tests/.tests/testInclude.py:miniconda/lib/python2.7/site-packages/numpy/core/_methods.py:70: RuntimeWarning: invalid value encountered in true_divide  meas_extensions_psfex/tests/.tests/testPsfexPsf.py:meas_algorithms/2016_01.0+efcb378250/python/lsst/meas/algorithms/objectSizeStarSelector.py:156: RuntimeWarning: invalid value encountered in less  pipe_tasks/tests/.tests/testCoadds.py:miniconda/lib/python2.7/site-packages/numpy/core/_methods.py:70: RuntimeWarning: invalid value encountered in true_divide  pipe_tasks/tests/.tests/testProcessCcd.py:miniconda/lib/python2.7/site-packages/numpy/core/_methods.py:70: RuntimeWarning: invalid value encountered in true_divide  pipe_tasks/tests/.tests/testTransform.py:miniconda/lib/python2.7/site-packages/numpy/core/_methods.py:70: RuntimeWarning: invalid value encountered in true_divide  pipe_tasks/tests/.tests/ticket-2155.pyminiconda/lib/python2.7/site-packages/numpy/core/_methods.py:70: RuntimeWarning: invalid value encountered in true_divide  sims_catUtils/tests/.tests/testObservationMetaDataGenerator.py:......sims_utils/2.1.0-2-gcea7c0b+68e7d4995d/python/lsst/sims/utils/WcsUtils.py:190: RuntimeWarning: invalid value encountered in arccos  {code}    "
Answer: 1016594.0

User story: "The code to generate the kernel used to correct for the brighter fatter effect was written by Will Coulton, a grad student at Princeton.  It was never implemented on the HSC side although we used the output to apply the correction.  We need this code in LSST in order to generate kernels for cameras other than HSC.  I have attached Will's code that he used for HSC."
Answer: 1028263.0

User story: "develop design and project management methods in conjunction with L1 design.  Deal with ARI labor component  General management of staff"
Answer: 2.0