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: Butler design requires that there be at most one Dataset in each Collection with a particular DatasetType and data ID.  This is currently implemented in a very fragile, concurrency-unsafe way in the Python Registry classes.  To make it robust, we need to implement it in the Registry database itself, which is tricky for several reasons:   * We don't have a single field that represents "the data ID" of a Dataset (but this is DM-14821).   * This might need to be a multi-table constraint (the alternative is denormalizing dataset_type_name and the DM-14821 packed data ID integer into the DatasetCollections join table).   * We've thus far assumed in various places that we can detect violations of this constraint before actually making any changes to the database *or* even triggering a rollback of an ongoing transaction.  It's pretty clear we'll need to just not make the latter assumption.  For the former assumption, we may just have to sometimes "orphan" Datasets that are successfully inserted into the Dataset table but not successfully associated with a Collection.    There's also a very relevant discussion of this on DM-15686.    [~<USER>, I've assigned this to you since you'd be much better than I would be at figuring out what kind of in-database constraint we want and how best to implement that in SQLAlchemy.  But I've added a blocker on DM-14821, which I'll need to do first, and I'm expecting us to work together (possibly via new blocker tickets assigned to me) on making sure the assumptions we make in the rest of the Butler are consistent with what we can actually implement robustly as a database constraint.
Answer: 144164.0

User story: "In the recent months the expected entries and values for the atHeaderService have evolved from the original document. This ticket attempts to capture all new entries, updates and corrections to the original templates.    Some of these include and are not limited to:    1) the keys proposed on TSEIA-79    E.g. {{AT-O-20180816-00010}} would become   * {{TELCODE}} = 'AT'   * {{CNTRLLER}} = 'O'   * {{DAYOBS}} = '20180816'   * {{SEQNUM}} = 10    2) The ATS Primary Header spec from Camera ats-primary.spec (these include the keys in 1)  https://jira.lsstcorp.org/secure/attachment/34119/ats-primary.spec    3) {OBSGEO-[XYZ]} FITS standard headers to define telescope location."
Answer: 44442.0

User story: "The Gen3 ingest code currently tries to provide transactionality at a level we probably can't realistically support, which constrains the implementation of some constraints in daf_butler to fragile approaches.   Full discussion on DM-16160.     "
Answer: 131009.0

User story: "sconsUtils is using some subprocess.Popen calls directly. In some cases this leads to an open file descriptor on error.  Rewrite to use subprocess.run."
Answer: 18517.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 Minor Planet Center requested information on the likely data rates that LSST is going to deliver as a function of time and/or cumulative over the first year(s). Using opsim it is planned to create observation and discovery statistics for asteroids and deliver them to the MPC."
Answer: 297037.0

User story: "Go through the Adapters and compare the callbacks they handle with the possible callbacks (discoverable by examining the grammar definition) and make sure that the Adapters handle the possibilities, either by creating IR, or throwing if the IR is not handled (or other reasonable options - maybe elements can be safely ignored, but then something explicit should be left so that it's shown in code that we know the element is being ignored)."
Answer: 29085.0

User story: "Write short 4 page paper for the ADASS proceedings related to the poster written in DM-16176. The paper draft must be submitted by November 9th and will have to be reviewed by the LSST Publication Board. The final submission date is end of November."
Answer: 51557.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: obs_lsst needs the {{instFlux->gaussianFlux}} changes too, similar to https://github.com/lsst/obs_subaru/commit/8b010fc0b06ccc8f86b577ea38d4b4a7e3e18951#diff-27e337224a9c8a613a718b1cd0998af5   otherwise getting the following error:  {noformat}  Traceback (most recent call last):    File "/software/lsstsw/stack3_20171023/stack/miniconda3-4.3.21-10a4fa6/Linux64/meas_base/16.0-13-gd9b1b71+8/bin/forcedPhotCoadd.py", line 24, in <module>      ForcedPhotCoaddTask.parseAndRun()    File "/software/lsstsw/stack3_20171023/stack/miniconda3-4.3.21-10a4fa6/Linux64/pipe_base/16.0-12-g726f8f3+6/python/lsst/pipe/base/cmdLineTask.py", line 598, in parseAndRun      parsedCmd = argumentParser.parse_args(config=config, args=args, log=log, override=cls.applyOverrides)    File "/software/lsstsw/stack3_20171023/stack/miniconda3-4.3.21-10a4fa6/Linux64/pipe_base/16.0-12-g726f8f3+6/python/lsst/pipe/base/argumentParser.py", line 634, in parse_args      self._applyInitialOverrides(namespace)    File "/software/lsstsw/stack3_20171023/stack/miniconda3-4.3.21-10a4fa6/Linux64/pipe_base/16.0-12-g726f8f3+6/python/lsst/pipe/base/argumentParser.py", line 832, in _applyInitialOverrides      namespace.config.load(filePath)    File "/software/lsstsw/stack3_20171023/stack/miniconda3-4.3.21-10a4fa6/Linux64/pex_config/16.0-5-gd0f1235+4/python/lsst/pex/config/config.py", line 543, in load      self.loadFromStream(stream=code, root=root)    File "/software/lsstsw/stack3_20171023/stack/miniconda3-4.3.21-10a4fa6/Linux64/pex_config/16.0-5-gd0f1235+4/python/lsst/pex/config/config.py", line 563, in loadFromStream      exec(stream, {}, local)    File "/home/<USER>stack/obs_lsstCam/config/forcedPhotCoadd.py", line 11, in <module>      config.measurement.slots.instFlux = None    File "/software/lsstsw/stack3_20171023/stack/miniconda3-4.3.21-10a4fa6/Linux64/pex_config/16.0-5-gd0f1235+4/python/lsst/pex/config/config.py", line 741, in __setattr__      raise AttributeError("%s has no attribute %s" % (_typeStr(self), attr))  AttributeError: lsst.meas.base.baseMeasurement.SourceSlotConfig has no attribute instFlux  {noformat}  
Answer: 1453.0

User story: "This very important command used to come along with the older versions of the shared stack on {{lsst-dev}}.  Please enable it in the latest one."
Answer: 1711.0

User story: "Standard file size and processing time documentation."
Answer: 41823.0

User story: "Finalize debugging of end to end processing of DECAM data."
Answer: 41835.0

User story: "- Use the InfluxDB, Chronograf, and Kapacitor Helm charts with custom values  - Configure nginx ingress controller  - Create DNS records on AWS Route53 for the services  - Create tls-certs secret for TLS termination  - Add instructions to configure Slack integration for Alerts  "
Answer: 8670.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: "There has been a request to make a new release of EUPS so that it can be included as a dependency for the v17.0 pipelines release.  This ticket is to create the new EUPS release.  Further tickets are needed to change lsstsw/newinstall to use it and to enable to new shebangtron support."
Answer: 223.0

User story: "Feedback and specification of actors based on feedback from DMLT"
Answer: 200226.0

User story: "Produce update to LDM-643 describing the second and third OPS Rehearsals."
Answer: 504699.0

User story: "Update LDM-643 to obtain a first draft of OPS Rehearsal #1 (LDM-503-09).    This is work is related to https://jira.lsstcorp.org/browse/DM-16075          "
Answer: 95184.0

User story: "Pipelines Release Fall 2019  Science Pipelines release in support of operations rehearsal LDM-503-11. Release contents described in LDM-564. Will be accompanied by a characterization report."
Answer: 596599.0

User story: "ComCam Ops Readiness      This may currently be set too early."
Answer: 993363.0

User story: "{color:#17365d}Ops rehearsal for commissioning #2 {color}  More complete commissioning rehearsal: how do the scientists look at data? How do they provide feedback to the telescope? How do we create/update calibrations?     We need to check the date though since we moved #1"
Answer: 1012438.0

User story: "Large Scale CCOB Data Access.  Demonstrate the ability to read data from the CCOB with 21 rafts, store at the Data Facility and make it available on some cluster for analysis."
Answer: 594856.0

User story: "There is a project milestone that DAQ/DM/Networks are available late 2019. We will run a full scale data acquisition test in to show this is ready."
Answer: 594988.0

User story: "I will be in Chile for a few days personal travel but I will take the opportunity to check in with Jacques Sebag, Luis Coral and others. If I can get up to the summit I will. ."
Answer: 40255.0

User story: "Ensure that a new version of LSE-163 is put on Docushare."
Answer: 22894.0

User story: "Ensure that MagicDraw model is updated and a new release of LSE-61 placed on Docushare."
Answer: 96483.0

User story: "Ensure that the MagicDraw model is updated and a new version of LSE-61 placed on Docushare."
Answer: 96486.0

User story: "Ensure that MagicDraw model is updated and a new version of LSE-61 placed on Docushare."
Answer: 94899.0

User story: "The LOVE PDR is on Thursday October 18th.  This is a full day meeting."
Answer: 9620.0

User story: "Thursday 18"
Answer: 7237.0

User story: "DO management seciton and summary."
Answer: 7243.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: Looks like the API change in DM-15663 broken coaddDriver and gave the following error:    {noformat}   Traceback:  Traceback (most recent call last):    File "/software/lsstsw/stack_20181012/stack/miniconda3-4.5.4-fcd27eb/Linux64/ctrl_pool/16.0-3-gbc759ec+15/python/lsst/ctrl/pool/parallel.py", line 509, in logOperation      yield    File "/software/lsstsw/stack_20181012/stack/miniconda3-4.5.4-fcd27eb/Linux64/pipe_drivers/16.0-6-gf9cb114+19/python/lsst/pipe/drivers/coaddDriver.py", line 323, in coadd      self.detectCoaddSources.write(coadd, detResults, patchRef)  TypeError: write() takes 3 positional arguments but 4 were given  {noformat}      One command to reproduce is:  {code:java}  coaddDriver.py  /datasets/hsc/repo --calib /datasets/hsc/repo/CALIB/ --rerun RC/w_2018_41/DM-16011:private/user/name --batch-type=slurm --mpiexec='-bind-to socket' --job  bug --time 600 --cores 24  --id tract=9697 patch=4,8 filter=HSC-I --selectId ccd=0..8^10..103 visit=35892^36140^36144  {code}  
Answer: 389.0

User story: "The current log level for noting that a footprint is getting skipped is at {{log.trace}}, so this information does not get printed to the logs.  This is an useful and important piece of processing information, so should be set to WARN at these two locations:  https://github.com/lsst/meas_deblender/blob/master/python/lsst/meas/deblender/deblend.py#L297  https://github.com/lsst/meas_deblender/blob/master/python/lsst/meas/deblender/deblend.py#L302  See DM-16151 for more details."
Answer: 395074.0

User story: "The old shared stack on lsst-dev01 contained a version of {{git_lfs}} that was easy to {{setup}} with eups.  This appears to be missing with the new shared stack from DM-16129"
Answer: 1224.0

User story: "For the ADASS conference in November we are presenting a poster on the butler gen 3.  This ticket covers writing the poster, not writing the paper."
Answer: 3053.0

User story: "reported by [~<USER>:    @n8pease a couple of compiler warnings maybe you could squelch:  ```core/modules/parser/ValueFactorFactory.cc: In member function 'std::shared_ptr<lsst::qserv::query::ValueFactor> lsst::qserv::parser::ValueFactorFactory::newFactor(antlr::RefAST)':  core/modules/parser/ValueFactorFactory.cc:116:29: warning: this statement may fall through [-Wimplicit-fallthrough=]   a = a->getFirstChild();   ~~~~~~~~~~~~~~~~^~  core/modules/parser/ValueFactorFactory.cc:120:5: note: here   case SqlSQL2TokenTypes::REGULAR_ID:   ^~~~  core/modules/parser/ValueFactorFactory.cc: In member function 'std::shared_ptr<lsst::qserv::query::ValueFactor> lsst::qserv::parser::ValueFactorFactory::_newColumnFactor(antlr::RefAST)':  core/modules/parser/ValueFactorFactory.cc:175:33: warning: this statement may fall through [-Wimplicit-fallthrough=]   child = t->getFirstChild();   ~~~~~~~~~~~~~~~~^~  core/modules/parser/ValueFactorFactory.cc:178:5: note: here   case SqlSQL2TokenTypes::REGULAR_ID:   ^~~~```"
Answer: 14783.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: Setup:  {code}  source /software/lsstsw/stack/loadLSST.bash   setup lsst_distrib   {code}    {code}  [<USER>lsst-dev01 notebooks]$ jupyter notebook --no-browser --port=8701  Traceback (most recent call last):    File "/software/lsstsw/stack_20181012/python/miniconda3-4.5.4/envs/lsst-scipipe/bin/jupyter-notebook", line 4, in <module>      import notebook.notebookapp    File "/software/lsstsw/stack_20181012/python/miniconda3-4.5.4/envs/lsst-scipipe/lib/python3.6/site-packages/notebook/notebookapp.py", line 40, in <module>      ioloop.install()    File "/software/lsstsw/stack_20181012/python/miniconda3-4.5.4/envs/lsst-scipipe/lib/python3.6/site-packages/zmq/eventloop/ioloop.py", line 210, in install      assert (not ioloop.IOLoop.initialized()) or \  AttributeError: type object 'IOLoop' has no attribute 'initialized'  {code}
Answer: 1296.0

User story: "As an invited speaker, I've accidentally signed up to write a 10-page paper, and that needs to get through the LSST publication process by Nov. 9.  Might as well write (most of) the talk at the same time.    This issue captures the first draft of that, up through submission to the LSST Pub. Board.     "
Answer: 40710.0

User story: "Old stack:  {code}   source /software/lsstsw/stack3_20171023/loadLSST.bash  setup lsst_sims -t sims  echo $SIMS_CATUTILS_DIR  # /software/lsstsw/stack3_20171023/stack/miniconda3-4.3.21-10a4fa6/Linux64/sims_catUtils/2.9.0.sims  {code}  New stack:  {code}[<USER>lsst-dev01 ~]$ source /software/lsstsw/stack/loadLSST.bash  Note: use devtoolset-6 in conjunction with this stack.  [<USER>lsst-dev01 ~]$ setup lsst_sims -t sims  Ignoring unsupported tags in VRO: sims  setup: Unsupported tag(s): sims  {code}"
Answer: 14463.0

User story: "The NCSA L1 Test Stand has seen limited use the last several months as development efforts have been focused on the Tucson test stand and the ATS system. This ticket insure that the necessary pkgs are available, and also brings the C++ in line with some of the modifications in Tucson and then tests those mods with multiple CSCs running at once."
Answer: 615617.0

User story: With {{w_2018_41}}, {{meas_mosaic}} fails with errors like    {noformat}  root WARN: Failed to read {'ccd': 24, 'visit': 1324, 'tract': 9615, 'filter': 'HSC-I'}: "Field with name 'i_instFlux' not found"  {noformat}    and then Segmentation fault from zero matchList ({{Mosaic INFO: len(matchList) = 0 []}} )      One (longer than necessary) command to reproduce is     {noformat}  mosaic.py /datasets/hsc/repo --calib /datasets/hsc/repo/CALIB --rerun RC/w_2018_41/DM-16011:private/usename/   --numCoresForReadSource=12 --id ccd=0..8^10..103 visit=26024^26028^26032^26036^26044^26046^26048^26050^26058^26060^26062^26070^26072^26074^26080^26084^26094 tract=9615   {noformat}    The same command (with the same input data) works using the {{w_2018_39}} stack. 
Answer: 1421.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: antlr4 parser errors are not always useful to users, and often (always?) contain backtrace & debug output info. the parser needs to be changed to provide error information helpful to users (e.g. "could not parser query because <this> at or around query fragment <some sql>", or something like that.) The parser *also* needs to emit useful trace & error information to the log.    To do this I need to take some time to better understand the exception structure & reporting in qserv.    As noted by [~<USER>, in qserv we have {{util::Issue}} which captures useful information about where the error happened: {{__FILE__, __LINE__, __func__}}
Answer: 16067.0

User story: "Remove explanation of file sets from DMTN-084 and include a link to the official documentation instead."
Answer: 144.0

User story: "pycodestyle has accepted our patch to support W505 warnings for long docstrings.  Flake8 now needs to be modified to allow the max docstring length to be included and propagated to pycodestyle.  This is necessary because all of our checks rely on flake8 to call pycodestyle. The required steps are:    * Beg pycodestyle to make a release with W505 enabled.  * Make a pull request for flake8 adding the new functionality.  * Update our pycodestyle EUPS package (or patch it locally).  * Apply the patch locally to our flake8 package until a new flake8 release is made."
Answer: 167182.0

User story: "According to Robinson from Google, Qserv need to be split in 2 statefulset, one for masters, and one for workers."
Answer: 66325.0

User story: "Close monitoring and minor bug fixes during first two weeks following service deployment."
Answer: 88945.0

User story: "Document the design of the handoff.    Need to decide if this is a single interface document or updates to three service design documents."
Answer: 99119.0

User story: "One or more design meetings to discuss the details of the handoff.    Deliverable is a sufficient outline of the design to enable design documentation to be written."
Answer: 70252.0

User story: "In working on some new diagnostics plots, I noted a large area in the COSMOS field that was not getting any detections.  In an effort to make sure I understood the cause and consequences, I looked more deeply into the images, masks, catalogs, and logs from the processing and became suspicious that something was amiss.  This ticket is to document the further exploration and observations in order to diagnose/confirm any issues."
Answer: 9759.0

User story: "THIS IS GEN2 BUTLER."
Answer: 141049.0

User story: "Mechanism for keeping mirror current as more data are generated at SLAC or deemed important to mirror."
Answer: 612535.0

User story: "Initial transfer of each of 5 areas discovered during initial investigation – provides a start of a mirror between SLAC and NCSA. 3 are on nfs filesystem, 2 are on gpfs with underlying HSM tape; these differences require different transfers. This story covers the 2 gpfs filesystem areas: SLAC I&T and test stand data."
Answer: 67619.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: "Initial transfer of each of 5 areas discovered during initial investigation – provides a start of a mirror between SLAC and NCSA. 3 are on nfs filesystem, 2 are on gpfs with underlying HSM tape; these differences require different transfers. This story covers the 3 nfs filesystem areas: BNL test stand, vendor data, and early SLAC test stand."
Answer: 12.0

User story: "Initial investigation – where to place data, what the data layout is at SLAC, how data are stored at SLAC and will be stored at NCSA.     "
Answer: 10.0

User story: "Debugging bbcp as a potential transfer mechanism."
Answer: 23.0

User story: "The Alert sizing numbers in LDM-151 are outdated.  Update them using the Avro schemas for DIAObjects and DIASources, including the cutout images in an efficient manner."
Answer: 28827.0

User story: "Add a LongString data type into table data model to indicate a very long string.    This is a way to optimize storage and limit capability."
Answer: 5694.0

User story: "Investigate how best to deal with inotify interface for detection of new files."
Answer: 51976.0

User story: "Clearly we have no current test that would catch this, please add one (which, on the current {{w_2018_40}} weekly would fail).  See DM-16068 for details."
Answer: 230.0

User story: "The shared stack on {{lsst-dev}} has been broken by changes to the underlying conda environment, and needs reinitializing.    Unfortunately, the initialization scripts have been broken by changes to {{newinstall.sh}}.    Fix the initialization scripts and roll out a new stack."
Answer: 13438.0

User story: "Implementation of RFC-526:    The FGCM (pure python) third-party package (https://github.com/<USER>fgcm) will be added to the stack (via a github fork to allow easy continued development), and the fgcmcal package currently hosted by lsst-dm (https://github.com/lsst-dm/fgcmcal) will be moved to lsst_distrib. There are no additional dependencies that will have to be added that are not already in lsst_distrib.     This ticket adds fgcm and fgcmcal to lsst_distrib"
Answer: 57962.0

User story: "Implementation of RFC-526:    The FGCM (pure python) third-party package (https://github.com/<USER>fgcm) will be added to the stack (via a github fork to allow easy continued development), and the fgcmcal package currently hosted by lsst-dm (https://github.com/lsst-dm/fgcmcal) will be moved to lsst_distrib. There are no additional dependencies that will have to be added that are not already in lsst_distrib.    This ticket moves fgcmcal from lsst-dm to dm"
Answer: 57734.0

User story: In pipe_tasks the propagateVisitFlag.py code assumes that it can get a dataRef from the butler by using the "ccd" keyword.  In obs_lsstCam, the keyword has been changed to "detector" so this code no longer works.  I have a simple fix on the branch u/<USER>desc-ccd-fix.      It would be nice to have this fix or something similar soon for use in DESC if possible.
Answer: 40290.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: "Now that data is being generated by the ATS we need to make sure we are capturing all success and failure conditions of the transfer pipeline between it and the Data Back Bone.   "
Answer: 103356.0

User story: "Currently many parts of the monitoring infrastructure are collocated on a single bare-metal machine, vastly wasting its capabilities with idle cycles as well as leaving it isolated from the automated deployment infrastructure.  We are working to bring these service into the new Vsphere environment that is coming online at the LDF to ensure more efficient use of resources and more robust recovery should hardware failure occur."
Answer: 103358.0

User story: "Utilizations reports for all systems, services, and storage are to be automatically generated and rolled up to proper management (<USER>and Margaret Johnson, maybe more folks) on a regular basis by automatic scripts to ensure timeliness and reduction in effort."
Answer: 103360.0

User story: "To monitor certain service statuses it will be most beneficial to deploy a Jenkins platform to perform service testing of LDF services.  Initially the checks will be things such as ensuring batch jobs can be submitted successfully, rudimentary Qserv queries return, pods can be spawned in K8's, etc.  more checks will get added as time progresses.  This story is for the instantiation of the service along with these first basic checks.  "
Answer: 103361.0

User story: "This ticket covers porting existing PST documents into the new PSTN document series (modeled after LaTeX technotes with landing pages).    The initial request from PST-73 is to deploy https://github.com/lsst-pst/PSTN-001 though others are expected."
Answer: 82030.0

User story: "Ingest raw imsim data to (proto-)DBB at {{/scratch/<USER>dbb-beta/}} "
Answer: 70528.0

User story: "With a small subset of imsim data, run main DRP pipeline steps by hand using existing CmdLineTasks"
Answer: 102398.0

User story: "- Ingest the imsim data run1.2i , link or copy calibration and reference catalog, and make a Butler (Gen2) repo at /datasets  - run simple processCcd to test the repo"
Answer: 90600.0

User story: "Run jointcal with HSC-RC2 and w_2018_50"
Answer: 103731.0

User story: "Run pipe_analysis scripts   # visitAnalysis   # coaddAnalysis   # colorAnalysis   # compareVisitAnalysis   # compareCoaddAnalysis    and validate_drp   # matchedVisitMetrics.py   # validateDrp.py   # reportPerformance.py    Upload the validate_drp metrics (json files) to SQuaSH:   # dispatch_verify.py    with the w_2018_50 RC2 outputs from DM-16109"
Answer: 99435.0

User story: "Reprocess the HSC RC2 dataset, as defined in DM-11345, using Stack w_2019_02. Steps include {{makeSkyMap.py}}, {{singleFrameDriver.py}}, {{mosaic.py}}, {{skyCorrection.py}}, {{coaddDriver.py}}, and {{multiBandDriver.py}}. "
Answer: 149821.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: "Reprocess the HSC RC2 dataset, as defined in DM-11345, using Stack w_2018_50. Steps include {{makeSkyMap.py}}, {{singleFrameDriver.py}}, {{mosaic.py}}, {{skyCorrection.py}}, {{coaddDriver.py}}, and {{multiBandDriver.py}}. "
Answer: 103745.0

User story: "Run pipe_analysis scripts   # visitAnalysis   # coaddAnalysis   # colorAnalysis   # compareVisitAnalysis   # compareCoaddAnalysis    and validate_drp   # matchedVisitMetrics.py   # validateDrp.py   # reportPerformance.py    Upload the validate_drp metrics (json files) to SQuaSH:   # dispatch_verify.py    with the w_2018_48 RC2 outputs from DM-16101"
Answer: 87840.0

User story: "Run jointcal with HSC-RC2 and w_2018_48"
Answer: 90622.0

User story: "Run jointcal with HSC-RC2 and w_2018_46"
Answer: 60475.0

User story: "Run jointcal with HSC-RC2 and w_2018_44"
Answer: 47696.0

User story: "Run pipe_analysis scripts   # visitAnalysis   # coaddAnalysis   # colorAnalysis   # compareVisitAnalysis   # compareCoaddAnalysis    and validate_drp   # matchedVisitMetrics.py   # validateDrp.py   # reportPerformance.py    Upload the validate_drp metrics (json files) to SQuaSH:   # dispatch_verify.py    with the w_2018_46 RC2 outputs from DM-16100"
Answer: 59133.0

User story: "Run pipe_analysis scripts   # visitAnalysis   # coaddAnalysis   # colorAnalysis   # compareVisitAnalysis   # compareCoaddAnalysis    and validate_drp   # matchedVisitMetrics.py   # validateDrp.py   # reportPerformance.py    Upload the validate_drp metrics (json files) to SQuaSH:   # dispatch_verify.py    with the w_2018_44 RC2 outputs from DM-16099"
Answer: 40427.0

User story: "Reprocess the HSC RC2 dataset, as defined in DM-11345, using Stack w_2018_48. Steps include {{makeSkyMap.py}}, {{singleFrameDriver.py}}, {{mosaic.py}}, {{skyCorrection.py}}, {{coaddDriver.py}}, and {{multiBandDriver.py}}. "
Answer: 90676.0

User story: "Reprocess the HSC RC2 dataset, as defined in DM-11345, using Stack w_2018_46. Steps include {{makeSkyMap.py}}, {{singleFrameDriver.py}}, {{mosaic.py}}, {{skyCorrection.py}}, {{coaddDriver.py}}, and {{multiBandDriver.py}}. "
Answer: 60583.0

User story: "Reprocess the HSC RC2 dataset, as defined in DM-11345, using Stack w_2018_44. Steps include {{makeSkyMap.py}}, {{singleFrameDriver.py}}, {{mosaic.py}}, {{skyCorrection.py}}, {{coaddDriver.py}}, and {{multiBandDriver.py}}. "
Answer: 40541.0

User story: "Run jointcal with the HSC-RC2 dataset, the w_2018_42 stack"
Answer: 17318.0

User story: "Run jointcal with the HSC-RC2 dataset, the w_2018_41 stack"
Answer: 7171.0

User story: "Run pipe_analysis scripts   # visitAnalysis   # coaddAnalysis   # colorAnalysis   # compareVisitAnalysis   # compareCoaddAnalysis    and validate_drp   # matchedVisitMetrics.py   # validateDrp.py   # reportPerformance.py    Upload the validate_drp metrics (json files) to SQuaSH:   # dispatch_verify.py    with the w_2018_42 RC2 outputs from DM-16095"
Answer: 28806.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: "Reprocess the HSC RC2 dataset, as defined in DM-11345, using Stack w_2018_42. Steps include {{makeSkyMap.py}}, {{singleFrameDriver.py}}, {{mosaic.py}}, {{skyCorrection.py}}, {{coaddDriver.py}}, and {{multiBandDriver.py}}. "
Answer: 28701.0

User story: "Gen3-related work done in October"
Answer: 31720.0

User story: "Put requirements into spreadsheet for ingestion to MagicDraw."
Answer: 204388.0

User story: "Analyze use cases and derive requirements, incorporate requirements from existing project documents."
Answer: 73591.0

User story: nopytest_test_coadds.py throws the following warnings in many places:    {code:cpp}  lsst.afw.image WARN: Could not parse options; writing with defaults:    File "src/PropertySet.cc", line 189, in T lsst::daf::base::PropertySet::get(const string&) const [with T = std::shared_ptr<lsst::daf::base::PropertySet>; std::string = std::basic_string<char>]      image not found {0}  lsst::pex::exceptions::NotFoundError: 'image not found'  {code}    This seems to be coming from:  https://github.com/lsst/daf_persistence/blob/master/python/lsst/daf/persistence/posixStorage.py#L642  which calls and executes to:  https://github.com/lsst/afw/blob/a4679bc1e1d40d112e1484359a353fee477c1331/python/lsst/afw/image/image/fitsIoWithOptions.py#L97    Where it expects a property of the property set to be called `image`. However, the options that are passed through the call chain are:  `  ['visit', 'ccd']  `    This optional prameter is generated:  https://github.com/lsst/daf_persistence/blob/master/python/lsst/daf/persistence/posixStorage.py#L637  and that variable comes from:  https://github.com/lsst/daf_persistence/blob/master/python/lsst/daf/persistence/posixStorage.py#L249  which in turn comes from the butler here:  https://github.com/lsst/daf_persistence/blob/master/python/lsst/daf/persistence/butler.py#L1421  the location variable is created here:  https://github.com/lsst/daf_persistence/blob/master/python/lsst/daf/persistence/butler.py#L1297  That optional data ultimately is initialized here:  https://github.com/lsst/daf_persistence/blob/master/python/lsst/daf/persistence/butlerLocation.py#L207  So whatever is creating butler locations (Some repository or mapper) is not adding the correct fields, or afw should be looking for different things to write.    These are just notes for what I have found so far, to help anyone who gets to this ticket. I am tagging [~price] because I think he was the last one to work with the additionalData code, and [~<USER> because he may be familiar with this work, or how it impacts gen3 middleware and will know if this is even worth pursuing. Also tagging [~<USER>, as I am not sure if I put this in the right epic.    
Answer: 55285.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 error can sometimes occur when running the command "templatekit list".  {quote}RuntimeError: Click will abort further execution because Python 3 was configured to use ASCII as encoding for the environment. Consult [http://click.pocoo.org/python3/for] mitigation steps.  {quote}  I believe the fix for this is the same to the error outlined in lsst-technode-bootstrap/README.rst  {quote}To solve this, you need to set your shell's *locale* to use UTF-8.   Type these lines into your shell:    export LC_ALL=en_US.utf-8   export LANG=en_US.utf-8    *This will work on macOS. Linux distributions may be different (try C.UTF-8).*  {quote}
Answer: 194.0

User story: I did not check multi-process option for some time and now it breaks:  {noformat}  Traceback (most recent call last):    File "/project/<USER>DM-15686/pipe_supertask/bin/stac", line 25, in <module>      sys.exit(CmdLineFwk().parseAndRun())    File "/project/<USER>DM-15686/pipe_supertask/python/lsst/pipe/supertask/cmdLineFwk.py", line 226, in parseAndRun      return self.runPipeline(qgraph, butler, args)    File "/project/<USER>DM-15686/pipe_supertask/python/lsst/pipe/supertask/cmdLineFwk.py", line 372, in runPipeline      mapFunc(self._executePipelineTask, target_list)    File "/project/<USER>DM-15686/pipe_supertask/python/lsst/pipe/supertask/cmdLineFwk.py", line 96, in __call__      return result.get(self.timeout)    File "/software/lsstsw/stack3_20171023/python/miniconda3-4.3.21/lib/python3.6/multiprocessing/pool.py", line 644, in get      raise self._value    File "/software/lsstsw/stack3_20171023/python/miniconda3-4.3.21/lib/python3.6/multiprocessing/pool.py", line 424, in _handle_tasks      put(task)    File "/software/lsstsw/stack3_20171023/python/miniconda3-4.3.21/lib/python3.6/multiprocessing/connection.py", line 206, in send      self._send_bytes(_ForkingPickler.dumps(obj))    File "/software/lsstsw/stack3_20171023/python/miniconda3-4.3.21/lib/python3.6/multiprocessing/reduction.py", line 51, in dumps      cls(buf, protocol).dump(obj)  TypeError: can't pickle lsst.log.log.log.Log objects  {noformat}    Need to fix it ASAP   
Answer: 22996.0

User story: "LDM-503-09a “Pipelines Release Fall 2018”    Pending release procedure ... though the test we run should not depend on that,."
Answer: 100492.0

User story: "LDM-503-09 “Ops rehearsal for commissioning #1”     This rehearsal will be moved to 2019  and there is a telecon to get the initial ideas in place."
Answer: 321344.0

User story: "LDM-503-06 “DM ComCam Interface Verification Readiness”          Even is Actual test is blocked on DAQ; the test spec can be produced."
Answer: 603723.0

User story: "LDM-503-08b Small Scale CCOB Data Access – this was in Jira .. but did we get an updated spec ?"
Answer: 189963.0

User story: LDM-503-07 "Camera Data Processing" originally to be done post review.  The test is supposed to be in Novemeber.
Answer: 93782.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 implementation of this RFC includes:   # strip "_instFlux" from the base_Blendedness_raw_instFlux and base_Blendedness_abs_instFlux names   # move "_instFlux" to the end of the name in the fields with actual flux units, thus   # base_Blendedness_raw_instFlux_child --> base_Blendedness_raw_child_instFlux   # base_Blendedness_raw_instFlux_parent --> base_Blendedness_raw_parent_instFlux   # base_Blendedness_abs_instFlux_child --> base_Blendedness_abs_child_instFlux   # base_Blendedness_abs_instFlux_parent --> base_Blendedness_abs_parent_instFlux   # an update to the doc strings to make a clear distinction/description between "raw" and "abs"
Answer: 14175.0

User story: "create Jira tickts for the test specs assigned to relevant people with reasonable dates on them  .. tagged so we can find them easily .. ?"
Answer: 49132.0

User story: The "Adding a new package to the build" section of the DM Dev Guide has some items that are specific to Science Pipelines packages. Now that we're starting to get more services and products that are outside Science Pipelines, we should make clear what applies to those.
Answer: 28843.0

User story: "{{SelectParser}} and {{QueryAnaHelper}} are still using the antlr v2 parser, and so some qserv unit tests are still being executed using the older parser. Make the choice explicit so that these tests can be incrementally fixed and changed to use the antlr4 parser."
Answer: 13104.0

User story: "CMDB    Product tree    Archimate Model     "
Answer: 9997.0

User story: "https://docs.google.com/document/d/1b1P0_M-aKUSbtclqIXt3Tgd9AgkruMzi8MIVpA3K-GA/edit"
Answer: 53292.0

User story: "Run pipe_analysis scripts   # visitAnalysis   # coaddAnalysis   # colorAnalysis   # compareVisitAnalysis   # compareCoaddAnalysis    and validate_drp   # matchedVisitMetrics.py   # validateDrp.py   # reportPerformance.py    Upload the validate_drp metrics (json files) to SQuaSH:   # dispatch_verify.py    with the w_2018_41 RC2 outputs from DM-16011"
Answer: 31540.0

User story: - Prepare the three dependent packages without commas in the patch IDs   - Use the recently-installed stack and DESDM software bps {{w_2018_36-master}}   - Generate new HSC config and schema files consistent with the new software version  - Ingest the new config and schema files into the DBB  - Generate new skymap pickle file and ingest it into the DBB  - Run the ["hsc-mini" test|https://github.com/lsst-dm/prod_wcl/blob/master/wcl/hsc_test_hscmini.wcl] and update wcl as necessary.  For new stack features that require wcl or other updates, disable via config as much as possible just to get by, rather than adding new dependencies, new data types, etc. Updates to accommodate new features more properly will be in future tickets.   - The goal in this ticket is to have a hsc-mini that can run successfully with the {{w_2018_36-master}} software with minimum updates.  
Answer: 33127.0

User story: "Update the write method in hutils.py to deprecate method that used newline as separator."
Answer: 11142.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: "Read the papers by Alard & Lupton and ZOGY and understand the principles behind image differencing.    As you read them, you'll probably come across other papers you want to read or techniques you want to try out. Where those are more than a couple of hours of work, may new tickets to capture those activities."
Answer: 54843.0

User story: "ap_pipe is the prototype alert production pipeline, which actually does some image differencing. There's some documentation at https://github.com/lsst/ap_pipe/tree/master/doc/lsst.ap.pipe (albeit just as raw restructured text). Experiment with it, and try using it to process some data.    If necessary, [~<USER> should be able to point you in the right direction when you hit snags."
Answer: 35104.0

User story: "On your new computer, follow the tutorial at pipelines.lsst.io."
Answer: 10301.0

User story: "So far, Firefly saves the table data in IPAC table format, adding extra meta data about the table as key=value in the file header before data.  When DM-15826 is implemented, Firefly will have more meta data about table supplied by VOTable, and keeping them in the saved file would be desirable.     Develop the infrastructure and and implement csv and tsv.         Related tickets proposes to give user options to save the table in VOTable form and maybe FITS table format too. "
Answer: 142932.0

User story: "Update and test the HeaderService to use Erin Sheldon's ignore_empty on the newest version of fitsio. This allows writing more than one empty (no data) hdu, as needed by the HeaderService. The testing will be done on the Tucson Test Stand for the ATS."
Answer: 5773.0

User story: "Implementation of RFC-526:    The FGCM (pure python) third-party package ([https://github.com/<USER>fgcm]) will be added to the stack (via a github fork to allow easy continued development), and the fgcmcal package currently hosted by lsst-dm ([https://github.com/lsst-dm/fgcmcal]) will be moved to lsst_distrib. There are no additional dependencies that will have to be added that are not already in lsst_distrib.    This ticket moves the third-party fgcm ticket to the stack."
Answer: 11730.0

User story: "Update underlying version fitsio to use Erin Sheldon's ignore_empty. This allows writing more than one empty (no data) hdu, as needed by the HeaderService.     The update will also be done on the Tucson ATS Test stand."
Answer: 5804.0

User story: "Fixing some warnings on DM-15500 that looked like some that were safely fixed in meas_* accidentally brought in a requirement on numpy >= 1.14.  Revert that.     "
Answer: 5.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: "LSST fourth calibration workshop was held last week in Paris.    https://indico.in2p3.fr/event/17773/timetable/#20181002    I presented two talks :    [^at_strategy.pdf]    [^merra2_assimilation.pdf]    ^The first one is about the overall A.T. observation strategy so as to deliver the atmospheric parameters that enable to derive a monitoring of the atmospheric transparency along LSST line of sight at few permil precision.^    ^The second one explore how  ancillary data could potentially improve the precision.^    ^These findings will be included in a DM technical note.^               "
Answer: 85826.0

User story: "During the discussion of DM-15826, the team realized there are several searchProcessors in Firefly will get the table data from a file in IPAC table format persisted by Firefly before the Firefly internal DB was introduced. With the augmentation of DataGroup required by keeping more meta data from ingesting VOTable, this practice will cause problem.  We need to refactor the code of the old search processors not to write out the data result to IPAC table and access it later.    In particular, the class TableFromSource.java has to be refactored first.     Also UserCatalogQuery.java"
Answer: 88960.0

User story: "DM-15826 requires the augmentation of the Firefly internal table data model DataGroup, adding meta data about the table and fields from VOTable to DataGroup. All the newly added meta data need to be persistent in the Firefly DB for later table operations. Rendering of the data need pass the regression test.     Rendering of the new types of data like link will be captured in a different ticket."
Answer: 34320.0

User story: "Add functionality so that footprints loaded to Firefly and a source catalog loaded to Firefly are linked.  Selecting a footprint overlay on the image locates the corresponding entry in the source table, and selecting a row of the table highlights the corresponding footprint. Make the column name of the table used for the linking a parameter, though it is likely to be 'id'. "
Answer: 38978.0

User story: "selectedIdx is a state kept by TabPanel.  It's possible that selectedIdx is greater than the number of tabs due to adding and removing tab dynamically.    Currently, this condition is handled in the render function of the component.  This visually appears correct, but the state is out of sync."
Answer: 5697.0

User story: "Add scan-classification, number-of-chunks-involved, and chunks-processed-so-far columns to qmeta (chunks-processed-so-far to be periodically updated by the czar as chunk-query results are merged).    It might also be useful to consider separate qmeta states and timestamps for the state where chunk-queries are being executed and the later state where the czar aggregation query is running?"
Answer: 217257.0

User story: "Until jupyterlab-manager is published for 0.35 we have to pin JL back to 0.34 and keep extensions at a compatible level."
Answer: 7197.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: "JupyterLab is stabilizing.  See if we can drop master for latest released version in builds for things that are not our own packages."
Answer: 86527.0

User story: "Split apart the thin inheritance relationship of MergeDetectionsTask and MergeMeasurementsTask by removing MergeSourcesTask. The separated classes should be pulled out into their own files in the refactoring.    This change both makes each class more manageable on its own, but will also simplify the conversion to PipelineTasks.    This ticket will not remove the MergeSourcesTaskRunner, as it will only be around while the gen2 middleware exists anyway."
Answer: 37738.0

User story: "Add logging levels as an option for the HeaderService"
Answer: 7273.0

User story: There are two functions in the stack that effectively generate a denormalized catalog of matches.  The matches between a reference and source catalog are "joined' into a single "match" catalog, putting a {{ref_}} or {{src_}} prefix on the field names for the reference and source fields, respectively.  However, when the schema for the match catalog is created, it does not propagate any aliases that may be set, which will then break any code looking for a field by its alias name (often happens with aliases set for backwards compatibility).  This ticket is to update the following functions to include the aliases from the individual catalogs in the schema for the matched catalog:    - {{matchesToCatalog}} in {{afw}} ([here|https://github.com/lsst/afw/blob/master/python/lsst/afw/table/catalogMatches.py#L101])   - {{denormalizeMatches}} in {{meas_astrom}} [(here)|https://github.com/lsst/meas_astrom/blob/master/python/lsst/meas/astrom/denormalizeMatches.py]    I will leave it for a future tickets whether these two very similar functions should be consolidated into one.
Answer: 5830.0

User story: "A jupyter mime extension is pretty inflexible.  To do what we need to we need to make it a full Jupyter extension, then see it we can control how the file is uploaded instead of just sending to the browser then to the firefly server."
Answer: 98125.0

User story: "Add a command on the sidebar, when the user clicks then show Firefly slate in a tab. The extension will server as the basis for doing more advance interaction with the python api."
Answer: 98128.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: "During recent stress testing, it was found that if many exposures are taken very quickly one after the next, the Forwarder may get behind by 15 seconds or more. This will delay the acknowledgement that the readout is complete and the file has been processed and sent to archive. One solution is to extend the max time that the ATS CSC will wait for a response - which will allow even more delay to accumulate - then if the max time is exceeded, the system is put in Fault state as there is no response ACK.    Another solution is to NOT make the CSC dependent on the ACK arriving within a prescribed window of time, and simply address the result set information in the ACK when it arrives.[1] There is already an Forwarder health check every exposure, as well as a check that the transfer params were received by working Forwarders - both of which will send the system to FAULT state in no Forwarders are available to work...if a Forwarder dies during EndReadout, the AT CSC will know that an ACK was +never+ received. Then the health state of the Forwarder will be checked on the next exposure.    [1] If checksum verification of archived files is selected to be used, the 'result set' is a struct that includes the path to the file on the Archive and the checksum calculated for the file before it was sent. When the file is verified as existing and its checksum is correct, the ArchiveController issues a receipt for that image file and the receipt is sent to the DMCS bookkeeping database."
Answer: 90.0

User story: "Implement a minimal version of a measurement Task, and transfer responsibility for some of {{ap.verify.measurements}}' metrics to the task. Exact specifications TBD, but the initial version might only support e.g. source catalog queries."
Answer: 102275.0

User story: We have provisionally decided to create an "afterburner" task that generates metrics from Butler datasets, as proposed in [DMTN-057|https://dmtn-057.lsst.io/#option-make-measurements-from-output-datasets] However, DMTN-057 only explored the feasibility of such an approach, and stopped short of an actual design.    Create a design for a measurement task(s) that allows refinement through rapid prototyping (in particular, without depending on the introduction of `PipelineTask`), and document this design in enough detail to allow a design review.
Answer: 59185.0

User story: "for example `select max(filterID) from Filter`"
Answer: 1156.0

User story: "1. Robinson demonstrate that pd are not mounted inside pods, this need to be fixed.  2. An extra additional pod is created, fix it  3. Attach pd directly to GCE instance  4. Check what happen to pd if cluster is resized"
Answer: 22636.0

User story: <USER>(NAOJ) reports the following color terms for the HSC NB1010 filter:  {code}  'N1010': Colorterm(primary="y", secondary="z",c0=0.003607, c1=0.865366, c2=1.271817)  {code}
Answer: 18703.0