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: "A new tag for {{3.10.0-4.3.0.el7}} for the sal rpms has been released. This new ts_xml version {{4.3.0}} contains several elements of new metadata that the HeaderService need to create full consisent headers. A new environment both in Docker and NCSA Test Stand need to be re-deployed."
Answer: 25841.0

User story: "A new tag for {{3.10.0-4.3.0.el7}} for the sal rpms has been released. This new ts_xml version {{4.3.0}} contains several elements of new metadata that the HeaderService need to create full consisent headers."
Answer: 7162.0

User story: "DM-20265 introduced analytic Jacobians for fitting Gaussian mixtures in MultiProFit. I accidentally broke this by not raising when the validation (comparison with finite differencing) fails, and also by failing more often than it should by using only positive deltas (which doesn't work when a parameter is at or very near its upper limit)."
Answer: 40556.0

User story: "Document needs in a project-accessible location."
Answer: 40187.0

User story: "There is an issue preventing the Java tests from working correctly.     This task is to record my steps along the way on a confluence page to reproduce these issues. "
Answer: 36037.0

User story: "Write a conda development guide and procedure."
Answer: 11667.0

User story: "This task is to cover the time spent preparing and going through 3 seperate interviews. One is for a documentation position, a software engineer and a senior software engineer."
Answer: 1228.0

User story: "After looking at the outputs of the fgcmcal-tract calibrations (DM-20161) that were coadded on DM-21308 and analyzed on DM-21309, it is clear that the cosmos tract 9813 is not performing as well as I would like. Investigations on DM-21482 showed that this is because of the lack of aperture corrections in the tract mode.    The decision not to explicitly implement the aperture corrections was done because they wouldn't necessarily be internally calibratable, and because I thought they would come out with the wash.  I was clearly incorrect on the second part.    In this ticket I will investigate whether the aperture corrections can be calibrated reliably within the tract mode for RC2 data, and if so, simply turn that on.  Alternatively, I can use the aperture corrections calibrated from PDR1 (for example) and use that as a configuration parameter."
Answer: 32855.0

User story: "During live testing, meta data for NAXES are wrong and this ticket fixes that."
Answer: 2957.0

User story: "Using the more resent HSC-RC2 rerun (w_2019_38 from DM-21386), run the as-is post-processing tasks to generate the Object tables in Parquet format.      Convert them into csv format (standard panda tools is fine for now).    Avoid duplicate columns. "
Answer: 11894.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: "[sealed-secrets|https://github.com/bitnami-labs/sealed-secrets] provides a way of encrypting secrets with a private key that's only available from the Kubernetes cluster. This provides an easy way to securely commit secret resources for a Kubernetes deployment into a Git repository (such as for Roundtable's Argo CD-based workflow). This is similar to how Travis CI lets you encrypt secrets and commit those encrypted secrets into the repo's {{.travis.yml}} file.    Note that a better alternative is to use LSST's centralized Vault, but at the moment we haven't figured out the right workflow for Roundtable-based apps to use Vault."
Answer: 6159.0

User story: "The TLS certificate for keeper.lsst.codes is scheduled to expire on October 8th 2019. Since Roundtable provides Let's Encrypt-based certificates, it makes sense to relocate the LTD Keeper deployment there.    This means that LTD Keeper should be deployable as a Helm Chart or Kustomize manifest (Kustomize is likely to be easier in the near-term)."
Answer: 6255.0

User story: "In DM-21118 we deployed Strimzi as the basis for Roundtable's Events service. Strimzi enables us to use mutual TLS for authenticating (and authoring) clients of the Kafka brokers.    Now we'd like to deploy Confluent's Schema Registry service for Avro schemas. This is an integral part of the Events service.    Unfortunately the Schema Registry Helm chart does not provide an easy way to load the TLS certificates generated by Strimzi for clients.    I think an ideal solution for bringing the Schema Registry into a Strimzi-based Kafka deployment is to create a Kubernetes Operator for Schema Registry that is specifically capable of getting the TLS certificate, converting it into a format usable by the Schema Registry, and then deploying the Schema Registry to use that certificate.    A python framework for building Kubernetes operators is https://kopf.readthedocs.io/en/latest/"
Answer: 43608.0

User story: "begin lab testing with chiller and white light source, plus address issues we discover"
Answer: 38608.0

User story: "This ticket is to perform the regular monthly reprocessing of the HiTS dataset."
Answer: 49047.0

User story: "Create setup.py script for dm_ATArchiver"
Answer: 18773.0

User story: "After looking at the outputs of the fgcmcal-tract calibrations (DM-20161) that were coadded on DM-21308 and analyzed on DM-21309, it is clear that the cosmos tract 9813 is not performing as well as I would like.  I need to investigate why the fgcmcal calibrations are not converging properly."
Answer: 93838.0

User story: "Use the gains from ticket DM-18052, and use them to correct a flatfield (or whatever we have that's closest to one in the configuration that this data was taken in) and check to see how good the continuity across amp boundaries. "
Answer: 232043.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "It would be very helpful for the telescope and site developers if we could have the same branch & PR auto-linking to Jira that happens for the DM github group. Could you please configure Jira to link to the {{lsst-ts}} group on github?"
Answer: 12608.0

User story: "Run test integration using the salobj version of the ATArchiverCSC, the Forwarder and the ArchiveController.       This test should deposit files in the forwarder staging area, and create hard links to the DBB and OODS staging areas.    Once this first test is complete, the second test will be to run the OODS ingest generated files into the Gen2 Butler."
Answer: 211507.0

User story: "Recent infrastructure work broke {{insertFakes.py}} (see, for instance, the misspelled import statement at line 35    [https://github.com/lsst/pipe_tasks/blob/master/python/lsst/pipe/tasks/insertFakes.py#L35]    This happened silently, because there are no unit tests that exercise this code.    This ticket is to fix the parts of the code that have been broken and then add a unit test so that the code cannot break silently again."
Answer: 112467.0

User story: "The current workflow in the DM project is a free-for all from any state to any state. This means that the button at the top of the ticket which is supposed to show the next step along in the workflow rarely does the right thing. The fix is to make an actual workflow.     No statuses will be changed. I anticipate the only controversial aspect is whether to allow a route from In Progress to Done without passing through Review. On the basis that anything is going to be an improvement on the current situation, I propose to allow it for now and y'all can decide what to do later. "
Answer: 17455.0

User story: "Write a simulator for the vendor's MT hexapod and rotator TCP/IP interface and code that talks to it. Test it on real hardware.    This will help inform the total time required to write a simulator for these devices and the best approach to such a simulator."
Answer: 17313.0

User story: "Now that we are using devtoolset-8 everywhere we need to update the developer guide and pipelines.lsst.io."
Answer: 7142.0

User story: "Please add the {{moto}} python module to the telescope and site docker container, so that we can use it to unittest the salobj code that will write to the newly-planned LFA. It is pip-installable.    https://github.com/spulec/moto"
Answer: 14289.0

User story: "In this task, I will begin to update the ts_MTAOS to use the salobj 5.0. It is working with salobj 3.x right now. At this moment, I have only the salobj 5.0.RC.2 (RC: release candidate). The configuration file should be put in ts_config_mttcs."
Answer: 20397.0

User story: "I this task, I will test the TCP/IP message from middleware code in the googletest framework. The unit test of function will be implemented as well. I also need to make the Makefile can be switched between production and development modes."
Answer: 10429.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: "Tests related to generating quantum graph pickle files based on a HSC-RC2 registry on AWS-RDS. "
Answer: 43020.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: "Currently, forwarder has hard-coded values for raft and ccd. Those values should come from ATArchiver so that ATArchiver can tell forwarder to pull a dynamic raft - ccd.     "
Answer: 7311.0

User story: The DCR multiband coadd source detection and measurement tasks (DM-14553) appear to be broken when running on lsst-dev. {{detectCoaddSources.py}} runs fine for a normal {{deepCoadd}} but fails with the following error message when run on a {{dcrCoadd}}. The problem appears to be the warning: {{root WARN: Unexpected ID subfilter; guessing type is "str"}}    {code:}  CameraMapper INFO: Loading exposure registry from /project/<USER>hits2014/ingested/registry.sqlite3  CameraMapper INFO: Loading calib registry from /project/<USER>hits2014/ingested/calib2/calibRegistry.sqlite3  CameraMapper INFO: Loading calib registry from /project/<USER>hits2014/ingested/calib2/calibRegistry.sqlite3  root WARN: Unexpected ID subfilter; guessing type is "str"  root WARN: Unexpected ID numSubfilters; guessing type is "str"  root INFO: Running: /project/<USER>code/pipe_tasks/bin/detectCoaddSources.py /project/<USER>hits2014/dcrcoadds_processed --output /project/<USER>hits2014/dcrcoadds_processed --id filter=g subfilter=0^1^2 numSubfilte  rs=3 tract=0 patch=17,11^17,12^17,13^17,14 --config coaddName=dcr --clobber-config --clobber-versions  WARNING: You are using OpenBLAS with multiple threads (24), but have not  specified the number of threads using one of the OpenBLAS environment variables:  OPENBLAS_NUM_THREADS, GOTO_NUM_THREADS, OMP_NUM_THREADS.  This may indicate that you are unintentionally using multiple threads, which may  cause problems. WE HAVE THEREFORE DISABLED OpenBLAS THREADING. If you know  what you are doing and want threads enabled implicitly, set the environment  variable LSST_ALLOW_IMPLICIT_THREADS.  detectCoaddSources FATAL: Failed on dataId=DataId(initialdata={'filter': 'g', 'subfilter': '0', 'numSubfilters': '3', 'tract': 0, 'patch': '17,11'}, tag=set()): RuntimeError: Failed to format 'dcrCoadd/%(filter)s%(subfilter)  dof%(numSubfilters)d/%(tract)d/%(patch)s.fits' with data DataId(initialdata={'filter': 'g', 'subfilter': '0', 'numSubfilters': '3', 'tract': 0, 'patch': '17,11'}, tag=set()): %d format: a number is required, not str  Traceback (most recent call last):    File "/software/lsstsw/stack_20190330/stack/miniconda3-4.5.12-1172c30/Linux64/obs_base/18.1.0-18-gb5d19ff+1/python/lsst/obs/base/cameraMapper.py", line 922, in _mapActualToPath      return template % transformedId  TypeError: %d format: a number is required, not str  {code}
Answer: 1499.0

User story: "There seems to be an duplicate sdssCentroid plugin run in ip_diffim. This ticket will remove it."
Answer: 17266.0

User story: "{{ParseTask.getInfoFromMetadata}} does not handle the case that a header value is present but undefined, leading to errors such as {{TypeError: float() argument must be a string or a number, not 'NoneType'}}."
Answer: 10205.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: "From #dm-middleware on slack:  {quote}I'd like to get Datastores using the new schema stuff I added recently (TableSpec/FieldSpec) for anything they want to keep in the registry database, and I want to stop using a dict interface, as it's hard to map __setitem__ to insert and update, especially for bulk operations.  I'm thinking of:   * Removing DatabaseDict and DatabaseDictRecordBase entirely.   * Add abstract methods to StoredDatastoreItemInfo to translate to/from dictionaries that correspond to records to be saved.   * Moving the logic for inserting and retrieving StoredDatastoreItemInfo from the database directly into GenericDatastoreBase.  That would probably be _insert_info and _fetch_info methods that replace _info_to_record and _record_to_info.   * Overriding _insert_info and _fetch_info in InMemoryDatastore to save into a dict instead of letting GenericDatastoreBase's implementations write to the database.{quote}"
Answer: 41621.0

User story: "We're going to need a REPLY_QUEUE field in the message in the FILE_TRANSFER_COMPLETED message so that ArchiveController knows which queue to reply on.   We can't rely on the Forwarder reply queue which the ATArchiver knows about after startIntegration, because that particular forwarder might always be the thing that talks to the Archiver gets messages from;  it could be something else later."
Answer: 7457.0

User story: (Previous title was "Refactor DatasetRef into multiple better-defined classes", but now we're changing DatasetRef).    The current DatasetRef has too many fields (provenance stuff we never use), too many states (whether or not it has a {{dataset_id}} _completely_ changes what it represents), and ill-defined comparisons.  It's almost-but-not-quite immutable, which makes it tempting but a bit dangerous to use as the key type in a set or dict.     
Answer: 108515.0

User story: Once Patrick sends the serial numbers of the spectrographs and their "names" (e.g. MTRed: "1234567"), we can figure out which SAL index corresponds to which serial number, and have the CSC use the index to connect to the correct device.    [~<USER>: might as well attach the serial number information/photos to this ticket.
Answer: 31717.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "We are getting two different errors that kill the InfluxDB connector, while we are trying to understand the cause and then handle these exceptions in the connector, we can improve the current situation by automatically restarting the connector if it stops running.    this happened on 2019-09-24 06:32:36 UTC  {noformat}  java.lang.RuntimeException: org.influxdb.InfluxDBIOException: java.net.ConnectException: Failed to connect to influxdb-influxdb.influxdb/10.43.78.18:8086  {noformat}      and this hapenned on  2019-09-25 05:35:10 UTC    {noformat}  Caused by: org.apache.kafka.connect.errors.DataException: lsst.sal.ATPneumatics.ackcmd      at io.confluent.connect.avro.AvroConverter.toConnectData(AvroConverter.java:103)      at org.apache.kafka.connect.runtime.WorkerSinkTask.lambda$convertAndTransformRecord$1(WorkerSinkTask.java:514)      at org.apache.kafka.connect.runtime.errors.RetryWithToleranceOperator.execAndRetry(RetryWithToleranceOperator.java:128)      at org.apache.kafka.connect.runtime.errors.RetryWithToleranceOperator.execAndHandleError(RetryWithToleranceOperator.java:162)      ... 13 more  Caused by: org.apache.kafka.common.errors.SerializationException: Error deserializing Avro message for id 247  {noformat}    the last one seems to be related with the rebalance happening on the broker:    {noformat}  [2019-09-25 05:32:23,887] INFO [GroupMetadataManager brokerId=0] Removed 0 expired offsets in 65 milliseconds. (kafka.coordinator.group.GroupMetadataManager)  [2019-09-25 05:32:25,933] INFO [GroupCoordinator 0]: Member connect-1-069a8f18-bac1-4588-a940-ace48b747bbd in group cp-helm-charts has failed, removing it from the group (kafka.coordinator.group.GroupCoordinator)  [2019-09-25 05:32:25,936] INFO [GroupCoordinator 0]: Preparing to rebalance group cp-helm-charts in state PreparingRebalance with old generation 3 (__consumer_offsets-42) (reason: removing member connect-1-069a8f18-bac1-4588-a940-ace48b747bbd on heartbeat expiration) (kafka.coordinator.group.GroupCoordinator)  [2019-09-25 05:32:25,937] INFO [GroupCoordinator 0]: Group cp-helm-charts with generation 4 is now empty (__consumer_offsets-42) (kafka.coordinator.group.GroupCoordinator)  [2019-09-25 05:35:03,698] INFO [GroupCoordinator 0]: Preparing to rebalance group cp-helm-charts in state PreparingRebalance with old generation 4 (__consumer_offsets-42) (reason: Adding new member connect-1-6ceaf43a-310a-4be4-9ea5-e1527bdb1ccd) (kafka.coordinator.group.GroupCoordinator)  [2019-09-25 05:35:06,699] INFO [GroupCoordinator 0]: Stabilized group cp-helm-charts generation 5 (__consumer_offsets-42) (kafka.coordinator.group.GroupCoordinator)  [2019-09-25 05:35:06,702] INFO [GroupCoordinator 0]: Assignment received from leader for group cp-helm-charts for generation 5 (kafka.coordinator.group.GroupCoordinator)  {noformat}      "
Answer: 22985.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Now that we have a JL-1.0-based prod build, figure out what broke in Dask 2.0 and get it fixed.  [~<USER> needs newer Dask for his work, and helpfully has the ear of someone at Quansight who has the ear of Matt Rocklin."
Answer: 79413.0

User story: "DM-17023's addition of import/export functionality included a test that is intended to be run only on PosixDatastore-backed butlers, because that's the only datastore that implements export at present.  However, the S30-backed butler test class inherits from the PosixDatastore-backed test class, so when the (optional) moto/boto3 dependencies are present, the import/export test is attempted there, too, and fails.    The right fix appears to be changing the inheritance relationship so that S3 and PosixDatastore butler tests both inherit from a common base class, mirroring the inheritance relationship of the datastore classes themselves."
Answer: 1360.0

User story: "Test an instance of the Alert Distribution system-- running a payload through the distribution system to test the configuration so that development against this system can proceed. This could be something like recreating relevant portions of LDM-503-05."
Answer: 242263.0

User story: "Set up bare-metal instance of Kafka for testing the Alert distribution system."
Answer: 119731.0

User story: "ci_hsc_gen2 includes a check that the package provenance recorded by the CmdLineTask machinery includes a few packages, and that list includes wcslib.  Since our own WCS classes now use AST instead, whether wcslib appears depends on whether other optional stack packages that still use wcslib are set up, and that makes this test fragile."
Answer: 372.0

User story: "Obtain the Kafka EFD bundle from SQuaRE; instal and test it on the NCSA test stand. Understand internal workings and how it relates to database issues."
Answer: 242272.0

User story: "Remove the hard-coded data in middleware by Moog. Consider to add the configuration file. Use the path variable is also a solution. Need to check the yaml support in c language."
Answer: 9740.0

User story: "Setup two DIMM CSCs on tower DIMM server."
Answer: 129237.0

User story: The {{frame=}} arg has been removed from {{afwDisplay.Mosaic.makeMosaic}}.    {quote}<USER>17:30    Use    disp = afwDisplay.Display(frame)  mos.makeMosaic(display=disp, title="Kernel Basis Images")  {quote}
Answer: 29019.0

User story: This ticket will design and create the machinery necessary to define "top" level workflow pipelines and their associated configurations. This is envisioned to be a set of tasks commonly run together in a manor similar to how pipe_drivers currently groups tasks. However, this is not intended to be tied to concrete tasks in the way pipe_drivers is, but a framework for users to specify processing pipeline definitions so that they can be reusable and revision controlled.    Jim and Andy I am adding you as watches so that if you have any thoughts on this you can comment.
Answer: 65231.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 the future, we'll record EFD data in multiple stores like InfluxDB, Oracle, Parquet etc    Kafka replicates data using connectors, right now the decision of which timestamp is used as the InfluxDB time is done in the connector configuration, by a KSQL query:    {code}  INSERT INTO mytopic SELECT * FROM mytopic WITHTIMESTAMP private_sndStamp  {code}    a similar configuration would be done in the Oracle connector to define which timestamp field should be indexed.    To avoid making this decision in different connectors and potentially in different deployments of the EFD, the definition of which timestamp to use in the EFD should be done in the SAL Kafka Producer instead.     There are different ways to accomplish this.    The easiest one is to create a new field in the Avro schema called, for example, {{private_efdStamp}} which is a copy of whatever timestamp field we should use. Initially, that can be hardcoded to use {{private_sndStamp}}.    The other way is making use of "aliases" in Avro:    https://avro.apache.org/docs/1.8.1/spec.html#Aliases    that create an alternate name {{private_efdStamp}} for the timestamp field we want to use.     NOTE: we assume aliases work the way we expect but that needs to be tested. In the above KSQL query {{SELECT * FROM mytopic}} ensures that all fields in {{mytopic}} will be inserted as fields in InfluxDB with their original names and  {{WITHTIMESTAMP private_efdStamp}} will use the alternate name to use the right timestamp as the InfluxDB timestamp.    Either way, the different connectors always use {{private_efdStamp}}.    Another benefit of doing this in the SAL Kafka producer code or in the Avro schema is that changes to the code or to the Avro schema are versioned, while changes in the connector configuration are not.     This ticket is not blocking anything in the moment. But having the {{private_efdStamp}} would make the EFD configuration more realiable.
Answer: 43435.0

User story: "Moving into new office, shipping memo from tucson arrived. Moved computer into room. Drove to sodimac to buy adapters to make things work.    Tried getting internet on desktop to work via a usb adapter since desktop only has ethernet. Was running into compilation errors from the adapter driver software.     Tried moving desktop downstairs to connect via ssh instead, having troubles with this as well. Julio has been trying to resolve why and getting into contact with Joseph cockrum who installed originally network adapters.     Ethernet is being installed within a week or two so I don't think more time is spent on this on focus on other tasks meanwhile internet comes online for the second floor. "
Answer: 1443.0

User story: "LCR-1425 added new requirements to the DMSR. These requirements have recently been pushed to the Jira LVV project. Corresponding test cases (LVV-T) skeletons should be created.    The relevant Verification Elements are:    LVV-18222    LVV-18223    LVV-18224    LVV-18225    LVV-18226    LVV-18227    LVV-18228"
Answer: 362916.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: "Update AOS package to use the scientific pipeline w_2019_38. This is a preparation to update ts_MTAOS to use the salObj 4."
Answer: 10313.0

User story: "We need to do this before DM-17023 lands or the nightly ci_hsc builds (which are still running the old ci_hsc package) will be broken.    Only tricky bit is the question of how gracefully LFS handles being removed from the master branch of a repo."
Answer: 242.0

User story: "Clean up as-is scripts/command lines used for running HSC-RC2 jobs and upload them to https://github.com/lsst-dm/gen2-hsc-rc2"
Answer: 34522.0

User story: "According to its table file meas_astrom still depends on astrometry_net even though that dependency was removed in DM-2186.  "
Answer: 1128.0

User story: "Add missing unit tests for C++"
Answer: 53074.0

User story: "This ticket is to implement the background handling changes approved in RFC-630"
Answer: 4458.0

User story: "DMTN-82 makes the initial proposal on how the EFD data would be available for the Science Platform. In SQR-029, we prototyped our EFD solution based on Kafka and InfluxDB. In SQR-031 we deployed the EFD at the lab in Tucson and at the Summit supporting AuxTel tests.    In this technote, we'll detail the EFD operations, which includes the data flow from the Summit to LDF, data replication, fault tolerance, data retention policies and formats to store the raw EFD data for the lifetime of the experiment."
Answer: 26022.0

User story: "Continue generation of XML files needed to control the HVAC system. The new files consist of the events and commands. For the events, an analysis will be performed on the actions to be taken associated with alarms in the system."
Answer: 23483.0

User story: "Branch to put our very rough draft on. Will contain our rough notes and minutes, which aren't ready for https://dmtn-126.lsst.io/ yet.   "
Answer: 161861.0

User story: "Go through the TMA Action tracker list that Sandrine and others have been working on.     Continue with the action items that have been assigned to me. "
Answer: 7156.0

User story: "Rob pike suggested a short write up for google to see if we can make a deal .."
Answer: 25587.0

User story: Adding on the useful command line tool {{pipetask qgraph --show graph --qgraph pickle}}  I extended it a bit to show the quanta's input/output URIs based on a given Butler repo and also show the quanta dependency.  The outputs contain information of a basic workflow and can be provided to any workflow system (with format translation as necessary), or at least I find it useful to examine small quantum graphs.     In principle this could be a standalone script, but it could reuse the command line framework in ctrl_mpexec without adding new dependencies. It does complicate the "show" feature though.
Answer: 30035.0

User story: "Dask 2 has given us a lot of trouble.  If we could release something based on a new jupyterlab with an old dask it might be worth doing."
Answer: 6989.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Reprocess the HSC RC2 dataset, as defined in DM-11345, using Stack w_2019_38.     pipe_drivers / pipe_tasks  # {{makeSkyMap.py}}  # {{singleFrameDriver.py}}   # {{jointcal}}   # {{skyCorrection.py}}   # {{coaddDriver.py}}    # {{multiBandDriver.py}}.     pipe_analysis   # visitAnalysis   # coaddAnalysis   # colorAnalysis   # compareVisitAnalysis   # compareCoaddAnalysis    qa_explorer  # matchVisits.py     validate_drp   # matchedVisitMetrics.py   # validateDrp.py   # reportPerformance.py    Upload the validate_drp metrics (json files) to SQuaSH:   # dispatch_verify.py    Also upload the json file generated by colorAnalysis to SQuaSH:  # dispatch_verify.py  "
Answer: 38961.0

User story: "Use https://github.com/lsst-dm/gen3-hsc-rc2 bootstrap script, make a Gen3 repo for the HSC-RC2  dataset on GPFS with the sqlite registry.     Upload the HSC-RC2 data to S3. "
Answer: 17048.0

User story: "Write a technote [DMTN-133|https://dmtn-133.lsst.io/v] outlining how we think that OCS triggered data processing will happen."
Answer: 223636.0

User story: After a successful file transfer, the Forwarder should send a message with the following format:    MSG_TYPE: FILE_TRANSFER_COMPLETED  FILENAME: <full path to file>  SESSION_ID: <session_id>  JOB_NUM: <job_num>    to the queue "archive_ctrl_consume"      The Forwarder should also accept an acknowledgment message with the following format:      MSG_TYPE: FILE_TRANSFER_COMPLETED_ACK  FILENAME: <full path to file>  SESSION_ID: <session_id>  JOB_NUM: <job_num>    on its FORWARDER_CONSUME_QUEUE (which is gotten from the config files).
Answer: 8533.0

User story: If the "parent" parameter is set to None, the consumer and publisher will error out by trying to call an object that doesn't exist.
Answer: 19877.0

User story: "Add a photometric repeatability metric like the SRD's PA1 metric, but for galaxies and based off model fluxes rather than PSF fluxes."
Answer: 106852.0

User story: "runHscQuick should be able to run after the changes in DM-13298, but it needs some updates to work like the full runHsc (which runs on validation_data_hsc rather than ci_hsc)."
Answer: 28668.0

User story: "DM-21317 adds the {{technote_aastex}} template to https://github.com/lsst/templates.    This ticket is to add support for this new technote type to the lsst-templatebot-aide project and to commission the template for production."
Answer: 290.0

User story: "after finishiing component level work and telemetry, write the high level logic that integrates light and chiller at the csc level, including interlock that makes sure the light can't be on without the chiller. "
Answer: 20394.0

User story: "There is a new GitHub organization (https://github.com/lsst-verification-and-validation) and they would like to populate EUPS packages in it using the {{stack_package}} template and SQuaRE Bot.    * Add the org to the template  * Add the sqrbot account to the new org  * Enable Travis CI for the org."
Answer: 349.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 latest {{ts_xml 4.2.2}} include new meta-data for the header service from T&S CSC "
Answer: 4280.0

User story: "A new version of {{ts_xml 4.2.0}} has been released. This new version and the accompanying new meta-data  need to be tested."
Answer: 5742.0

User story: After discussion with [~<USER>, we decided that we should have some internal polling timer to allow the device controller to cancel the PollScan after some amount of time. We'll have to decide how long is "too long". If this timer is exceeded, the controller should call {{stop_exposure}} and raise either {{asyncio.CancelledError}}, or some other error to let the CSC know that the exposure was automatically (as opposed to user) aborted.    5 seconds is my first guess for this timer: the readout should be a fraction of a second, so this should only be relevant if the spectrograph internals get into some "stuck" state, which we should know about after a second or two.    This is also a usecase for the {{TIMEDOUT}} ExposureState.
Answer: 28811.0

User story: The ArchiveController needs to be updated to accept a message to indicate that a file hase been successfully transmitted.  Once the message is acknowledged, the file needs to be:    1) hard linked to the OODS staging area  2) hard linked to the DBB staging area  3) Removed from the Forwarder staging area    The file can't be directly written to either the DBB or OODS staging areas and then linked because there would be a race condition between this process and both the DBB and OODS.    Furthermore, a separate process shouldn't be used to scan a staging area. (In other words, don't make the ArchiveController do this, let a separate process do it).   A completely separate process would insert an additional delay depending on it's scanning interval and the scanning interval of the OODS.  The OODS shouldn't do it because would recreate a dependency of requiring the OODS to always be there for the DBB.  The DBB process shouldn't create the link to the OODS because it has maintenance windows that would prevent the OODS from getting the file in a timely manner.    The Forwarder will send a message with the following format:    MSG_TYPE: FILE_TRANSFER_COMPLETED  FILENAME: <full path to file>  SESSION_ID: <session_id>  JOB_NUM: <job_num>    on the queue "archive_ctrl_consume" for the ArchiveController to ack on.  When this message is received, the actions above are taken.    The ArchiveController will send an acknowledgment message with the following format to the Forwarder:      MSG_TYPE: FILE_TRANSFER_COMPLETED_ACK  FILENAME: <full path to file>  SESSION_ID: <session_id>  JOB_NUM: <job_num>    on the FORWARDER_CONSUME_QUEUE (which is gotten from the config files).
Answer: 17081.0

User story: "Update the OODS code:      Get rid of YAML load warnings  Fix syntax error that occurred when file name refactoring happened."
Answer: 17090.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: "Excerpt from pipe_tasks' {{assemble.py}}    {code}          if isinstance(tempExpRefList[0], DeferredDatasetHandle):              dataIds = [ref.datasetRefOrType.dataId for ref in tempExpRefList]              psfMatchedDataIds = [ref.datasetRefOrType.dataId for ref in supplementaryData.warpRefList]          else:              dataIds = [ref.dataId for ref in tempExpRefList]              psfMatchedDataIds = [ref.dataId for ref in supplementaryData.warpRefList]  {code}    Quote from [~<USER> in a code review:  {quote}It's a shame the deferred handle object exposes datasetRefOrType as as public attribute - that's really an implementation detail (in that it's just saving all of the arguments to butler.put directly). It looks like we should be doing some normalization of the those arguments up-front so it can just have a ref attribute directly.{quote}  "
Answer: 188652.0

User story: "It would be very helpful for debugging T&S software if we had the `ipdb` package installed as part of the T&S docker container. ipdb is small, and doesn't have many dependencies, but I find it invaluable when debugging code. Can you please add it to our docker container?"
Answer: 25609.0

User story: "While discussing failure modes, we realized that the only user-configurable parameter in the `expose()` command is the exposure time, which has a vendor-specified range 0.002ms-600s). We should check that the requested exposure time is in this range, before we ever attempt to configure the measurement, and raise an exception early if it is not.    We can make this a custom exception so that the CSC doesn't go into FAULT in this instance (vs. what happens when there is an internal error to the spectrograph during an exposure)."
Answer: 28824.0

User story: "The UCD camera definition was updated but the tests were not modified to reflect the change in the number of detectors that were expected."
Answer: 49.0

User story: "Chiller model needs unit tests. Write some. "
Answer: 96825.0

User story: "In DM-19873 I added {{PropertySet.update}} but I misunderstood the internal semantics of {{PropertySet.combine}}.    It turns out that {{combine()}} effectively adds values into the PropertySet so if you have matching keys you get an array item in the combination. This is not what {{update}} is semantically required to do which is effectively to overwrite existing values ({{set}} semantics).  I need to remove the special case call of {{combine}} inside the {{update}} method."
Answer: 241.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} coaddDriver.py /datasets/hsc/repo --calib /datasets/hsc/repo/CALIB/ --rerun RC/w_2019_34/DM-21091:private/<USER>RC2/eli_debug_coadd --batch-type=None  --cores 1  --id tract=9697 filter=HSC-I patch=1,6 --selectId visit=$VVDS_I  {code}     ends with:    {code:python}  compareWarpAssembleCoadd FATAL: Cannot compute coadd (minimum=(3900, 27900), maximum=(8099, 28099)):    File "src/math/Stack.cc", line 82, in void lsst::afw::math::{anonymous}::checkObjectsAndWeights(const ObjectVectorT&, const WeightVectorT&) [with ObjectVectorT = std::vector<std::shared_ptr<lsst::afw::image::MaskedImage<float, int, float> >, std::allocator<std::shared_ptr<lsst::afw::image::MaskedImage<float, int, float> > > >; WeightVectorT = std::vector<float>]      Weight vector has different length from number of objects to be stacked: 10 v. 9 {0}  lsst::pex::exceptions::InvalidParameterError: 'Weight vector has different length from number of objects to be stacked: 10 v. 9' {code}    The adaptation of assembleCoadd for the new Gen3 API in DM-20692 wasn't quite right for Gen2.     Thanks to [~<USER> for bumping into this before the 38 RC2 run. 
Answer: 1394.0

User story: "Qserv container builds are busted since rh-git29 scl package has disappeared from distribution servers.    Roll up to rh-git218.  Roll up to devtoolset-8 while we are at it."
Answer: 37.0

User story: "Update to latest upstream XRootD.  Should address issue with binary characters in log messages."
Answer: 66.0

User story: "Currently, one is allowed to change the simulation mode of a CSC in either STANDBY or DISABLED states (see {{base_csc.py:272}}), while the change from STANDBY to DISABLED is when the device connection should occur. This makes it more difficult to implement library mocks as I have done for the fiber spectrograph: the mock cannot patch over an already loaded library.    If we only allow changing the simulation mode in STANDBY, then these mocks are trivial to implement, and I believe it is safer overall as well: you don't want to start simulating over the top of an already existing connection."
Answer: 8735.0

User story: "Prior to DM-16297 when a header was merged in astro_metadata_translator the resultant header was always a dict and never a PropertyList.  In DM-16297 that is changing because PropertyX can now support for dict-like methods and the conversion to a dict is not required, and also the result of the merge must be able to be sent to afw and it is important that the type does not change.    This breaks pipe_drivers which expects the result from merge_headers to support the {{items()}} method and PropertyX does not.  On this ticket I will add {{items()}} using the existing {{\__iter__}} support."
Answer: 424.0

User story: "Headers are put together currently from index 0 to 15 but depending on sensor type(STA, ITL, WFS, e2v), index 0 of pixel array could be segment 00.  This code should read sensor information from config file and put the header with the right pixel array."
Answer: 9932.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: "Most telemetry messages to the chiller can be generated and sent, and some responses can be processed. Finish the remaining ones needed to publish all telemetry specified in xml"
Answer: 18873.0

User story: "CentOS 8 will be released imminently. We need to check that lsst_distrib can be built with it as a precursor to dropping CentOS6 from Jenkins and replacing it with CentOS8.  "
Answer: 322908.0

User story: "This is a SP for anything that comes up relating to the SAL 4 build process in this sprint. "
Answer: 40305.0

User story: "pipe_base depends on obs_test in order to run its unit tests.  This adds an indirect dependency from pipe_base on obs_base.    We'd like to both start adding Tasks for Gen3 data repository management (e.g. ingest) to obs_base (well, we've already done so, but don't yet import them at package scope) and keep meas_* from depending on obs_test.  This would accomplish both.    Work on this is already at least mostly done on DM-20864; this ticket will cherry-pick those changes in order to land them a bit faster than the rest of that ticket."
Answer: 547.0

User story: "The ArchiveController has information about which directories below the top level storage area should be used to put images.  The ATArchiverCSC needs to message the ArchiveController in order to get this information, otherwise everything ends up in the top level area."
Answer: 23067.0

User story: "We need to fix the fileserver and other things to get NFSv4 working on GKE, like how we are now using NFSv4 at NCSA."
Answer: 49869.0

User story: "Create a fileserver that does NFSv4"
Answer: 1278.0

User story: "This ticket records for earned value purposes the work that was performed on the “Per-CCD distorted astrometry sprint” epic (DM-19943) during the first three months of the Fall 2019 cycle."
Answer: 1.0

User story: "That ain't never gonna work in our k8s environment."
Answer: 1357.0

User story: "Change directory for git cloning."
Answer: 1388.0

User story: "Prepare for IVOA meeting.  This includes:  * preparatory telecons.  * prepare for DCP meeting  * collaborate on DCP ADASS paper and poster.    The meeting is three days: lunch time on the 9th October to lunch time on the 11th October."
Answer: 40244.0

User story: "As folks have left the T&S team and CSCs have been redistributed, the listing at ts_xml.lsst.io is in need of a refresh."
Answer: 22928.0

User story: "So in the 20-spawner code, I tried to set dailies to 0 to remove some of the overhead for more images.  But it still shows up in the spawner page as 3."
Answer: 51262.0

User story: "Following, DM-21239, we know what the appropriate pixelScale for use with obs_decam is. Use that to generate a new set of templates. Do this in parallel with DM-18828."
Answer: 182808.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: https://jira.lsstcorp.org/browse/DM-21230 identified that our DECam HiTS templates were using the pipeline-default 0.33"/pixel, and that 0.2"/pixel provide a 2x decrease in the number of (false) DIASources.  Subsequent [Slack discussion|https://lsstc.slack.com/archives/C2JPMCF5X/p1568742695024300] suggested that the pixel scale should not matter so long as the PSF was Nyquist sampled and the correlated noise was handled correctly in the coaddition.  The latter condition is not met, so while awaiting [future algorithmic advances|https://jira.lsstcorp.org/browse/PIPE-34] this ticket is to determine an empirical best choice for DECam.    This ticket is to produce HiTS templates for a small area for several pixel scales, ranging from (perhaps) 0.1"/pixel, including the instrumental pixel scale (0.26"/pixel), and up to and exceeding the Nyquist scale for the HiTS seeing distribution.  The output is a plot of the number of detected DIASources as a function of the template pixel scale.
Answer: 132158.0

User story: "Update salobj for Python 3.7 as follows:  * Use {{asyncio.run}} instead of {{asyncio.get_event_loop().run_until_complete}}  * Use {{asyncio.create_task}} instead of {{asyncio.ensure_future}} where practical. Stick to ensure_future in library code for backwards compatibility, especially with {{request_script.py}} in ts_scriptqueue which runs the event loop in a very unusual way that is not compatible with {{create_task}}.    To make this easier I added class method `amain` to `BaseCsc` and `BaseScript` and deprecated `main`.    Note that code should make sure an event loop exists when constructing a `Domain`, `Controller` or `Remote`, but we can't enforce that as long as we have {{request_script.py}}  "
Answer: 5419.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 writing the jupyterhub helm chart, it is kind of tricky because helm charts typically aren't served from the same repo as the code.  The helm charts are all next to each other in a special repo format for helm, which isn't like the current layout of the nublado repo (which is fine).    Right now nublado uses the hub image, and that requires the sample_configs found here [https://github.com/lsst-sqre/nublado/tree/master/jupyterhub/sample_configs], and these are put into the container via config maps.    Right now with the helm chart, it needs those files as well when you do the install with helm.  But those files are in the nublado repo, and the charts will be stored in this other repo:    [https://github.com/lsst-sqre/charts]    But the charts repo can't see files in the nublado repo (well, we could with a submodule, but I hate submodules).  So instead of that, what I would do is make a jupyterhub nublado image that just has the sample_configs right in the image, which would require no configmaps for that.  For most people, I think this is good enough.    We could do this by making another dockerfile.complete-hub or whatever, and make another image that is more self-contained.  Then the helm chart can use that complete-hub image, so there is no linkage required between the repos."
Answer: 28.0

User story: "The migration to {{ts_salobj}}  introduced a bug to the HeaderService were logging is missing from the sub-modules."
Answer: 1256.0

User story: "Review the importance of the Stripe82 dataset for SV&V with [~<USER>. SDSS stripe8 is old and some effort (hand-massaging) is needed to reprocess it. Is there sufficient value in the SDSS forced photometry to justify this manual effort or should we just move to HSC."
Answer: 354362.0

User story: "Add a first metric in the context of the [LSST verification framework|https://pipelines.lsst.io/modules/lsst.verify/] to the {{colorAnalysis.py}} script in {{pipe_analysis}}.  The metric is to be uploaded to and tracked by the [SQuaSH metrics dashboard|https://sqr-009.lsst.io]. The first metric added will be the width of the stellar locus."
Answer: 4674.0

User story: "https://jira.lsstcorp.org/browse/DM-21319#Add the first metric to fakesAnalysis, the metric will be the median magnitude difference between input and extracted magnitudes for fakes stars."
Answer: 456668.0

User story: "I believe this is a typo: [https://github.com/lsst/ci_hsc_gen3/blob/b00979639bb9881096ada26b0e51f4cd0c3bbeb1/bin.src/ingestExternalData.py#L70]           "
Answer: 15896.0

User story: "PSTN-004 is the start of a template for multiple papers .."
Answer: 31883.0

User story: "We'd like specify and configure functions to be used for a values calculated by the headerservice in the (yaml) configuration file."
Answer: 505515.0

User story: "Update LinearStage to salobj 4."
Answer: 40516.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 [~<USER>'s {{pipe_analysis}} scripts on the {{fgcmcal}} calibrated RC2 coadds and ensure that performance is consistent with internal {{fgcmcal}} metrics.  If not, further investigations will be made on a separate ticket. "
Answer: 134297.0

User story: "Update {{pipe_tasks}} and related configs to allow coadditions with different external {{PhotoCalib}} and {{SkyWcs}} calibrations, supporting {{jointcal}}, {{fgcmcal}}, and {{fgcmcal_tract}} for photometric calibrations, and {{jointcal}} for astrometric calibrations.  Terminology is now matched to DM-21950.    Originally: Following on DM-20161, with fgcmcal tract-based calibrations, run RC2 coadds."
Answer: 188065.0

User story: "Moving, lots and lots of moving. Going to the vet, going to the passport renewal center for expedited moving. Prepping my home for renting, meeting rental agencies. Last minute visits to family. Visiting the vet again to pick up health certificate to board the plane. Donating things I didn't take to movers. Moving washer and dryer since movers usually have their own."
Answer: 907.0

User story: "If the token grabbed from Github does not have write scope, we still configure the credential helper, which means pushes do not prompt for user/pass, but they also don't work.    There's some combination of detection and documentation that will represent the least wrong thing to do here.  Find it."
Answer: 4384.0

User story: "Use this opportunity to simplify and update the codebase as well as adding support for the Generation 3 middleware.    This ticket is simply to think through and write down your ideas; we'll then schedule time to discuss them with Yusra before we put them into practice.    We discussed this ticket on 2019-11-27 and agreed that the goal is to present initial design thoughts at the Brown Bag of 2019-12-04."
Answer: 139746.0