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

User story: "{{ap_verify}} will be most useful for integration testing if it can be run as a nightly job in Jenkins. Please create a job that exercises {{ap_verify}} on the {{ap_verify_ci_hits2015}} dataset. A solution that can be easily extended to additional datasets would be preferred.    Once the HiTS dataset is downloaded and set up, it can be run using {{run_ci_dataset.sh -d CI-HiTS2015}}."
Answer: 7648.0

User story: "Collect, record, and verify financial data for the LSST Data Facility. Deliverable consists of a monthly financial report delivered to the Project Controls Specialist."
Answer: 112399.0

User story: "Collect, record, and verify financial data for the LSST Data Facility. Deliverable consists of a monthly financial report delivered to the Project Controls Specialist."
Answer: 79367.0

User story: "Collect, record, and verify financial data for the LSST Data Facility. Deliverable consists of a monthly financial report delivered to the Project Controls Specialist."
Answer: 40592.0

User story: "Collect, record, and verify technical progress data and narratives for the LSST Data Facility. Deliverable consists of updated JIRA issues and a Technical Progress Report."
Answer: 103631.0

User story: "Collect, record, and verify technical progress data and narratives for the LSST Data Facility. Deliverable consists of updated JIRA issues and a Technical Progress Report."
Answer: 62252.0

User story: "Collect, record, and verify technical progress data and narratives for the LSST Data Facility. Deliverable consists of updated JIRA issues and a Technical Progress Report."
Answer: 31681.0

User story: "I wrote a brief orientation guide to meas_base. Include it in the meas_base Sphinx documentation."
Answer: 33108.0

User story: "See if IOPS were really our problem by using SSD rather than spinning disk."
Answer: 2.0

User story: "Currently flags are not being copied from the DIASource catalogs into the PPDB.  This ticket is to do so."
Answer: 111122.0

User story: "Learn how the LSST sims system works and how it could be applied to inserting fake objects. There is a script that I wrote while working on this in /home/sr525/insertFakeSources/mkFakeSourceCat.py, thank you to [~<USER> for all the help with this and the initial script this was based on."
Answer: 89767.0

User story: "SSIA."
Answer: 2816.0

User story: "Add send_telemetry() method and provide telemetry queue addition in at_Setup.py/Setup.py    and send telemetry for:    Final Image to Archive success    Non-Fatal errors such as:        Readout Failure        File Transfer Failure        Forwarder formatting error        Archive Controller unresponsive        and more as each component file is scanned for telemetry needs..."
Answer: 634256.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: "some of the unit tests were still using the antlr 2 parser.    change those unit tests to use the antlr4 parser    add those queries to the equivalent-IR test (in testCControl) and fix any issues identified."
Answer: 26343.0

User story: "Write a community post telling people about the new star galaxy classifier and how to use it."
Answer: 4287.0

User story: "Make Camera persistable.  I was originally expecting this to be a natural outcome of the combination of DM-14980 and DM-14363, but I've changed approaches on those."
Answer: 9742.0

User story: "Become familiar with looking at the butler though sql to investigate problems and or looking at output. This involves brushing up on sql, and learning about how all the information is stored in our database. "
Answer: 86474.0

User story: "Replace afw visitInfo with obs_metadata ObservationInfo inside daf_butler and obs_base. For the first test, includes updates of obs_subaru so that ci_hsc butler gen 3 ingest will use it."
Answer: 30514.0

User story: "Daf_butler put documentation says that it will take a DatasetRef, DatasetType, or string. However, if given a DatasetType it attempts to use it as a string, calling the DatasetType lookup function, which fails in its sql query. If the user passes a DatasetType, the function should use it and skip the lookup."
Answer: 1175.0

User story: "Optimize pyprofit's multi-Gaussian Sersic model evaluation with (or for fitting) pixel-convolved multi-Gaussian PSFs. In this case the model evaluation is one Gaussian function per component per pixel, which is easy to optimize in C++, avoiding the overhead in creating GalSim objects."
Answer: 95153.0

User story: "Implement and test a customizable workflow for galaxy fitting in pyprofit, specifying which models to fit in which order and giving options for the PSF model, initial parameters, etc."
Answer: 167143.0

User story: "DM-15349 implemented a Gaussian mixture approximation of a Sersic profile a la Hogg & Lang 2013, using the weights for exponential (n=1) and de Vaucouleurs (n=4) profiles. I updated the code to use interpolated weights for 0.5 < n < 6.25 from Dustin Lang's Tractor code."
Answer: 85070.0

User story: "Collect a list of datasets expected to be stored in the LFA component of the EFD.  This will also mean collecting additional information related to them like latency requirements, size and cadence."
Answer: 1.0

User story: "Create a conda distribution of [Documenteer|https://documenteer.lsst.io] and its dependencies so that that it can be installed by newinstall.sh as part of the conda environment.    This will deprecate the current process of maintaining a {{requirements.txt}} file in the https://github.com/lsst/pipelines_lsst_io repository that specifies the version of Documenteer that corresponds to that version of the product codebase."
Answer: 713156.0

User story: "Check quality of Done epics as per LDM-294"
Answer: 16314.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: "Pipeline task init method should take kwargs that that in cases where a pipeline task is used as a subtask all arguments are appropriately forwarded to all constructors."
Answer: 5351.0

User story: "Provide capabilities and support for LSP demo and Stack Club activities during the LSST2018 Project and Community Workshop."
Answer: 1243.0

User story: "In the first run of calibration of S18a with FGCM (DM-15545) there is a bimodality in the comparison between HSC r-band and Gaia G-band.  This could be due to disconnected regions or due to assumptions about the HSC-R and HSC-R2 filters (or something else).  "
Answer: 98018.0

User story: "Currently, every component file lists its error code prefix in the class file. In light of recent refinements in error code, the prefixes should be put in toolsmod so that components may pass in its name and receive the prefix – in case the overall prefix needs to change again."
Answer: 641382.0

User story: "Following discussion on DM-15760, we would like to try changing the database schemas to use TAI MJD as a single double precision number, rather than a {{datetime}} field.  We have to investigate whether sqlalchemy can support full double precision to represent MJDs (full precision gives about 1 ms accuracy), we should also determine whether the user interface should require MJDs as Python floats in all cases, or if the user could use {{astropy.time.Time}} everywhere (which understands TAI), converting to and from MJD at the database table layer."
Answer: 788140.0

User story: "Retire by:    - Stopping automatic builds;  - Updating documentation;  - Posting on CLO.    At least in the short term, I do not propose to actually remove the existing code."
Answer: 373.0

User story: "This notebook demonstrates the InfluxDB stack. We run InlfuxDB + Chronograf + Kapacitor using the docker compose configuration in this repo. We show different ways to write data to InfluxDB using the CLI utility, the HTTP API and the Python client. We send SQuaSH metrics to InfluxDB and use Chronograf UI for creating a dashboard."
Answer: 102514.0

User story: "Pipeline builder needs to instantiate DatasetTypes which depend on StorageClass (and they both are configured via task config). We want to keep pipeline builder independent of butler but that means that initialization of StorageClassFactory becomes an issue. DM-15850 adds support for loading all standard StorageClasses (which come from a standard YAML config) but any non-standard configuration will become an issue in this approach.    I want to see how we can solve this problem by either pre-loading non-standard config for the factory or avoiding its use entirely. "
Answer: 68241.0

User story: "# Review for standards compliance  # Make comments on code engineering, structure, style, and maintainability"
Answer: 3074.0

User story: "Read and comment on the OCS queue document draft, LTS-836."
Answer: 2995.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: "This needs to be sufficient to enable the creation of a text-based (YAML) source-of-truth in the cat package to describe tables, columns, and groupings."
Answer: 27456.0

User story: "There appears to be an issue with the {{py}} package, possibly due to it not being upgraded in the shared stack."
Answer: 47846.0

User story: "Once the AP packages are in {{lsst_distrib}}, we can add them to {{pipelines.lsst.io}} following the procedure in the [developer guide|https://developer.lsst.io/stack/add-a-package-to-pipelines-lsst-io.html]. This ticket is to register all the documentation, including:  * Updating to the latest [documentation standards|https://developer.lsst.io/stack/package-documentation-topic-types.html], including removing the package-level docs for code repositories and overhauling the ones for datasets.  * Checking inter-package links in the Sphinx documentation, which have until now gone untested.  * Updating cross-references from non-Sphinx documentation (e.g., readmes) to point to the published pages."
Answer: 18968.0

User story: "daf_butler has a really nice, robust function for importing a symbol given a string.  I want that in afw for importing PupilFactory classes in cameraGeom, so I can replace a Python class object with a string when moving Camera to C++."
Answer: 1156.0

User story: "Try out the CADC TAP services, and get them working with Topcat to be a start.  Once we get that, get a handle on how to develop for the system if it looks good.  Try to get some precursor data loaded into the oracle db."
Answer: 51592.0

User story: "The naming conventions in this file seem to vary, with underscores, fully-capitalized words, initially-capitalized words, and camelCase used in various places. I can see some of that being desirable for consistency with SAL, but some appears gratuitous."
Answer: 294122.0

User story: "The LSST license header is not present on the python files for salpytoos and it should be added as described on:    [https://developer.lsst.io/python/style.html#each-python-file-must-contain-the-standard-license-preamble]"
Answer: 64616.0

User story: "The LSST license header is not present on the python files for the HeaderService and it should be added as described on:    https://developer.lsst.io/python/style.html#each-python-file-must-contain-the-standard-license-preamble"
Answer: 64611.0

User story: "In salpytools.salpylib make sure that the  function  send_logEvent() has the correct payload when  eventname == 'rejectedCommand'          "
Answer: 40018.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_38 RC2 outputs from DM-15690"
Answer: 50366.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: "Run jointcal with the HSC-RC2 dataset, the w_2018_38 stack, with the following config overrides:      {noformat}  config.astrometryRefObjLoader.ref_dataset_name='ps1_pv3_3pi_20170110'  config.photometryRefObjLoader.ref_dataset_name='ps1_pv3_3pi_20170110'  config.astrometryRefObjLoader.filterMap={'B': 'g', 'r2': 'r', 'N1010': 'z', 'N816': 'i', 'I': 'i', 'N387': 'g', 'i2': 'i', 'R': 'r', 'N921': 'z', 'N515': 'g', 'V': 'r'}  config.photometryRefObjLoader.filterMap={'B': 'g', 'r2': 'r', 'N1010': 'z', 'N816': 'i', 'I': 'i', 'N387': 'g', 'i2': 'i', 'R': 'r', 'N921': 'z', 'N515': 'g', 'V': 'r'}  {noformat}    In the future, the config overrides won't be needed once DM-15606 is merged. "
Answer: 28969.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: "  In this notebook we introduce the main concepts of Prometheus. We run a Prometheus server, and look at a few metrics to illustrate the Prometheus interface and the PromQL query language.    Then we use the Prometheus python client to instrument a small app and expose metrics to the Prometheus server.    Finally we exemplify alerting with Prometheus."
Answer: 29938.0

User story: Following the merge of DM-11693, we are discovering that sconsUtils is no longer deleting the .xml.failed file when it is re-run.  The "running tests twice as part of install" problem has been fixed but normal developer workflow of typing scons, getting a failure, fixing the failure, typing scons again, is now broken.  This is because the second time you type scons the .failed file is not removed, so pytest now passes but sconsUtils sees the .failed file and stops everything and reports that there was a problem (when there wasn't).   Being forced to manually remove the .failed file is annoying.
Answer: 30207.0

User story: "Currently the default Storage Classes are loaded whenever a Butler is created. Supertask needs to know about Storage Classes without an associated butler. To allow this to work change StorageClassFactory so that it always tries to load the definitions from the daf_butler/config directory.    PipelineTask may still need to provide a way for people to define non-standard StorageClasses but that is out of scope of this ticket."
Answer: 2680.0

User story: The pipeline user documentation talks about using the {{Calib}} object and "coadd's zeropoint", with some particular details that only apply to the old {{Calib}}. We should clean that up, and any other user docs, so they refer to the new {{PhotoCalib}}.
Answer: 292956.0

User story: "Convert MergeDetectionsTask into a pipeline task. This work will probably involve working on its base class as well. Some things like loading schemas from the butler may need to have a temporary workaround for the time being."
Answer: 130197.0

User story: "The primary config file for Redis in /etc/redis.conf should have an include that pulls in the Redis.conf from /usr/local/etc with the correct values needed for DM L1 set up, such as:    Number of database instances (20)    Location of Redis dump file    Frequency of dumping a snapshot..."
Answer: 645479.0

User story: "The pipeline task conversion processes involves separating all code which needs access to io from algorithm code. In some cases this is not yet possible (such as with IdFactories)  as the middleware necessary for doing this does not yet exist.    However, to make process on the bulk of the conversion process it is possible to use stand in code to allow conversion and testing in place of a final solution.    This ticket will cover the work of going back to all the places where this occurs and fixing it up to a final solution once the required middleware exists."
Answer: 193640.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 have been issues with getting a successful transfer of readout params to the forwarders. This seemed a sometimes intermittent problem that was caused by     not getting a proper ack from the forwarder about 10% of the time. After analysis, the xfer_params ack is returning SO quickly that calling the 'clear_forwarder_response_state'    method immediately after publishing the xfer_params message  left too litle time for the ack response code to begin listening, as the response is returned in another thread. The fix here was simple, and painfully obvious in hindsight - clear the state first and then publish the xfer_params message. The debug timer has also been replaced with a progressive ack timer.  This is an important fix, because a FAULT state is entered when time exceeds the limit for the xfer_params_ack to return."
Answer: 11.0

User story: With {{w_2018_38}}, {{mosaic.py}} failed with many errors such as:  {noformat}  root WARN: Failed to read {'ccd': 19, 'visit': 1270, 'tract': 9615, 'filter': 'HSC-I'}: "Field with name 'i_fluxErr' not found"  {noformat}    Then  {noformat}  Mosaic INFO: frameIds : []  Mosaic INFO: ccdIds : []  Mosaic INFO: Creating kd-tree for matched catalog ...  Mosaic INFO: len(matchList) = 0 []  Caught signal 11, backtrace follows:  <....>  Segmentation fault  {noformat}        It looks related to the changes of DM-10302? 
Answer: 3750.0

User story: "In C++, it's natural to require an explicit template argument for templated functions whose template parameters only affect their return type.  That doesn't work when wrapping normally with pybind11, which just sees a set of equivalent overloaded functions and blithely selects the first one defined.    The [Num-]Pythonic interface for functions like this would take a {{dtype}} argument to select the type returned, and this ticket will provide a helper class that makes that easy to implement.    This is a spin-off from DM-15500, where this helper code is now almost complete.    I'm calling this gen3-middleware because that's why I'm doing DM-15500, even though this ticket is a few steps removed from the core gen3 work.  TCAMs are welcome to reclassify."
Answer: 18789.0

User story: "Attend meeting - give talk on Tuesday - Workshop on Thursday .."
Answer: 34611.0

User story: "Assist the Google cloud PoC effort (DM-15522) by preparing LSST30 dataset within IN2P3 for optimum transfer.     "
Answer: 12.0

User story: "Based on the tests in DM-15658, transfer LSST30 dataset to the europe-west1 bucket, then to us-central1 within the cloud."
Answer: 44629.0

User story: "Following RFC-528, remove the unused sexagesimal angle routines from utils and afw. obs_ctio0m9 needs fixing since it is the only package that uses the utils routines. Replace that with astropy usage."
Answer: 4330.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: "In order to make better use of the UCD and other attributes in VOTable, we need to improve the current function to read in a VOTable in Firefly. The goal is to read and store all the attributes available in VOTable, making them accessible for later usage.      This will result in substantial modification to Firefly internal table data model DataGroup.     Two new object classes added to the DataGroup: LinkInfo, GroupInfo. (i.e. LinkObject and GroupObject in the attached draft). "
Answer: 30061.0

User story: "For display of images, source catalogs and footprints described in DM-15823, enable a zoom-to-footprint functionality. The user will be able to select a row in the displayed source catalog. The image will then zoom to the appropriate level to the selected footprint, and will highlight it. The zooming will make the footprint fill around 90% of the display."
Answer: 250094.0

User story: "Implement functionality as part of the {{display_firefly}} backend to enable drawing footprints on an image, a custom method of the {{Display}} object.    The {{overlayFootprints}} method will take the {{SourceCatalog}} instance as a required arguments, and will upload a table object that Firefly will understand to contain LSST detection footprints for drawing. Functionality will be added for setting the layout to place the image at upper left and the table at bottom in the Firefly display, similar to IRSA's Gator layout.         The example notebook is https://github.com/lsst/display_firefly/blob/master/examples/HSC-Footprints.ipynb"
Answer: 66168.0

User story: Thanks to DM-15472, we have a {{lsst-task-topic}} that marks a topic as being a *task topic* that is the canonical documentation for a task.    We now want to create toctrees of these task topics that automatically find task topics by some criteria, and then present those topics in a useful way.    Some features:    - Be able to both generate toctree entries and a non-indexing list. This is so that we can create polyhierachies.  - Present the tasks using a definition list structure so that the "term" is the task class's name and the definition is the one-sentence summary or customized summary presented as the content to the {{lsst-task-topic}} directive.  - Filter for tasks based on a root Python namespace  - Filter for tasks based on tags (tags are entered on the {{lsst-task-topic}} directive).
Answer: 17103.0

User story: "Update to error/acknowledgement codes from commands, particularly when CSC already in requested state. Following the description from:         https://confluence.lsstcorp.org/display/LTS/Command+Acknowledgment"
Answer: 67366.0

User story: "Update the matrix of allowed transitions for CSCs. This is the states.py libraries inside salpytools."
Answer: 19918.0

User story: "The utils package uses boost::regex for sexagesimal string parsing and for demangling. Neither of these examples need the power of boost::regex and std::regex can be used instead."
Answer: 6933.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: "qserv_deploy has to support  https://cloud.google.com/kubernetes-engine/docs/how-to/persistent-volumes/preexisting-pd to run on GKE."
Answer: 18754.0

User story: "Currently, {{ap_verify}} is configured to use an SQLite association database (this assumption is, in particular, hard-coded into the {{measurements}} subpackage). Switch {{ap_verify}} over to using {{l1dbproto}} so that {{ap_association}} can remove support for SQLite, preferably in a way that doesn't couple {{ap_verify}} to future changes in how databases are handled."
Answer: 116626.0

User story: "This is the DM version of https://jira.lsstcorp.org/browse/TSEIA-83    Dates in header service headers are illegal    Headers in files written with the OCS/CCS bridge such as    {{DATE-OBS}}  {{2018-08-20T20:51:59.393(UTC)}}    which are illegal (with the trailing {{UTC}}).  This is with {{dayObs=2018-08-20 seqnum=3}}       |KEYWORD: DATE-OBS|  |REFERENCE: FITS Standard|  |STATUS: reserved|  |HDU: any|  |VALUE: string|  |COMMENT: date of the observation|  |DEFINITION: The date of the observation, in the format specified in the|  |FITS Standard. The old date format was 'yy/mm/dd' and may be used only|  |for dates from 1900 through 1999. The new Y2K compliant date format is|  |'yyyy-mm-dd' or 'yyyy-mm-ddTHH:MM:SS[.sss]'.|"
Answer: 5850.0

User story: "Use functions in salpytols to write utility script to clear up the dreaded DDS_RETCODE_PRECONDITION_NOT_MET that plagues CSCs."
Answer: 10026.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: With the release of Sphinx 1.8.0, documenteer's Sphinx runner appears to be broken:    {code}  build succeeded, 110 warnings.    The HTML pages are in _build/html.    Traceback (most recent call last):    File "/Users/<USER>lsst/pipelines_lsst_io_stack/stacks/w_2018_37/python/miniconda3-4.5.4/envs/lsst-scipipe-fcd27eb/lib/python3.6/site-packages/documenteer/sphinxrunner.py", line 86, in run_sphinx      return app.statuscode    File "/Users/<USER>lsst/pipelines_lsst_io_stack/stacks/w_2018_37/python/miniconda3-4.5.4/envs/lsst-scipipe-fcd27eb/lib/python3.6/contextlib.py", line 88, in __exit__      next(self.gen)    File "/Users/<USER>lsst/pipelines_lsst_io_stack/stacks/w_2018_37/python/miniconda3-4.5.4/envs/lsst-scipipe-fcd27eb/lib/python3.6/site-packages/sphinx/util/docutils.py", line 144,in patch_docutils      yield    File "/Users/<USER>lsst/pipelines_lsst_io_stack/stacks/w_2018_37/python/miniconda3-4.5.4/envs/lsst-scipipe-fcd27eb/lib/python3.6/contextlib.py", line 88, in __exit__      next(self.gen)    File "/Users/<USER>lsst/pipelines_lsst_io_stack/stacks/w_2018_37/python/miniconda3-4.5.4/envs/lsst-scipipe-fcd27eb/lib/python3.6/site-packages/sphinx/util/docutils.py", line 134,in using_user_docutils_conf      os.environ.pop('DOCUTILSCONFIG')    File "/Users/<USER>lsst/pipelines_lsst_io_stack/stacks/w_2018_37/python/miniconda3-4.5.4/envs/lsst-scipipe-fcd27eb/lib/python3.6/_collections_abc.py", line 795, in pop      value = self[key]    File "/Users/<USER>lsst/pipelines_lsst_io_stack/stacks/w_2018_37/python/miniconda3-4.5.4/envs/lsst-scipipe-fcd27eb/lib/python3.6/os.py", line 669, in __getitem__      raise KeyError(key) from None  KeyError: 'DOCUTILSCONFIG'    Exception occurred:    File "/Users/<USER>lsst/pipelines_lsst_io_stack/stacks/w_2018_37/python/miniconda3-4.5.4/envs/lsst-scipipe-fcd27eb/lib/python3.6/os.py", line 669, in __getitem__      raise KeyError(key) from None  KeyError: 'DOCUTILSCONFIG'  {code}    Note that the HTML _is_ built successfully, but the command returns a non-zero build status that is breaking the Jenkins build.    I think the most expedient solution is to pin Sphinx to <1.8.0 and solve the 1.8.0 compatibility later. We can probably release this new version as Documenteer 0.3.0 (out of beta).
Answer: 230.0

User story: "It looks like in current implementation of graph builder it is possible to make graphs containing loops. Simplest example that was observed already is when pipeline of a single task reads and writes into the same dataset type. We are already supposed to have loop detection when we build Pipeline, maybe logic there is not robust enough and needs a small fix."
Answer: 1824.0

User story: "DM-10302 changed the names of `flux` columns to instFlux. As ap_association isn't currently in distrib the change was missed on the package. This ticket will modify the names of the columns ap_association expects from flux to instFlux"
Answer: 17.0

User story: "SSIA"
Answer: 69195.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: "Add IMAGE_ID val to xfer_params messages to CSCs so that Fwdrs can use a more efficient internal job representation."
Answer: 47613.0

User story: "The DMCS currently allows OCS Commands sent for start up and shutdown, to respond positively when the DMCS is, say, asked to move from Disable to Disable state. When this ticket is Done, the DMCS (via the OCS_Bridge) will respond with a negative ACK and include command error number -324 that designates that the CSC is already in the requested state. This will not generate a FAULT however. In the description field of the ACK, the DMCS should briefly explain that the OCS is asking to move to Disable (as an example) while Disable is already the current state of the CSC.    The detection of this condition is simple, however a meaningful description of the error will take a bit of time. It will probably rely on a static lookup table for string responses."
Answer: 2996.0

User story: "Now that the code has been updated from {{_flux}} to {{_instFlux}} in schemas, we should do a minimal pass over our documentation to bring it up to date. [~<USER> had some suggestions of where we should look in that regard, on DM-10302"
Answer: 9476.0

User story: "Create a task to force photometer difference images and PVIs at DiaObject locations. This ticket only creates the task. Further tickets will integrate it into ap_association and ap_pipe."
Answer: 213263.0

User story: "The change in variable names from Sigma to Err where not caught in ap_association as it not currently part of lsst_distrib. This ticket makes that change in package."
Answer: 43.0

User story: "Current version of DESDM depends on ​[PyFITS|https://pythonhosted.org/pyfits] which is being deprecated in favor of [astropy.io.fits|http://docs.astropy.org/en/stable/io/fits/index.html]. As a result running *dessubmit* generates a warning    {code}  /project/production/py3/desdm_prereqs/lib/python3.6/site-packages/pyfits/__init__.py:22: PyFITSDeprecationWarning: PyFITS is deprecated, please use astropy.io.fits PyFITSDeprecationWarning)  # noqa  {code}    The goal is to replace *pyfits* with *astropy.io.fits* across DESDM code base."
Answer: 34302.0

User story: "In support of ticket DM-10500, creates a framework for an async SearchProcessor.  This ticket will introduce an async SearchProcessor as well as making the SearchManager aware of async calls.  It will also allow SearchManager to treat backgrounded search differently depending on whether it's async or sync. "
Answer: 18723.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: "   {code:java}  4/ndarray/1.5.1.lsst1+2/include/ndarray/pybind11.h:83:8: warning: 'ndarray::Pybind11Helper<double, 2, 2>' declared with greater visibility than the type of its field 'ndarray::Pybind11Helper<double, 2, 2>::wrapper' [-Wattributes]  /home/<USER>LSST/lsstsw/stack/Linux64/ndarray/1.5.1.lsst1+2/include/ndarray/pybind11.h: In instantiation of 'struct ndarray::Pybind11Helper<double, 1, 0>':  /usr/include/c++/7/tuple:185:12:   recursively required from 'struct std::_Tuple_impl<1, pybind11::detail::type_caster<ndarray::Array<double, 1, 0>, void>, pybind11::detail::type_caster<ndarray::Array<double, 2, 0>, void>, pybind11::detail::type_caster<lsst::geom::Point<int, 2>, void> >' {code}  I had thought these would go away with DM-15151, but I guess not, and it's probably better for us to fix them in the code anyway."
Answer: 1272.0

User story: "SSIA."
Answer: 22956.0

User story: "PST in SLAC this week"
Answer: 5773.0

User story: "do any needed updates"
Answer: 5802.0

User story: "Agree with [~<USER> where to document local jupyter even if it is NOT SUPPORTED. We need a place for hacks and things people will do .."
Answer: 34532.0

User story: In section 3.2.2 - Solar System Object Processing, step 4 is to delete {{DIAObjects}} which have had all their {{DIASource}} detections reassigned to {{SSObjects}}. For query-repeatability purposes these should not be deleted, and instead should be "expired" by setting the appropriate validity end time (c.f. DPDD Section 2.5, Repeatability of Queries). Further detail on this process is described in LDM-135.
Answer: 423513.0

User story: "Look over, expand on, and rewrite https://confluence.lsstcorp.org/display/JP/System+Requirements"
Answer: 101942.0

User story: "DBB design choices depend somewhat on the actual latency of Prompt Product delivery to science users.  Give [~<USER> some background to prepare for questions from the DBB requirements group."
Answer: 5447.0

User story: "Finish reading and commenting on [~<USER>'s document."
Answer: 9997.0

User story: "For the Sphinx-based task topic documentation, we want to be able to show the signature of the task's Python API (particularly its {{__init__}} and {{run}} methods). This shouldn't replace the canonical source of documentation as generated by {{automodapi}}, but it should instead give users a quick summary and entrypoint into that API documentation.    One scenario is to show the signatures of the tasks's constructor and methods, and make those signatures clickable so that a user can access the API docs quickly.    Another approach might be to also show the full docstring of things like the constructor and run method.    The best approach is TBD."
Answer: 5657.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 move of the implementation of FitsStorage on DM-15599 neglected to include support for reading PropertyLists directly from FITS.  This is somewhat understandable; we had no test coverage for that functionality and it was used in only one place (obs_lsstCam) that's not yet in CI.  Should be easy to add it back in."
Answer: 182.0

User story: "Once RFC-521 is accepted I'll need to move generally useful pieces of code into a new package. Code that is only useful for performance studies will stay in {{l1dbproto}}. The name of the new package will likely be {{dax_ppdb}}, modules/classes will need to be renamed too.    Some simple unit tests would be nice to have too to make sure that things work OK after splitting.  "
Answer: 14896.0

User story: "Implement initial Task documentation in packages (such as {{lsst.pipe.tasks}}) based on the in-development template ( DM-15422) and using the custom Sphinx roles and directives (DM-15472 )."
Answer: 60691.0

User story: "We recently added <USER>as a user on the DM ATS machine located in Tucson. He was to have sudo privs for running a check script and a restart script for the DM ATS services on that machine. The user is unable to run the scripts, however."
Answer: 641.0

User story: "Task is misnamed - should be called something like `runEotestTask.py`. Nobody uses this at the moment, so no RFC should be required.    Also, add Travis checking and reformat docstring for flake8."
Answer: 71142.0

User story: "Remove remnants of pex_policy, which was long ago shifted to used {{pex_config}}.    The main things being gotten rid of are:    Commands:    killcondor.py - used the old style pex_policy job description to identify and kill jobs.  writeNodeList.py - this was required in an early version of ctrl_orca to enumerate the nodes used (in pbs jobs, I believe).  ProvenanceRecorder.py - This was used to make database records for policy files used in a run.  This was in addition to the provenance information that used to be recorded via the provenance package, which is also obsolete, since it also used pex_policy.  I don't think a replacement was ever made for that package.    lsst/ctrl/orca:    PolicyUtils.py - used to get all file names listed in a policy    The ups/ctrl_orca.table needs to have pex_policy removed as a required setup."
Answer: 1860.0

User story: "To test [DM-15663|https://jira.lsstcorp.org/browse/DM-15663], it we be necessary to test using the preflight solver that Andy has been working on. This ticket captures the work that will go into learning that tool to execute tests."
Answer: 10422.0

User story: "When running the `construct*.py` scripts, if there is no input data (_e.g._ when the ingest has failed), the error one gets tends to be a division by zero from the zero-length of the refList. This is more confusing to newbies and people unfamiliar with this part of the stack that one might expect, and is worth fixing I think. A simple check that one isn't operating on no data before going ahead should suffice I think."
Answer: 306.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 weekly w.2018.37 fails with the error:    {{java.lang.NullPointerException: Cannot get property 'docker_registry' on null object}}    As per [~<USER> analysis, the problem seems to be in [https://github.com/lsst-sqre/jenkins-dm-jobs/blob/master/pipelines/release/docker/build_stack.groovy#L34]    where {color:#FF0000}+release+{color} should be {color:#FF0000}+scipipe+{color}."
Answer: 1172.0

User story: "This work was started on DM-14504, while trying to make it possible to remove {{daf.base.Persistable}} by first removing pex_policy.  I made a lot of progress on that, but the effort stalled out when I discoverd that ctrl_orca and ctrl_execute still use pex_policy, so I've spun off the work I _have_ done one this ticket.  Even if it doesn't remove pex_policy entirely, it'll still be a step in the right direction.     "
Answer: 48700.0

User story: "obs_lsstCam calibrations policy uses as {{date}} as {{obsTimeName}}, not {{dateObs}}.     {noformat}  RuntimeError: Unable to retrieve bias for {'visit': 185615, 'detector': 29, 'run': '185615', 'raftName': 'R10', 'detectorName': 'S02', 'snap': 0}: no such column: date  {noformat}"
Answer: 14382.0

User story: "{noformat}import lsst.cp.pipe.makeBrighterFatterKernel as kernelGen  biases, means, xcorrs  = kernelGen.calcBiasCorr([70000, 90000, 110000], (2000,1000), useTaskCode=False, nSigma=5, repeats=3){noformat}  and  {noformat}biases2, means2, xcorrs2 = kernelGen.calcBiasCorr([70000, 90000, 110000], (2000,1000), useTaskCode=True, nSigma=5, repeats=3){noformat}  differ, and they shouldn't. Investigate and fix.         Furthermore, as per what was originally DM-15401: something seems to not be quite right in the calculation of cross-correlations in {{MakeBrighterFatterKernelTask}}, as the sum of the cross-correlations are coming out much higher than they should be (I think, based on the code it was ported from at least).    Find out why, and once that's done, put the config value {{xcorrCheckRejectLevel}} back to the nominal value of 0.2 (or was it 0.1, check Will's code), if appropriate.    Given that these may be related, these are being combined."
Answer: 136743.0

User story: "This work deals with optimizing performance of current DR backup system by making code changes to reporting and transfer code base."
Answer: 15942.0

User story: "This story deals with getting copy of adm01 backups and they are pushed to backup01, from where it is getting backed up to the tape."
Answer: 15945.0

User story: "We're writing to let you know that, as part of the expansion to the IP ranges used for HTTP(S), TCP Proxy, SSL Proxy, and Internal Load Balancing, firewall rules for your projects need to be updated to allow traffic from both the 35.191.0.0/16 and 130.211.0.0/22 IP ranges by October 15, 2018."
Answer: 5973.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: John, I added you as a watcher in case I was duplicating effort.    Plan is to make lightweight task that can "applyJointcalResults" to calexps (based on [https://github.com/lsst/jointcal/blob/master/python/lsst/jointcal/jointcalCoadd.py)]  and make choice of meas_mosaic or jointcal retargetable.  Need to add the ability to do apply the photometric calibration in addition to the WCS (like [https://github.com/lsst/meas_mosaic/blob/master/python/lsst/meas/mosaic/updateExposure.py#L47)]          Outstanding question: do we want to be able to mix and match? Photo from one and WCS from another?     
Answer: 98396.0

User story: "Different pipelines that run on the same dataset will produce different metric results, we want to compare them on the same display, so we need a way to distinguish them.    Initially, I think that just adding metadata for the run would do the job."
Answer: 201694.0

User story: "Version being pulled in by ipykernel is old."
Answer: 207.0

User story: "Use simulated environments to test that changes made to HeaderService and salpytools and make sure no damage was done during updates to PEP8."
Answer: 10217.0

User story: "DM overview and status , a bit of LSST status as well."
Answer: 6177.0

User story: "As proposed in DM-13970, {{ap_verify}} should have a script that handles interaction between Jenkins (which should only need to know dataset names) and {{ap_verify}} itself. We should be able to model our script on {{validate_drp}}'s solution, although the standardized nature of {{ap_verify}} datasets may simplify the implementation."
Answer: 11696.0

User story: "Write summary for Monthly report"
Answer: 4696.0

User story: Run validate_drp/matchedVisitMetrics.py with w_2018_36's jointcal outputs.     The given example is this script: https://github.com/lsst-dm/jointcal_compare/blob/master/slurm/validate-calibration.py     An example I got out from the above script is   {noformat}  matchedVisitMetrics.py /datasets/hsc/repo/rerun/RC/w_2018_36/DM-15603-jointcal/ --output=/datasets/hsc/repo/rerun/RC/w_2018_36/DM-15603-jointcal/validate-jointcal/9813 -C=validate-jointcalConfig.py --id ccd=0..8^10..103 filter=FILTER tract=TRACT visit=VISITS  {noformat}  where `validate-jointcalConfig.py` is:  {noformat}  config.useJointCal=True  config.outputPrefix="validate-jointcal"  config.skipTEx=True  config.verbose=True  config.instrumentName="HSC"  config.datasetName="jointcal"  {noformat}
Answer: 6074.0

User story: "Create a notebook for Jeff to display every nth image comming into some dir."
Answer: 4.0

User story: "I would like to run the tutorial notebooks on the laptop using the docker images from sqre"
Answer: 6917.0

User story: "Get Dask (and spawning configuration) into JLD"
Answer: 51525.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: "Rewrote the GPFS mount check code to enable more robust handling of multiple file system mounts on a machine.  With the beginning of the Data Backbone File System (/dbb) and the likelihood of further file systems being created in the nearish future and not all file systems being mounted on all nodes intentionally, the check needed to be fortified to handle these additional constraints.  "
Answer: 15.0

User story: "Adding appropriate users and passwords; Authenticate client requests (telegraf); Authorize users with privileges"
Answer: 33118.0

User story: "Ping sweeps for responsive interfaces have been running on the public interfaces for a while on the LSST fabric, but a NIC failure serving an internal network brought to light the need to have alerts on that fabric as well.  Sweeps of this network have been implemented and are being monitored.  "
Answer: 33312.0

User story: "The OCS_Bridge has a very occasional need for a unique number from a sequence. Rather than including an OTS in-memory DB like the type that the python components use (Redis), or fabricate one, the OCS_Bridge could simply request a unique number from the DMCS via an internal message...as the DMCS has a scoreboard class specifically for number sequences. This would not be a resource drain or a possible introduction of latency, because these values would only be requested at startup, when the internal message network is at its most quiet.         This ticket, if pursued, has two parts; one is the addition of a simple handler for the new message in the DMCS, and the other part is the generation of the request in the OCS_Bridge and the handling of the response."
Answer: 20208.0

User story: "obs_subaru's config for forcedPhotCcd loads CModel, but CModel doesn't yet implement forced photometry when WCSs differ, leading to a fatal error when attempting to use {{forcedPhotCcd.py}} to do forced photometry on individual exposures. Use of CModel is disabled for forcedPhotCcd in ci_hsc, which demonstrates that it shouldn't be there in the first place."
Answer: 388.0

User story: "Add help anchor and ~2 lines of help text to hue preserving dialog.    Ask [~<USER> for wording.         Add scaling factor for each band. Scientifically natural UI would be a logarithmic slider for each band, going from 0.1 to 10.0, with 1.0 centered, and the default being 1.0  (no scaling)."
Answer: 49861.0

User story: "Write the test plan for milestone DM-SUIT-6,     LSSTCam data display and visualization    Dec. 12, 2019 update:    Test case LVV-T368 includes the test case for Firefly    * That results can be displayed in the Firefly display tool.    DMTR-112 covered testing the display with Firefly Python API firefly_client. "
Answer: 132494.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: Here is the user (Joe Mazzarella) description of the issue. Essentially the first attempt to load/display FF content   in a browser session fails. We have seen cases where the browser has cached an older copy of the Firefly startup JavaScript file, and references that, after finding that the expiration date (HEAD) on the server is unchanged, and   uses the cached copy. This is the reference to the "caching problem" I believe.    [[Note: The rc.ned (release candidate) and ned.ipac (operations/public) systems use the same IRSA ops instance of Firefly, and the same NED backend in this case.]]  {quote}In Chrome, when I try to compare results from RC with Ops, the infamous JavaScript caching problem appears.    Details: On the homepage, a search on 'M82' returns a message "SED Plot Loading..." with no plot. Likewise the Phot & SED tab contains no Firefly content (all three divs are empty.)  [https://rc.ned.ipac.caltech.edu/?q=byname&of=pre_text&list_limit=5&img_stamp=YES&hconst=73&omegav=0.73&obj_sort=RA%20or%20Longitude&omegam=0.27&extend=no&out_csys=Equatorial&objname=M82&corr_z=1&out_equinox=J2000.0]   Interestingly, the same query on Ops at the same time does return FF content:  [https://ned.ipac.caltech.edu/?q=byname&out_equinox=J2000.0&omegav=0.73&corr_z=1&hconst=73&objname=m82&out_csys=Equatorial&img_stamp=YES&of=pre_text&list_limit=5&obj_sort=RA%20or%20Longitude&omegam=0.27&extend=no]   When I run the same query on RC.ned in a separate browser, it works fine.   About 10:00-10:30 AM (20180804), Loy and Jeff looked at this on MY computer. They looked at the debugger/Inspector in Chrome. WE simply clicked the RELOAD button and the Firefly content did load.  {quote}  NED ENG-1072     
Answer: 888673.0

User story: "Stay current with JupyterLab/JupyterHub development"
Answer: 124044.0

User story: "Config inherits from UserDict and hence gets a lot of dict-like methods.   They don't all seem to work; {{get}} didn't until DM-15424, and {{del}} doesn't seem to work either, at least when nested below the top level.    We should probably add tests for all dict-like operations.    As an alternative, I've been working around these issues by just working directly with the {{data}} attribute, which really is a nested dictionary (with some lists).  I'm finding that much more pleasant.  Perhaps we should expose that more directly, and remove more of Config's implementation, i.e. make it so the children of a Config are not themselves expected to be Configs."
Answer: 2995.0

User story: "When FAULT is detected and Fault State is entered, a Summary State event should be issued. A Summary State event should also be issued when FAULT is exited via the ResetFaultState event."
Answer: 1040.0

User story: The test {{testReadFitsWithOptions}} in {{test_maskedImageIO.py}} assumes that {{afwData is available, so it needs a}}  {code:java}  @unittest.skipIf(dataDir is None, "afwdata not setup") {code}  decorator
Answer: 1138.0