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: "There are 3 messages streams in the code - Chat in fabric.proto, Chat in events.proto and Register in chaincode.proto.    All three streams are created more or less in the same manner (upon stream creation a handler object is created and from that point it handles all the stream communication) and all three lack a mechanism of user / applications level configurable flow control, only grpc level flow control.    The idea is to leave those handlers relatively unchanged, but instead of sending messages directly to the stream they will send messages to channels and some comm layer code will actually send them to the real streams. The same pattern will be used to handle incoming messages - instead of calling the handler handleMessage method directly after stream.Recv(), messages will be put in a channel and another go routine will call handler.handleMessage.    Handling messages in and out channels, go routines, etc will be placed in a separate module in core/comm package.    Gerrit: https://gerrit.hyperledger.org/r/#/c/535/  "
Answer: 306435.0

User story: "As application developer, I want an easy way to deploy and test my app by only having a single orderer process.    This refers to the 'Solo' ordering process.  This will be a simple to deploy, minimal code ordering process.  Because there is only one process, no 'consensus' need be reached between multiple processes, so this is largely as simple as having multiple clients write into a buffered channel, with a single thread reading it, and creating batches/blocks.    The deliver side is only slightly more complicated, as to allow for disconnection and reconnection, the orderer service must allow history to be discovered.  This requires implementing a simple in RAM ledger, and allowing individual clients to seek within it.  "
Answer: 30130.0

User story: "Story: Developer needs the ability to gain signatures from endorsers as defined by a policy by simulating a transaction without writing to the ledger create, so that they can submit a transaction.    Endorsers simulate tx with state and reply with rw set of all keys that were modified.    A submitter composes a transaction consisting of [header, payload, rw-set] where rw-set is the set containing the state variables that the transaction reads from (read-set) and the state variables that the transaction writes to (write-set). The rw-set is created via transaction execution simulation (not writing to database). This simulation is also done by the endorsers of the transaction to fulfill the endorsement policy of the transaction."
Answer: 107769.0

User story: "As an application developer, I want documentation for upgrade flows"
Answer: 847039.0

User story: "As a chaincode developer, I want use life cycle system cc to manage deployment policies for chain codes"
Answer: 354035.0

User story: "As an application developer, I want to provide friendly name to identify a chain code, so I can more easily manage and debug chain code."
Answer: 126970.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: "Developer must have the ability to manage the lifecycle of their chaincode, from beginning to end. So that they can modify, apply fixes and migrate her chaincode.    Chaincode lifecycle management    Description  Provide a way to manage chaincode lifecycle. Need for basic support of scenarios such as modify deployed chaincode, migration of chaincode (and activities such as backup of data related to it) etc.     We may also want to consider version support as part of this effort. Users can then start different versions of a chaincode but access the same data.This would go hand in hand with migration, maintenance, etc.    Justification  Developer: can modify deployed chaincodes "
Answer: 348886.0

User story: Copied from https://github.com/hyperledger/fabric/issues/748.    Summary:  Previous discussions have resulted in a decent foundation for providing trust in a network of chaincode. For instance, chaincode IDs are formed, in part, by hashing the underlying code. While this notion is critically important for certain use cases, it only becomes fully useful if the resulting hash can actually be traced back to the source for parties that may be interested in actually verifying an endpoint. In order to do that, there needs to be a few things:    1) a formal specification for how the chaincodeID is composed.  2) a query interface to allow an interested party to optionally ask for the decomposition.    Today, we form a chaincodeID by taking a few things such as the chaincode path, the ctor args, and a hash of the code, and hashing them together as a binary tuple. Technically, we could formally specify this schema to satisfy (1). However, it is suggested that something that provides schema management be used instead such that applications may pick and chose which fields they care about, ignore the ones they don't, and yet still be able to verify a hash.    Example: If we used a JSON document rather than the binary tuple, the specification could simply be chaincodeID=sha3(json), where json={"chaincode-hash":XXXXX, "path":YYYY, "ctor-args":ZZZZ, ... }, and a call like HTTP GET /chaincode/$id/decomposition could return the json. An application could then do validation on the fields they care about (probably primary "chaincode-hash") and yet still verify that the resulting chaincodeID is related by hashing the json document themselves.    I am partial to protobufs over raw JSON as far as schema declarations are concerned, but I am flexible as long as the basic criteria outlined above could be met.    
Answer: 1428596.0

User story: "Moved over from [issue-2169|https://github.com/hyperledger/fabric/issues/2169]"
Answer: 350036.0

User story: "barf"
Answer: 2.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: "Seems like we have a set of FAQs or at least a few specific repeated ones... some of these should probably addressed by more examples, tests and documentation, but for starters, we can also list a few of these in one easily accessible location, keep it updated and learn from it.    You can use this guide to help you identify and resolve basic problems you may be experiencing with the various configurations of Membership Services (enabling security, key length, registering more than once, etc...)    Later on, we can extend the basic structure and separate to sections, etc... but it'd be good to start with something as a baseline for improvement."
Answer: 339526.0

User story: "Currently, when the {{membersrvc}} binary is called, it expects a/the hardcoded `membersrvc.yaml` file.    I believe that it will be a lot easier both for *deployments* but certainly for *development* and *testing* if one is able to specify (dynamically, when executing/running/launching {{membersrvc}}) a location for the YAML file to use.    I can also see how this can help others when *reporting issues* (as one can simply upload the configuration file as part of the information needed for reproducing an issue/bug).    "
Answer: 47516.0

User story: "This Epic combines a set of (much needed!) improvements that are needed in order to make Membership Services easier to configure.    These are needed both statically (e.g., using the membersrvc.yaml file) or dynamically using CLI parameters at launch.  In addition, under the same bracket, while extending the configurability, we should also spend a cycle or two on 'house-cleaning', clearing up some of the tests data, and adding a lot more configuration related 'input validation' steps with clear(er)/informative error messages.    We should append/link more items here as we find them... so everybody, please feel free to pile suggestions/issues on."
Answer: 339568.0

User story: "Move various controllers into Controllers directory. Simplifies code structure."
Answer: 142.0

User story: "Adding read/write support for JSON to Config should be very quick and might help us make a decision on how to store the dimensions config in the database."
Answer: 426.0

User story: "Please add user {{<USER>} to the NCSA postgres access to the Gen3 RC2 database."
Answer: 189.0

User story: "The HVAC CSC so far only contains a simulator. Now that the HVAC MQTT server has been restarted, code can be added to connect to it. This ticket is for that."
Answer: 1602.0

User story: "Per discussion in DM-26685, for {{Registry.queryDatasets}} {{findFirst}} is a better description of the behavior for this argument than {{deduplicate}}, so it should be changed."
Answer: 3433.0

User story: "Robosimon (aka, mobu 1.0.3) has been such a hit let's put it on stable.  It just runs a small, so it shouldn't be taking a lot of load, and it only runs the prod notebooks."
Answer: 9.0

User story: "Update m1m3_sim container to build using new ts_salobj integration."
Answer: 1443.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 DM-26371 the graph API changed but the script for exporting a dataset from ci_hsc_gen3 was not updated. Fix it."
Answer: 4364.0

User story: "Perform an integration test with the IAU Minor Planet Center.    Rubin: Convert two weeks of simulated LSST observations for potential discoveries to ADES format.    Rubin: Submit simulated data set to the MPC.    MPC accepts/rejects simulated observations, fits and returns perliminary orbits and designations.    Rubin: Perform attribution of simulated observations with new orbits.    Rubin: close the loop by resubmitting attributed observations + potential discoveries of next night.    A report on the results of the integration test follows.     "
Answer: 3.0

User story: "The ESS CSC needs to be reverted to be compatible with the following software versions:    SAL v4.0.0  XML v 4.6.0  SalObj v5.3.0    This should be done on the Raspberry Pi at the BDC (base data center)."
Answer: 5297.0

User story: "In order to be able to use pylibftdi, libftdi is needed as well. This ticket is for adding that library to the RPi4 disk image."
Answer: 7531.0

User story: "Create child of QLabel, displaying time from last update in seconds/ms."
Answer: 5768.0

User story: "Wherever we're still using the wildcards, update 'em to the 2020-issued ones."
Answer: 8502.0

User story: "We saw this in one of the kafka-connect pods:    {noformat}  [2020-10-14 19:05:36,365] ERROR Encountered error engine: cache-max-memory-size exceeded: (1073761365/1073741824) (com.datamountaineer.streamreactor.connect.influx.writers.InfluxDbWriter)  {noformat}    It is a configuration on the InfluxDB side. Looks like we exceeded the  {{cache-max-memory-size}} which is set to 1G  - we are probably sending large volumes of data specially after the connector entered the UNASSIGNED state.    I think it is fine to set it to 0 to disable this limit."
Answer: 109.0

User story: "Try to integrate GraphQL with OWL.    Start with searching, expand to the other functions."
Answer: 9906.0

User story: "This task covers the time spent on the summit working on getting the M2 Server back online."
Answer: 6990.0

User story: Add the following endpoints to OWL:  * add: add a new message tied to an exposure  * delete: delete a message by setting is_valid=False and date_is_valid_changed to the current date  * edit: modify a message by copying an existing message, specifying which fields to change, setting parent_id to the old message, and "deleting" the old message (as above).
Answer: 10557.0

User story: "Currently the ingest tests take a long time because every single file that is ingested is also read back into memory (half the run time for obs_lsst ingest is doing this).  This is not testing ingest at all -- reading one dataset back tells you the formatter is probably working but you don't learn anything extra if you then read all the other files."
Answer: 5583.0

User story: "Move away from lsp-demo changed stripe ID."
Answer: 8750.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 IHS-4230 we realized that the filters registered for LSSTCam do not include empty second filter in the name but the metadata translator does include "~empty" because it uses code that is shared with LATISS.    Fix LSSTCam metadata translation to drop the second filter from the filter name if it is "empty".
Answer: 453.0

User story: "The renewed ESS CSC has not been tested yet at the Recinto because the thermal sensors appear to be offline. This ticket is for tracking the ESS test activities."
Answer: 13283.0

User story: "Now that the HVAC machine has been restarted, test the connectivity and verify that the MQTT server can be reached again and that it publishes telemetry."
Answer: 11482.0

User story: "1: update ospl.xml  2: add `LSST_DDS_PARTITION_PREFIX` with default value citest  3: make citest default for lab_dds_domain  4: replace hardcoded `net1` with `$LSST_DDS_INTERFACE` (and set that)"
Answer: 2667.0

User story: "The regression tests use the current branch information to compare different version of the code. But it depended on the `gitpython` package, which I didn't want to make a dependency, so I re-wrote the code to parse the git information in python. But my implementation was buggy so this ticket is to re-implement the working code using gitpython and add it as a docs build-only dependency (so that the stack and other python installs will not depend on it)."
Answer: 1457.0

User story: "Write some text to explain what lsp-deploy is and how it works."
Answer: 10013.0

User story: "Attend sessions"
Answer: 9042.0

User story: "ts_observatory_control is using some deprecated features from ts_salobj."
Answer: 11625.0

User story: "This task covers time to update and complete the unit test in ts_xml for verifying that string-type attributes are unitless.    Here is the PR:  [https://github.com/lsst-ts/ts_xml/pull/328]     "
Answer: 12.0

User story: "This ticket is to capture work originally under scope creep from DM-26702. We've redesigned the build pipeline a bit, and this adds parameters to salobj conda jenkinsfile to accommodate that, and passes them on to the next step of the pipeline."
Answer: 4367.0

User story: "In DM-27097 we are having difficulties with multiprocessing because in order to pickle RawIngestTask in that context we need to pickle the parent task. In general, ensuring that every parent task is pickleable is hard to do and it turns out that a task only needs its parent task to do some minor adjustments to internal configuration and does not use the parentTask at all other than when pickling.    Change pickling in Task so that it pickles the things it needs from the parent task but does not pickle the parent task."
Answer: 4665.0

User story: "Implement basic connectivity to a local PostgreSQL server to hold log messages, and to one or more local butler registries.  I do not intend to implement use of secrets at this point. I want to get some of the logic in place, first, then tackle that later."
Answer: 13020.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: "Deployment of HeaderService on the NTS with new OSPL and salobj 6"
Answer: 10096.0

User story: "The time has come: all environments should be their own independent snowflakes."
Answer: 5972.0

User story: "While having thoroughly characterized versions is nice, Java yanks old versions as they replace them, making it impossible to build with the current version from two months ago.    Retool our build process slightly to deal with this."
Answer: 5972.0

User story: "M1M3 GUI uses ts_sal, the old Python binding. It will be better to replace that with ts_salobj, the new, currently preferred Python binding."
Answer: 14701.0

User story: "The ci_hsc nightly builds only run on CentOS 7.  Given how frequently we run ci_hsc manually via Jenkins on all three stack-os-matrix targets, it seems like it shouldn't be a resource problem to also run all three in the nightly job."
Answer: 86.0

User story: "Quiet Friday is to be called focus Friday and we shall review at next DMLTf2f."
Answer: 387.0

User story: "Current fault states codes are 64bits (8 bytes) integer. This exceeds 32bit (4 bytes)  int type allocated in C/C++ to hold the states, causing problems when new code compares for fault code. The old code uses bitmask, which works fine as fault code is stored in lower 4 bytes.    Change codes to use only 4 bytes/32 bits."
Answer: 377.0

User story: "We should not have \gls \{} in the acronym entries in glossarydefs.csv (lsst-texmf).    They should all be removed and put in by generate acronyms.tex as appropriate i.e. scanning acronyms definitions as we do documents and marking them up at that point in time. This would also remove the suppression of \gls form the acronyms only runs."
Answer: 14334.0

User story: "In PREOPS-102 we were reminded that even though butler ingest-raws supports multiprocessing, butler convert does not. This inconsistency is causing slowdowns that will impact DP0.1.  For that reason I am calling this a Data Preview ticket."
Answer: 7818.0

User story: "To ensure backwards compatibility during the documenteer 0.6 transition, ensure that the original {{build-stack-docs}} CLI can continue to build pipelines.lsst.io without the Doxygen subsite."
Answer: 2874.0

User story: "For the point to point actuators in ts_simactuators all methods optionally accept a {{tai}} argument except stop. This allows one to shift time in unit tests. Add the missing argument to {{stop}} to complete the set."
Answer: 202.0

User story: "It seems to be permanently set to 2020-08-07, whereas (per comments in the source) it should be the date on which the document was most recently built."
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: "After DM-26529, generator specifications can refer to pre-generated data tables stored as CSV files. This is primarily used for the Visit table, which needs to span the entire survey and cannot be generated specifically for one chunk.    This file needs to be transferred and made accessible to all the worker clients. Since the files are small, this can probably done be via the same mechanism that transfers the generator specs."
Answer: 18575.0

User story: "Write the test framework of SAL LabVIEW API. This task begins to construct a framework to test the LabVIEW API for each new SAL update. In the past, we used the component CSC in LabVIEW to test this. Now, we need a framework to test this automatically. The SAL LabVIEW APIs rely on the shared memory, which is not needed for the C++ and JAVA APIs. Therefore, this kind of automatic test framework should be helpful for the maintenance of CSC in LabVIEW. This task is in the phase 3.    Based on Dave, I should use the {{LSST_TEST_LVDEBUG}} instead of {{LSST_Test_LVDEBUG}} to get the debug message. The CSC name should be capitalized in environment variables."
Answer: 9747.0

User story: "DM-26603 broke the daily build. This ticket is to fix this issue."
Answer: 59.0

User story: "Create docker environment to run M1M3 GUI."
Answer: 3007.0

User story: "Time spent coordinating, creating agenda, followups, reporting and  holding the weekly TMA Software Integration Meeting    Acceptance Criteria   * Agenda Generated and recorded into [https://confluence.lsstcorp.org/display/LTS/Weekly+TMA+Software+Integration+Meetings]   * Meeting held and action items recoded into the same confluence page   * Report sent out to the management"
Answer: 2929.0

User story: "This notebook was used in the past to manually send data from the SQuaSH API to an InfluxDB instance.    The code that transforms verification jobs in SQuaSH to the InfluxDB line protocol format was reimplemented in DM-18706 and moved exclusively to the SQuaSH API. It is executed automatically every time a verification job is sent to SQuaSH.     To preserve the functionality provided by this notebook, we can import the new code from the SQuaSH API and use it in the notebook instead.     The notebook narrative was also reviewed. It explains how the SQuaSH data model was constructed and how to use the new code better."
Answer: 6055.0

User story: "Design Postgres schema for the table holding observatory-wide logging messages.    Also:  * Get Postgres running locally  * Figure out how to run Postgres somewhere that the deployed system can access."
Answer: 1270.0

User story: "In IHS-4230 it was noted that if a file fails metadata extraction the entire ingest fails.    We need to have it ingest everything it can and then report the problematic files."
Answer: 1394.0

User story: "Update the developer guide page on Quiet Friday - this will now be Focus Friday    Also clarify that it will be asses in the next DMLTf2f"
Answer: 12600.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "When running a Pipeline it is sometimes desirable to run a subset of the labels, by specifying the list on the command line. Create a mechanism to do this."
Answer: 1386.0

User story: "Apparently we need to clear the astropy cache before we start.    https://ci.lsst.codes/blue/organizations/jenkins/sqre%2Finfra%2Faggregate-sal/detail/aggregate-sal/47/pipeline"
Answer: 1584.0

User story: "Per [discussion on Slack|https://lsstc.slack.com/archives/C2B6DQBAL/p1601472239035100]:  {code}  FileNotFoundError: [Errno 2] No such file or directory: '/j/ws/sqre/infra/documenteer/doc_template/_build/doctree/py-api/lsst.pipe.base.BuildId.doctree'  {code}"
Answer: 944.0

User story: "M1M3 simulator cannot be build be with develop-env:latest/b106. There are some strange dependency problems, which needs to be fixed so the simulator with latest .xml files (including changes of rejected* to preclipped*, see DM-26977."
Answer: 1523.0

User story: "To streamline small scarlet API changes that require modifications to the regression tests scripts in scarlet_extensions, we're moving all of the code necessary to run the regression tests into scarlet, allowing a single PR in a single repo to allow for updates."
Answer: 2939.0

User story: "After code changes in DM-26844, bpsub started printing bunches of warning messages like the following:   {code:java}  WARNING::10/02/2020 18:31:00::Missing search section 'payload' while searching for 'condor'  WARNING::10/02/2020 18:31:00::Missing search section 'pipetask' while searching for 'condor'  WARNING::10/02/2020 18:31:00::Missing search section 'site' while searching for 'condor'  WARNING::10/02/2020 18:31:00::Missing search section 'global' while searching for 'condor'    {code}"
Answer: 4078.0

User story: "Since the DSM is no longer configurable, the settingsAppliedSetup topic should be removed from the DSM XML."
Answer: 15809.0

User story: I just did some profiling of 2to3 conversion and noticed that the defects writing for HSC data is dominated by the normalization step that we don't need.  We can already assume that a defects file in a obs_*_data package is optimal so I don't think we need to normalize again on read.  From a quick test it took 59 seconds to read all 112 defects files but nearly 40 seconds of that was in the normalization.    The problem is knowing when to disable normalization since at the moment the readText method has no way to disable normalization and also the pipe_tasks code for reading from obs data packages would not really want to do an "if defects add special option"    One option is to declare that we never normalize when reading from fits or text file, and we only normalize if a Defects is being constructed directly. This would be a two line change to the constructor call in readText and readFits.    I'm inclined to go for that option since otherwise it's impossible to even see exactly what went into a file.
Answer: 382.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 repo for nublado 2 and get some kind of integration test working so we can have a cycle of improvement from the start."
Answer: 25937.0

User story: "Add a name parameter, and if the thing you're doing is running a notebook, derive the workflow name from the notebook name, not the harness name."
Answer: 4075.0

User story: "I'm not understanding something with the code [here|https://github.com/lsst-dmsst/metric-pipeline-tasks/blob/master/python/metric_pipeline_utils/matcher.py#L71].  My understanding is that if we are passing three parameters to that method, the third should be a flux error.  It looks like flux is being passed in both columns.  I could very easily be mistaken, but it looks like a bug as it is."
Answer: 5625.0

User story: "run_mtmount.py is broken with salobj 6: the simulate argument is defined twice.    The fix is to remove valid_simulation_modes from the CSC. This will make it compatible with salobj 5 and 6.    Also add a unit test that checks the bin script."
Answer: 227.0

User story: "The string fields in the softwareVersions event are limited to 16 characters, which is too short for some of our versions.    I suggest no limit, or if we must have one, a limit of 256.    Please consider removing the limits for all strings in SALGenerics.    I am happy to do the work. I anticipate the only difficulty being to get agreement on what limits to use, if any."
Answer: 93.0

User story: "Modernize the simulation mode support in ts_MTMount as per salobj 6.    and adding the version class attribute for a change to salobj in DM-27029."
Answer: 5506.0

User story: ts_salobj 6 adds a --version option to the command parser used by {{BaseCsc.amain}}. Unfortunately it returns the version of salobj, which is not what is wanted.    I suggest adding an optional {{version}} *class* attribute to CSCs; if present then add the `--version` argument in class method {{make_from_cmd_line}} (which is why it must be a class attribute) and also use it to set {{evt_softwareSettings.cscVersion}} in {{start}}.    Update the "how to write a CSC" documentation accordingly.
Answer: 1362.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: I just ran the template package (fresh git pull of master) to make a roundtable_aiohttp_bot app and ran into a few small issues:    * src/<name>/\_\_init\_\_.py adds "metadata" to \_\_all\_\_ but that symbol does not exist.  * There is an if statement based on Python version, but the two cases are identical (not a bug, but please consider simplifying the file to remove this).  * src/<name>/handlers/\_\_init\_\_.py adds "init_routes" to \_\_all\_\_ but that symbol does not exist.    I also see these issues in segwarides yet it runs, so maybe the two things I think are bugs are not. If they actually work then a brief comment explaining what is going on in the generated files would be appreciated. Certainly they make flake8 very unhappy.    Finally: the newly created files could not be committed because {{isort}} said some imports were out of order.  I used the package name "owl" in case that makes a difference.
Answer: 7112.0

User story: "In DM-22266, the {{pipe_analysis}} scripts are being converted to have the option of reading in the parquet files now being persisted via {{pipe_tasks}}'s  postprocessing.py script. For the coadds, we are reading in the {{deepCoadd_obj}} datasets (added on DM-13770), which consist of a single parquet file per patch that is a merge of the {{deepCoadd_meas}}, {{deepCoadd_forced_src}} and {{deepCoadd_ref}} tables for all filters for a given dataset. As such, these all follow the same column naming conventions as those in their {{afwTable}} equivalents (i.e. they do not follow the DDPD-ified naming conventions; those are persisted as the {{objectTable}} dataset). For the visit level qa analysis in {{pipe_analysis}}, we would like to follow a similar pattern, but using the parquet equivalent of the {{src}} catalogs. The dataset for these is {{source}} (added as part of DM-24062). However, the default in {{singleFrameDriver.py}} is to NOT persist these nor the DPDD-ified {{sourceTable}} versions. The latter got a config override in {{obs_subaru}}, so they do get persisted for HSC processing. While we may eventually move to only using the DPDD-ified tables, in the interim, having the parquet tables with the original column names is desired (especially for maintaining the ability to read in the {{afwTables}} for older repos that didn’t get the {{postprocessing.py}} step, so have no parquet output).    As such, the {{doSaveWideSourceTable}} config in {{singleFrameDriver.py}}, which currently defaults to {{False}}, will be also be overridden in {{obs_subaru}} to {{True}} so that these visit-level {{src}}-like parquet files will be available for future RC2 processing runs.    It will be for a future decision (and RFC!) whether any of the defaults should be changed in {{singleFrameDriver.py}} itself and/or if we move to using the DPDD-ified versions only."
Answer: 5794.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: "Support activities to develop a dome environment conditioning contract, to control the temperature during daytime. The activities include reviewing proposals, provide technical information to potential contractors, meetings with Rubin Observatory reviewers and contractors."
Answer: 16076.0

User story: "Support activities for the development of low level dome control software development by EIE contractor. The activities include organization and attendance to technical meetings, review of documentacion, enforce compliance to requirements of software implementations, plan timeline of deliverables, provide technical support and guidance during development."
Answer: 15903.0

User story: "lsst.ts.salobj.assert_black_formatted should exclude .git and similar.    It is using --exclude to exclude version.py, but specifying --exclude wipes out the standard excludes. Include them again."
Answer: 92.0

User story: "Release documenteer 0.6 to PyPI and to conda-forge. This is a critical step for adding documenteer to the stack's conda environment and finally integrating Doxygen with regular CI builds."
Answer: 8656.0

User story: "The OPSTN series is replaced by the RTN series. Only OPSTN-002 was ever distributed.    To implement this:   # Remove OPSTN-002 from the LTD system and search index   # Remove the homepage for OPSTN on [www.lsst.io|http://www.lsst.io/]   # Remove mention of OPSTN from lsst/templates"
Answer: 17.0

User story: "[~<USER> reports that he can't convert some DECam gen2 repos because the validity timespans overlap. [~<USER> determined that this is because in gen2 some calibration repos have a day gap in validity ranges and we were compensating for this by adding a day. This led to repos without a gap being incorrect.    The 2to3 tool should handle this case and assume that <=1 day means no gap."
Answer: 1816.0

User story: "Hi Chris, I'd like to start using the gen3 postgres registries in {{/project/hsc/gen3repo/README}}          Would appreciate necessary accounts and instructions on how to use them. Thank you. "
Answer: 456.0

User story: "test"
Answer: 17087.0

User story: "Datastore Checksum calculation is not used by anything but takes a significant amount of CPU time during ingest/put.    Turn it off by default."
Answer: 179.0

User story: "The {{compare*}} scripts from {{pipe_analysis}} compute the differences of various quantities between different data repositories.  To prepare for a future transition of {{pipe_analysis}} to using {{lsst.pipe.base.functors}}, it may be useful for a {{Functor}} to have a {{.difference}} method that allows you to pass two {{ParquetTable}} reference objects and have it return the difference in the calculations between the two.  "
Answer: 597.0

User story: "Modernize the documentation for the following packages:  * ts_hexapod  * ts_rotator"
Answer: 13238.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 rest of the stack now can use fcgm for calibration, the fakes insertion code has fallen behind in these calibration updates. Add a config option that allows the user to specify their preferred calibration type."
Answer: 10482.0

User story: "Update ts_hexrotcomm to wait for sockets to finish closing. The pattern is:    {code}  writer.close()  await writer.wait_closed()  {code}    Note that the wait sometimes raises asyncio.CancelledError (this appears to happen when the writer is already being closed, but I only see it on our Docker image; not running the same version of Python (3.7.6) on macOS. I think it's a bug in Python."
Answer: 10158.0

User story: "The {{lint}} environment runs black, isort, flake8 and flake8-docstrings. The {{coverage-report}} calls the current test runner in the SQuaSH API. Tests will be reviewed in DM-26979. Also replace Travis CI with GitHub Actions."
Answer: 2849.0

User story: "Configuration of static M1M3 FA data (xyz position, actuator ID, actuator type) is stored in configuration file. After installation, those data aren't supposed to change at all. It will be much better to move the values into a structure in source code, the same way LBTO organizes stores those values."
Answer: 11259.0

User story: "Ingest the SCTR series, hosted in the github.com/lsst-sitcom organization, into www.lsst.io."
Answer: 248.0

User story: One of the unit tests in ctrl_mpexec experiances random failures:  {noformat}  qexec = QuantumExecutorMock(mp=True)  mpexec = MPGraphExecutor(numProc=3, timeout=1, quantumExecutor=qexec, failFast=False)  with self.assertRaises(MPTimeoutError):  mpexec.execute(qgraph, butler=None)  >       self.assertCountEqual(qexec.getDataIds("detector"), [0, 2])  E AssertionError: Element counts were not equal:  E First has 0, Second has 1: 0  E First has 0, Second has 1: 2  {noformat}    This looks like timing sensitivity, with 1 second timeout it's likely that processes that should finish normally did not manage to do it. It's hard to make this much more reliable without much longer delays, probably OK to disable this test entirely.
Answer: 209.0

User story: Changes to bearer token usage:   * Read token from file instead of environment variable   * Pass token file path via a new environment variable    This allows the user to renew the token and replace it when necessary: until this feature is deployed, a long running job will fail at token expiration, with no possibility for the user to pass a new token.    Other changes:   * Improve webdav debug logs   * Avoid opening multiple sessions for consecutive requests   * Manage error 405 on mkdir to avoid race condition on folder creation when running parallel ingestion   * Add the possibility to enable "Expect: 100-Continue" header in requests, via environment variable   * Manage code 307 redirection in PUT requests (do not send data before we know what is the final destination)
Answer: 19751.0

User story: "Final push to test deployed releases on the NCSA Test stand"
Answer: 20049.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 DIMM CSC was created some time ago. Now that SALOBJ 6 is about to be released, the code needs to be migrated to that version. This ticket is for doing that."
Answer: 20401.0

User story: "The Environment (WeatherStation) CSC was created some time ago. Now that SALOBJ 6 is about to be released, the code needs to be migrated to that version. This ticket is for doing that."
Answer: 20402.0

User story: "In DM-25511 we did a lot of the work to get the Gen3 version of validate_drp running in Jenkins, but did not actually flip the switch to have it running in the nightly.  This ticket is to make that change happen."
Answer: 1407.0

User story: "Task to write the feature based scheduler driver for the scheduler CSC."
Answer: 20146.0

User story: "After a couple of weeks of intensive build work to make sure we got a stable system deployment configuration, it have left a couple of things behind in ts_cycle_build. I will take some time to implement a couple of these improvements in this ticket. The improvements I am planning on doing are:        * Write doc page for ts_cycle_build.   * Implement more features in the Jenkinsfile to allow cycle build to be done on Jenkis.   * Create a centos base image that does not contain conda for CSCs that don't require it, currently, M1M3 simulator and pointing component. "
Answer: 20525.0

User story: "MTMount is falling behind when run with its internal simulator, as shown by occasional delayed heartbeat events. Run the simulator in a different process to offload the main CSC."
Answer: 5493.0

User story: "Write the new nublado architecture document"
Answer: 8793.0

User story: "In the flurry of late-night merging for DM-26629, I forgot to do (at least) two things:   * I added one post-review feature commit to daf_butler to enable simple calibration lookups in {{butler.get}}.  This was used (and hence tested) in ci_cpp_gen3, but it merits tests in daf_butler and probably some additional documentation, as well as a review.   * I promised in the review to update some documentation in pipe_base about ButlerQuantumContext preconditions, and then forgot to actually do so.    Happily none of them involve schema changes (or even non-test code), so it's probably good that they just got deferred to another ticket instead of holding up DM-26629."
Answer: 3455.0

User story: "While converting {{datasetPtc}} to an {{IsrCalib}}, a {{toTable}} method was added. After creating a second {{Table}} (astropy) in that method, {{fromTable}} seems to fail to read it (it read the first table fine). This was seen when trying to open a FITS file with more than one table (i.e., at least 3 HDUs) with {{readFits}} (parent class: {{calibType}}). "
Answer: 19519.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: "Find a place to save our Kapacitor scripts for alert rules on github.    This is important for history, and because the rules are easy to corrupt in the Kapacitor interface.    A subdir of Watcher would probably suffice.  Note that the scripts are going to be different for the different sites (summit, NCSA teststand, etc.): the destination will be different and the EFD identification may also be different."
Answer: 4192.0

User story: "From discussion on DM-26937 I learned that the newer imsim data have an AIRMASS header (and AMSTART). Use that header in the translator and only use the altaz values if the header is missing.    I don't think this change will speed up DM-26937 because the altaz has to be calculated anyhow for the zenith angle."
Answer: 5672.0

User story: "The task used by ingest-raws can support multiprocessing but the command line can't supply it. Add the option."
Answer: 4299.0

User story: "Overlooked creating a unquie id that is unique across all tracts. Will add a use uuid4 for this purpose."
Answer: 7179.0

User story: "We are going to want to ingest a lot of raw files so we should profile raw ingest to ensure there are no obvious slowdowns.    testdata_lsst has 450 files and I have a copy locally so first try with that.    Checksum calculation should be disabled (and possibly I should make that the default)."
Answer: 5764.0

User story: "Financial Reporting for October 2020  This ticket had been created automatically Primavera ID: None"
Answer: 38695.0

User story: "DM-26738 changed the name of {{abstract_filter}} to {{band}}.  We need to update all mention of {{abstract_filter}} to {{band}} in the [metric-pipeline-task|https://github.com/lsst-dmsst/metric-pipeline-tasks] repository."
Answer: 4326.0

User story: "Includes removing now-unused old-pipetask code."
Answer: 16175.0

User story: "The issues is described here:  https://gitlab.com/pycqa/flake8/-/issues/583    Flake8 ignores should be on both the decorator line and function line to support python 3.7 and 3.8 for an interim period."
Answer: 19032.0

User story: "Mark obs_ctio0m9 as deprecated for Pipelines release 21.0.0."
Answer: 15608.0

User story: "Support unit testing for instances of CscCommander    and add unit tests for CscCommander."
Answer: 248.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: Follow-up on some oddities from per-visit differences from run to run with {{fgcmcal}} on RC2 (thank you [~<USER>!) revealed that there were some problems with outlier rejection in the {{fgcm}} code.  Initial investigation led me to realize I could add some additional "full focal plane" outlier rejection on a per-visit basis that would be very robust, which is implemented on this ticket, and that is certainly helpful.  This then led me to the realization that the final "gray" zeropoint correction could be done much more robustly per visit rather than per ccd.  Finally, some additional oddities in some visits led me to find a bug in {{fgcm}} such that bad reference stars were not always masked out, and could therefore contaminate certain post-fit measurements.    Tests on the {{w_36}} version of RC2 from the changes on this ticket yield significant improvements in the internal repeatability metrics within {{fgcm}}, reducing the bright source repeatability from 5-6 mmag to 3-4 mmag. 
Answer: 22888.0

User story: "Used in more than one place now, so wants to live somewhere central."
Answer: 1.0

User story: "Write a tech note proposing an approach to network encryption of telescope data."
Answer: 30379.0

User story: "> one or two pager on what is needed for next step testing, in cloud context (what sorts of nodes, with what sorts of storage/mem/cpu, and procured for how long to do the testing)"
Answer: 1826.0

User story: "Once DM-26600 adds the ability to remove a dataset type, we will need a butler subcommand to make it usable from the command line."
Answer: 10178.0

User story: "Fix ts_standardscripts use of get to explicitly flush if needed."
Answer: 45.0

User story: I get errors testing astshim with pybind11 2.5.  {code}______________________________ ERROR collecting tests/test_rateMap.py ______________________________  ImportError while importing test module '/lsstsw/build/astshim/tests/test_rateMap.py'.  Hint: make sure your test modules/packages have valid Python names.  Traceback:  tests/test_rateMap.py:6: in <module>      import astshim as ast  python/astshim/__init__.py:43: in <module>      from .fitsChanContinued import *  python/astshim/fitsChanContinued.py:3: in <module>      from .fitsChan import CardType, FitsChan, FitsKeyState  E   ImportError: generic_type: type "FitsKeyState" is already registered!  {code}  Note that FitsKeyState is an "enum class" type, and includes an export_values() call in the declaration for pybind11.      There is a note in the developer guide about using .export_values with that type, which I'm not sure if it's applicable in this instance, which reads:     Add .export_values() if (and only if) you need to export the values into the class scope (so they can be reached as ExampleOne.RED, in addition to ExampleOne.State.Red).    Never do this for new style scoped enum class types, since that will give them different symantics in C++ and Python.
Answer: 2596.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: A BPS configuration class can already be initialized with a dictionary. However, this dictionary was implemented to not have the actual config values themselves, but rather provide information about how to construct the config, e.g., location of the config file, a flag whether to get default site values from a database, etc. The goal is to modify the initialization part of the class to allow one to pass in a dictionary of values. It will make testing easier and is a more natural use of passing in a single dictionary.  The "how to construct the config" capability will be removed for now and added later if we ever need it. 
Answer: 12905.0

User story: "In DM-22698, DM-23094, and DM-22461 we incorporated Doxygen builds for Pipelines docs directly into Documenteer, migrating away from our dependency on sconsUtils and lsstDoxygen. This included consolidating the Doxygen configuration, while still allowing individual packages a limited vocabulary of Doxygen configuration tags to include or exclude specific paths from the documentation.    We've discovered, though, that the {{base}} package actually plays a special role in providing configuration defaults beyond those coded into sconsUtils.    Thus in this ticket we will port base's configurations into documenteer and expand documenteer's Doxygen configuration facility to handle these new tags."
Answer: 11852.0

User story: "Follow standard procedures for updating the main branch with two commits that were prepared for the rc2 branch."
Answer: 522.0

User story: "Currently return codes are being swallowed by the scripts that wrap up the various steps in the Gen3 {{validate_drp}} scripts.  I think we probably want to make sure the return code from the processes is returned by the script."
Answer: 18782.0

User story: "If we intend to continue using obs_ctio0m9 and the related CI package, we need to port it to Gen3. This means:    * Write astro_metadata_translator translator  * Write an Instrument class and Formatter    Please close as Won't Fix if no-one cares and people are okay with removing the obs package. I don't think we've formally deprecated it but I might be wrong.  I'm assuming this ticket is not a blocker on DM-DAX-12."
Answer: 11742.0

User story: "The tooling we wrote in DM-25507 only sent on the abstract filter in the {{filter_name}} metadata field.  SQuaSH treats this field as special and assigns the value in that field to the {{filter}} tag which is used by dashboards to filter results.  Existing dashboards assume that tag has the name of the physical filter.  In order to be consistent with that assumption, change the value assigned to the {{filter_name}} field to be the best guess at the physical filter.  It's useful to still send on the abstract filter name since it doesn't cost much."
Answer: 57.0