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: "*   [braces|https://github.com/lsst-sqre/lsst-sphinx-bootstrap-theme/network/alert/package-lock.json/braces/open]  moderate severity   by [GitHub|https://github.com/github][package-lock.json|https://github.com/lsst-sqre/lsst-sphinx-bootstrap-theme/blob/master/package-lock.json]   *      [js-yaml|https://github.com/lsst-sqre/lsst-sphinx-bootstrap-theme/network/alert/package-lock.json/js-yaml/open]  high severity   by [GitHub|https://github.com/github][package-lock.json|https://github.com/lsst-sqre/lsst-sphinx-bootstrap-theme/blob/master/package-lock.json]   *      [tunnel-agent|https://github.com/lsst-sqre/lsst-sphinx-bootstrap-theme/network/alert/package-lock.json/tunnel-agent/open]  moderate severity   by [GitHub|https://github.com/github][package-lock.json|https://github.com/lsst-sqre/lsst-sphinx-bootstrap-theme/blob/master/package-lock.json]   *      [fstream|https://github.com/lsst-sqre/lsst-sphinx-bootstrap-theme/network/alert/package-lock.json/fstream/open]  moderate severity   by [GitHub|https://github.com/github][package-lock.json|https://github.com/lsst-sqre/lsst-sphinx-bootstrap-theme/blob/master/package-lock.json]   *      [tar|https://github.com/lsst-sqre/lsst-sphinx-bootstrap-theme/network/alert/package-lock.json/tar/open]  high severity   by [GitHub|https://github.com/github][package-lock.json|https://github.com/lsst-sqre/lsst-sphinx-bootstrap-theme/blob/master/package-lock.json]   *      [lodash|https://github.com/lsst-sqre/lsst-sphinx-bootstrap-theme/network/alert/package-lock.json/lodash/open]  low severity   by [GitHub|https://github.com/github][package-lock.json|https://github.com/lsst-sqre/lsst-sphinx-bootstrap-theme/blob/master/package-lock.json]   *      [extend|https://github.com/lsst-sqre/lsst-sphinx-bootstrap-theme/network/alert/package-lock.json/extend/open]  low severity   by [GitHub|https://github.com/github][package-lock.json|https://github.com/lsst-sqre/lsst-sphinx-bootstrap-theme/blob/master/package-lock.json]"
Answer: 42066.0

User story: "h3. 1 Jinja2 vulnerability found in [setup.py|https://github.com/lsst-sqre/lander/blob/master/setup.py] on Apr 10  h4. Remediation    Upgrade Jinja2 to version 2.10.1 or later. For example:  install_requires=[ 'Jinja2>=2.10.1' ],  or…  extra_requires=[ 'Jinja2>=2.10.1' ],  Always verify the validity and compatibility of suggestions with your codebase.  ----  h4. Details  h5. CVE-2019-10906 [More information|https://nvd.nist.gov/vuln/detail/CVE-2019-10906]  high severity  *Vulnerable versions:* < 2.10.1  *Patched version:* 2.10.1  In Pallets Jinja before 2.10.1, str.format_map allows a sandbox escape."
Answer: 1913.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: "Make the XML for Script, ScriptQueue and Test meet our new requirements of having a non-empty Description and Units entry for each topic and fields.    Also fix an existing problem where some topic-level Explanation fields were present that should have been Description fields (from before Description was supported for topics)."
Answer: 1146.0

User story: "The Test Case name is a free text in Jira, therefore the user can use whatever character in it.    In order to be rendered properly, it shall be defined as HtmlPandocField() and not just as a String.         The same should be for other text fields."
Answer: 8908.0

User story: "Write a presentation for the DESC DE School to familiarize attendees of the problems due to deblending and how we are addressing them in LSST."
Answer: 9310.0

User story: "Set the default role in [https://github.com/lsst-dm/dm_dev_guide] to python so that the default role (single backticks) can link to Python APIs. This ticket includes testing and adjusting any existing docs to use this role."
Answer: 30584.0

User story: A common approach for enabling external communication to kafka deployed on k8s is to [place a load balancer service in front of each Kafka broker|https://argus-sec.com/external-communication-with-apache-kafka-deployed-in-kubernetes-cluster/]. That provides a simple but still secure solution using SSL termination.     That is the approach we currently use in our EFD deployment at GKE.    For single machine deployment using k3s ("kubes") we are limited by a single external IP address, so that approach does not work. Ingress cannot be used here to route the traffic to each broker because Kafka uses a different protocol than HTTP.    In this ticket we'll investigate the [NodePort approach|https://medium.com/google-cloud/kubernetes-nodeport-vs-loadbalancer-vs-ingress-when-should-i-use-what-922f010849e0] for enabling external communication to the kafka cluster.     We will test this approach on both k3s and gke deployments. In the end, my assumption in DM-19745 that we could have n>1 brokers behind 1 load balancer service may be right if I do it correctly.  
Answer: 202765.0

User story: "The HSC-Footprints notebook in the {{display_firefly}} repository predates the Firefly extension, and also points to a data location for reprocessed HSC data that is no longer valid. Update the notebook."
Answer: 3043.0

User story: "There are three issues:  * test_csc_utils.py sometimes fails with a timeout when setting the final state to OFFLINE. I am virtually certain the problem is that the CSC exits before the final state is reported.  * test_salpy.py succeeds for me, but reports a segfault after reporting success. The segfault is caused by creating a SALPY object and a dds domain in the same process. I don't know why, but it's easy to avoid that.  * test_salpy.py fails for Tiago sometimes. I have not been able to reproduce this."
Answer: 2739.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "There are several missing third party packages from the conda-forge channel. [~<USER> has created previous conda build recipes for most of them, but it may be tractable to move those into conda-build feedstocks, integrating into the conda-forge framework (and getting builds for free), to rely on a single channel for all third parties, instead of an additional lsst channel.         The following packages appear need to be converted to feedstock:     * ndarray   * starlink_ast   * minuit2    "
Answer: 44438.0

User story: "Previous work on packaging third party packages focused on conda in the large, without a specific recommendation on a channel.    This work will take an audit of third party software on conda-forge, which has strict repeatable build rules while also having a larger corpus of software to choose from, thanks to a community effort the default channel doesn't quite have.         [https://conda-forge.org/docs/user/introduction.html#why-conda-forge]          "
Answer: 10244.0

User story: Participate in the "False Positives" Sprint. The outcomes were documented and presented in the Sprint Demo: https://paper.dropbox.com/doc/Understanding-False-Positives--AgE8PF0Rfs0XcCZw~~~B4CqDAg-ZbMedgwpw0npI4ij8tPKl
Answer: 20512.0

User story: "A reasonable request from NAOJ to restore functionality dropped (I think) in the switch to PhotoCalib."
Answer: 283828.0

User story: "[~<USER> created a branch during the deblender sprint that included a significantly improved algorithm for symmetrizing scarlet models, along with an improved centering algorithm motivated by [~<USER>. This ticket is for implementing [~<USER>'s code in scarlet master and the LSST stack."
Answer: 4686.0

User story: "Invited presentation on the potential of LSST to detect exoplanets"
Answer: 45565.0

User story: "Update SAL to include a set of features  to improve interaction with salobj based components  This will be a multi task effort over the next 2 sprints"
Answer: 99107.0

User story: "Identify upgrade components for the EFD systems, test compatability with a sample unit, locate sources and pricing and submit requisition for same  "
Answer: 17303.0

User story: "Test candidate hw for PC based PXI test systems, identify source and submit req for same  "
Answer: 17306.0

User story: "There was an upstream change in the interface to the TAP service that caused this build break:       /home/travis/build/lsst-sqre/lsst-tap-service/src/main/java/org/opencadc/tap/ws/TAPWebService.java:85: error: TAPWebService is not abstract and does not override abstract method heartbeat() in AvailabilityPlugin  public class TAPWebService implements AvailabilityPlugin \{    ^     We just need to add the heartbeat method in and that should fix it."
Answer: 4263.0

User story: "These three wavelength correspond respectively to AOD, ozone and pwv dominated regions.    The time-series are here : [^juillet2019.pdf]     Main comments is that there is still no sign of annual modulation in SNF time series :(     "
Answer: 160883.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: "As part of the AP Sprint to cahracterize false positives:  https://paper.dropbox.com/doc/Understanding-False-Positives--AgE8PF0Rfs0XcCZw~~~B4CqDAg-ZbMedgwpw0npI4ij8tPKl"
Answer: 15418.0

User story: "While working on DM-20154, I wanted to mark a Config field as deprecated, but we have no system for doing that (other than just adding a docstring). [~<USER> suggested an approach on slack, which was fairly simple to implement. I'll also add a note to the dev guide on how to use it as part of this ticket."
Answer: 37184.0

User story: "I ran into ci_hsc failures due to gen2/gen3 getter comparisons, meaning I need to update the gen3 raw readers to look like the changes I made to the gen2 ones. In order to allow both butlers to use the same underlying code, we need to move {{FitsRawFormatterBase}} from daf_butler into obs_base. [~<USER> suggested this change."
Answer: 1174.0

User story: "Due to the new version of the ingress controller, rules that use the rewrite-target aren't compatible with the old version of the rules.  Now new capture groups have to be added.  Do this for -int, then stable when we roll it out there."
Answer: 5735.0

User story: "Implement the simple, shift/rot WCS fitter as described in DM-20310."
Answer: 46078.0

User story: "Investigate resource manager options for kubernetes commons  - Understanding AA and SSO for k8s deplyment"
Answer: 1.0

User story: "Write a simple pure OpenSplice dds example that shows the problem of occasional duplicated samples when a writer with TRANSIENT durability writes to a reader using VOLATILE durability.    Make sure the reader waits at least 10 seconds for the data, since it likely is due to historical data and the wait_for_historical_data cal can easily take 10 seconds or more.    If possible also demonstrate the issue of dds complaining of an invalid read condition, since the case above seems to exacerbate that problem."
Answer: 62.0

User story: "Update BPS to match Gen3 changes from [DM-19988|https://jira.lsstcorp.org/browse/DM-19988]"
Answer: 37486.0

User story: "The name of the file should match the name of the task it contains."
Answer: 38774.0

User story: "DM-19382 changed the name of a keyword in {{ip_isr.interpolateFromMask}} from {{growFootprints}} to {{growSaturatedFootprints}}, but did not update {{obs_lsstSim.processEimage}} which calls it, breaking it."
Answer: 36.0

User story: "Update XML for ATDome and ATDomeTrajectory to use units=unitless for quantities with no units. Also make sure the descriptions for the topics are complete and the metadata in SALSubsystems.xml is correct and complete, including a useful description."
Answer: 2999.0

User story: "Investigate and learn from <USER>how to use salobj to communicate via SAL with other CSCs. Evaluate the feasibility of migrating the HeaderService to salobj"
Answer: 12743.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 ts_sal script make_idl_files.py uses {{os.rename}} to move the generated IDL file to ts_idl. Unfortunately this call fails if the source and destination path are on different file systems, as can easily happen when using Docker.    The simplest fix is to copy the IDL files instead of moving them."
Answer: 1520.0

User story: LCR-1728 on LSE-319 has been approved by the CCB and the PM.  It now needs to be released in order to reach the CCB "Fully Implemented" state.  Most of this work, for a LaTeX/Github/LTD-based document, falls to the proposer, with final steps done by [~<USER>.      This tickets asks for the appropriate branch and tag management in the document release process to be done, with the products provided to Rob for final release.
Answer: 112395.0

User story: "Review the SHWFS and guider code by vendor (the developer is Pauline in France). The goal is to evaluate if LSST could take this code and change them or if we needed Pauline to help us (which would require a change request).    The new Factory Acceptance Test Review dates are July 18th and 19th and Sandrine would like to have an answer by then."
Answer: 32968.0

User story: "This will enable reproducible builds."
Answer: 314703.0

User story: "Update the ts_MTAOS xml for description and unit. The related tests in ts_xml will be done by Rob. This task will also take time to be familiar with the unit module in astropy."
Answer: 23088.0

User story: "Work with the communications team to put in place the workshop website and set up short link to ls.st/<>    Website request form: https://project.lsst.org/website-request"
Answer: 10420.0

User story: "This task is to capture the work I've been doing in putting together a build system for the development environment which encompasses several products and that is used as base for a lot of CSC development and early deployment. "
Answer: 20383.0

User story: "Send to   * LSST community  * LSST Digest  * Communications team  * Science collaborations  * slack announce-everyone"
Answer: 20434.0

User story: "Currently, the SQuaSH password for {{dispatch_verify.py}} is supplied via environment variable or command line option.    On shared systems, neither mechanism is very secure.  This ticket will add an option to prompt for the password when the script is run interactively."
Answer: 3159.0

User story: "Prepare and present on:   * DM status   * Alerts in LOY1    Update DM sections on the Operations Readiness Criteria    Present 'DM updates on response to AMCL' on behalf of Wil who cannot attend    "
Answer: 10539.0

User story: "While processing Decam data for DM-15340 I identified a few places in building the DCR model that could be made more efficient. These improvements speed up the calculation by 5 - 40%, depending on the properties of the input exposures."
Answer: 8497.0

User story: "Add units and update metadata in SALSubsystems.xml for the Script, ScriptQueue and Test SAL components."
Answer: 2272.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: "If SAL is updated to not dispose of the ackcmd sample immediately after writing it (DM-20312) then undo the change made to ReadTopic in DM-20275 to work around this issue."
Answer: 84935.0

User story: "It turns out that SALPY is disposing of each {{ackcmd}} and {{command_...}} topic sample immediately after writing it, in order to conserve resources. This makes acmcmd different from events and telemetry, which means salobj cannot ignore NOT ALIVE ackcmd samples, unlike for events and telemetry. It also means that the ADLink {{ospltest}} tool cannot see these samples unless one changes a default setting.    I really hope there is a better way to restrict the resources -- one that allows filtering on NOT ALIVE and works with the {{ospltest}} defaults.    If the resources are cleaned up once the sample goes off the end of the queue then I think we can just stop manually disposing the samples, especially now that our queue length is shorter. And if resources for samples are not automatically cleaned up when the queue fills then we'll have to modify salobj and possibly SAL as well, to dispose of samples at some point, else resource usage will simply grow over time.    This is what was causing: DM-20275 ts_salobj cannot see command acknowledgements."
Answer: 90763.0

User story: "Investigate how to fit a final tweak to the WCS from tangent-plane/IWCS produced by DM-20188 to the Sky allowing for tweaks to on sky positions and affine transform."
Answer: 3074.0

User story: "LDM I suppose .."
Answer: 190134.0

User story: "Following discussion at the Commissioning SV&V workshop in June 2019, it was decided to migrate the contents of LDM-502 to Jira and merge the test specifications defined therein with those being developed in the Jira based LVV project.     "
Answer: 101066.0

User story: "Create test plan and report LSE-429 for:    Commissioning Science Verification Test Plan: Single-visit and Full-survey Performance w/ ComCam    The corresponding Jira test plan is LVV-P2."
Answer: 24915.0

User story: "General refresh of LDM-294 - latest schedule, milestones, product tree, update org chart. Align text."
Answer: 45021.0

User story: "There are small but significant amp-to-amp offsets in post-ISR HSC images that are not removed by flat-fielding that cause problems with sky estimation and photometry.  It has been suspected that these problems are caused by incorrect non-linearity corrections, but I think this is still an open question.    This ticket is to record investigations into the origin of these offsets."
Answer: 94965.0

User story: "While updating the API in scarlet some of the tests related to PSF normalization broke. Since I am the one who wrote the tests it will be easiest for me to diagnose the cause of the differences and the code and or the tests to give the correct results."
Answer: 4302.0

User story: "What,  if any,  are the driving use cases for access to alerts in < 5 min"
Answer: 469279.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: "Clarify if/how the project could provide filtered streams, e.g   * Simple filters: RA/DEC, Magnitude, Spuriousness cuts?   * Image-free streams of alert packets?   * sources associated with past alerts?    and provide estimate of how much the stream volume is reduced by these options"
Answer: 469476.0

User story: "Draft responses for review by the broker workshop SOC, DM, and LSST operations.    Consider the final destination of the answer to each question – do any LSST documents need to be updated?"
Answer: 55851.0

User story: "Goal: Understand what’s preventing us from full focal plane background models    Questions:  - Are there amp-to-amp offsets? What’s causing them?  - What causes the chip-to-chip offsets? What’s causing them?  - What’s the interaction between backgrounds and transmission/zero-points?"
Answer: 11.0

User story: For the work being done in DM-19943, we need to have the CCD plate scale description in the camera geometry to properly reflect the pixel-to-mm conversion.  Currently (for historical reasons?), the {{obs_subaru}} package defines this transformation to be unity and this is a showstopper for using HSC data as a test data for validation of the work of DM-19943.  While all cameras are in the process of being converted to YamlCamera and will use consistent/correct scaling (this is DM-19352 for {{obs_subaru}}), we would like to be able to move forward with this before that is all merged (HSC is otherwise the ideal test dataset for these purposes because we understand it well and the distortion model is well represented).  This ticket is thus to make an attempt at fixing this units issue in the current state of the camera representation (slight emphasis on "attempt" as this might be more complicated/convoluted than one might naively picture and this should not turn into a huge time sink).
Answer: 30154.0

User story: "I found log messages from ISR saying:  {code}  processCcd.isr INFO: Applying brighter fatter correction.  processCcd.isr INFO: Finished brighter fatter correction in {bfResults[1]} iterations.  {code}    This incorrectly uses the new python string formatting (missing a leading {{f}} on the string). However, we generally want log messages to defer the formatting, so the old {{%f}} style should be used instead.    I suggest auditing other recent changes to the logging for similar bugs."
Answer: 31835.0

User story: "Jérémy Neveu has developed and tested a forward model spectrogram extraction software, he is willing to help us using and testing it."
Answer: 20026.0

User story: "Per the [DMLT review of QAWG outputs|https://confluence.lsstcorp.org/display/DM/DMLT+Discussion+of+QAWG+recommendations], convene a mini-working-group to discuss the design of the metrics system.    DM-QAWG-25, 26, 35."
Answer: 250866.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 now appears that there is no one to one relationship between SNF and MERRA-2 atmospheric parameters.    A better approach will be to look directly at the extinction, for instance at 550 nm (to remove the angstrom exponent from the comparison)."
Answer: 33388.0

User story: "Submit the LCR after the updates in the epic are complete."
Answer: 75734.0

User story: "ts_salobj 4 cannot seem to communicate with ts_sal v3.10.0. The symptoms are that events and commands are transmitted, but command acknowledgement is not received. Also I have seen segfaults if I create the SALPY object and the salobj Domain and Remote in the same process, when things finish shutting down. But this does not seem to happen if they are in separate processes.    Add a unit test for this that uses SALPY_Test. Add ts_sal as an optional dependency of ts_salobj since the SALPY_Test module will be there.    I tried to use the ADLink Tester tool but it cannot find anything to connect to. so I get no information from it, alas."
Answer: 9596.0

User story: "Write the Alarm class for the Watcher. This class keeps track of alarm state and state transitions.    The basic plan is to have a rule class that takes care of watching data from CSCs. Each rule will have exactly one alarm and the rule will set the alarm's severity. Changing the alarm's severity will cause the alarm event to be output. The CSC will have a command to acknowledge one or more alarms. Snooze will be handled by auto-unacknowledging an alarm and auto-acknowledge can be handled by auto-acknowledging an alarm."
Answer: 16942.0

User story: "Following discussions at the Community Broker Workshop 2019. This is to propose that the PPDB contents be non-proprietary, and hence redistributable by users with data access."
Answer: 79045.0

User story: "As specified by LSE-209, there are two detailed states in offline that should be published. The ATCamera XML contains the appropriate information and can be used as an example.     The CAP ticket is here:  https://jira.lsstcorp.org/browse/CAP-224"
Answer: 117.0

User story: "Review the documents of M2 to have an initial understanding of status. This is the phase 1."
Answer: 24242.0

User story: "The repository of ts_wep has been updated to support the eimage. This task will test the update in ts_ofc and ts_phosim repositories. The PhoSim will be used to verify the closed-loop simulation with Eimage."
Answer: 17366.0

User story: The developer guide ["Responsibilities" section|https://developer.lsst.io/services/datasets.html#responsibilities-on-ingest-or-maintenance] notes that datasets need a readme, and has a specific note about where the refcat readme goes. We have no such readme for any of the {{/datasets/refcats}} subdirectories. I'll writeup a description of the Gaia DR2 data and attempt to add some description of the other existing {{htm/v1}} refcats.
Answer: 180200.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 top-level detailed enumeration is unnecessary as CSCs should not repeat summary states in detailed states and should be removed from the XML.    This captures the work from:  https://jira.lsstcorp.org/browse/CAP-225"
Answer: 93.0

User story: "DM-19843 implemented computing and using the Jacobian in least squares fits of Gaussian mixture models in MultiProFit, but not for PSFs, where we fit a total flux (fixed to 1) and flux ratios. This ticket will implement computing the Jacobian for flux ratio terms or a suitable workaround."
Answer: 96307.0

User story: "A test Jenkins is required in order to test that the changes implemented in DM-18112 have no impacts on the existing builds."
Answer: 29198.0

User story: "We need something that runs reliably on new versions; separate stack and JL development cycles."
Answer: 24779.0

User story: "Test and ensure all the required files are in 3.10 rpm folder in [https://project.lsst.org/ts/lsstrepo/] 3.10 tag."
Answer: 46136.0

User story: "Bring up AT sim CSCs down in auxtel lab on pontus. Update CSCs to sal 3.10."
Answer: 226047.0

User story: "Install MQTT broker, to accept communications from SAL applications and HVAC telemetry"
Answer: 47807.0

User story: "Currently, there is no licensing or copyright information in either of the alert_stream or sample-avro-alert repositories.    Since this code (or, possibly, some ZTF-derived variation of the same) is now popping up in [various|https://github.com/lsst-uk/lasair/blob/e6baca8a68a43de0f66a9a5848697dfb11545023/src/alert_stream_ztf/python/lsst/alert/stream/alertProducer.py] [places|https://github.com/astrolabsoftware/fink-broker/blob/1378d4066d4540e05632e1c9b5a872d3ba4b2013/fink_broker/alertProducer.py] (apparently in some cases with copyright claims added and released under an Apache license!), we should make sure that it is properly attributed and licensed so that this is all above board."
Answer: 47.0

User story: "Per [discussion on Slack|https://lsstc.slack.com/archives/C2K6YMTK2/p1561046699106000], the full name of  the service often referred to as “the EFD” is “the Engineering and Facility Database”, following LTS-210. Please update the DM glossary appropriately.    (Bonus points for fixing any other documents which define the acronym without referring to the standard glossary)."
Answer: 128669.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, data formatting is done on the server-side and passed to the client as string.  This okay for display but, it cannot be used in calculation since some precision may have been lost.  Switch to client-side formatting so that the full data's precision is preserved on the client.    This is typically a problem for FITS or VOTAbles that doens't express the precision in their attributes and when the data gets to the clinet for table and chart , some problem appeared there bevause of the default formatting implied on the server.    See discussion in [IRSA-2270|https://jira.ipac.caltech.edu/browse/FIREFLY-117], but when precision is not given:   * double in fits file will get "%.9g"   * floating-numbers in votable will go through a 'guess' logic with a minimum of 8 decimal places.    IPAC ticket [https://jira.ipac.caltech.edu/browse/FIREFLY-108]    [https://jira.ipac.caltech.edu/browse/FIREFLY-149]
Answer: 541616.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: "Working on the tickets to implement the new defects handling, [~<USER> implemented a new class to hold lists of defects.  This seems to not be playing well in some very specific circumstances.    Specifics:  I never see segmentation faults on Linux.  On mac OS I've seen a segmentation fault on High Sierra running v10.1 of command line tools.  I have also seen a segmentation fault on Mojave running v10.2.1 of command line tools, but not when running v10.1.    To repeat:  1) setup w_2019_24  2) setup {{master}} of:    * {{obs_test_data}}    * {{obs_decam_data}}    3) setup {{tickets/DM-18739}} of:    * {{obs_base}}    * {{obs_test}}    * {{pipe_tasks}}    4) setup {{tickets/DM-19730}} of:    * {{obs_decam}}    * {{testdata_decam}}    5) Navigate to a location where an output repository can be created.  6) Execute (on some systems, this will result in a segmentation fault in the measurement phase in the calibrate task):  {code}  processCcd.py $TESTDATA_DECAM_DIR/rawData --output tmp_out --id visit=229388 ccdnum=1 --calib $TESTDATA_DECAM_DIR/rawData/cpCalib --config calibrate.doPhotoCal=False calibrate.doAstrometry=False  {code}  7) Remove output repository and rerun with defect interpolation turned off.  This does not result in a segmentation fault on my system.  {code}  processCcd.py $TESTDATA_DECAM_DIR/rawData --output tmp_out --id visit=229388 ccdnum=1 --calib $TESTDATA_DECAM_DIR/rawData/cpCalib --config calibrate.doPhotoCal=False calibrate.doAstrometry=False isr.doDefect=False  {code}    I isolated things a little by running {{calibrate.py}} on the persisted outputs of {{IsrTask}} and {{CharImageTask}} and did not observe a segmentation fault.    I did more looking and if I modify the defects sent to {{IsrTask}}, I can get rid of the segmentation fault:  * Send an empty {{Defects}} -- No segmentation fault  * Drop the last three defects from the list -- No segmentation fault  * Drop the first three defects from the list -- Segmentation fault  * Delete the python object that holds the defects immediately after interpolating -- Segmentation fault.    Here is the backtrace from my terminal is attached. "
Answer: 52705.0

User story: With w_2019_24 and its ci_hsc repo, running the Gen3 ISR task failed     For example, to reproduce:  {noformat}  pipetask -d "visit.visit=903334" -d "detector.detector=22" -j 1 -b $CI_HSC_DIR/DATA/butler.yaml   -p lsst.ip.isr -p lsst.pipe.tasks     -i raw,calib,ref/ps1_pv3_3pi_20170110  -o test1 run --register-dataset-types      -t isrTask.IsrTask:isr -C isr:$OBS_SUBARU_DIR/config/hsc/isr.py  {noformat}      The error is   {noformat}  lsst.pipe.base.graphBuilder.PrerequisiteMissingError: Deferred search failed for prerequisite dataset illum using data ID {exposure: 903334, visit: 903334, physical_filter: HSC-R, abstract_filter: r, instrument: HSC, detector: 22}.  {noformat}    
Answer: 146.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 ts_externalscripts for ts_scriptqueue 2.2. This is a trivial change but is blocked by DM-20151 and DM-20152 which update the scripts for ts_scriptqueue 2.1 (a much harder job)."
Answer: 62208.0

User story: "<USER>[identified a typo|https://community.lsst.org/t/typo-bug-in-meas-algorithms-utils-py/3744] in {{lsst.meas.algorithms.utils}}."
Answer: 170.0

User story: "Update ts_sal unit tests for DM-19474: remove char0 field from all Test array topics: setArrays command, arrays event and arrays telemetry."
Answer: 213.0

User story: "Make a version of ts_xml develop that is compatible with both ts_sal v3.10.0 and also the development/pre-4 branch. Do this as a single commit that can be reversed when it is time to release ts_sal 4.    This requires two changes:  - Undo the removal of the char0 arrays field  - Add back whatever Script enum the ts_sal v3.10.0 test is looking for."
Answer: 422.0

User story: "This ticket is to capture requested updates to DMTN-102 that come out of the Community Broker Workshop.    First, to recast the data rates section in (mega/giga) bits per second rather than bytes per second, for easier comparison with typical bandwidth units."
Answer: 290381.0

User story: "- Update the milestones repository with data extracted from PMCS (/)  - Update LDM-503, LDM-564, images repository (/)  - Update milestone dates loaded into Jira (/)  - Update skeleton May 2019 monthly report (/)  - Circulate upcoming milestone list to dm-cams  - Audit and update https://confluence.lsstcorp.org/display/DM/DM+PMCS+Update+Requests"
Answer: 91760.0

User story: "Update PSTN-003 in advance of July PST."
Answer: 379756.0

User story: "Transfer [https://confluence.lsstcorp.org/display/SYSENG/SAL+constraints+and+recommendations] from confluence markup to RST and push changes to ts_xml.lsst.io."
Answer: 3996.0

User story: "Per https://github.com/lsst-dm/alert_stream/issues/24, the latest release of fastavro is incompatible with the serialized alert data in lsst-dm/alert_stream.    Long term, we need to fix the data. Short term, pin the version of fastavro to one that works in the Dockerfile."
Answer: 28.0

User story: "429 is OK as well as 200."
Answer: 69.0

User story: "Work intended for this epic was either postponed or done under the following epic:   * DM-18717"
Answer: 1.0

User story: "Old T&S Epic carried over from old JIRA project - no longer valid"
Answer: 5.0

User story: "Finish off monthly - check variance narratives ."
Answer: 99676.0

User story: "Work intended for this epic was done under the following epic:   * DM-18010 Finishing ATMonochromator SW Development"
Answer: 1.0

User story: """SHOW databases"" in qserv-in multi-czar shows the local databases in the local Mysql instance instead of the installed databases, like qservTest_case05_qserv. Further, the only local databases, in multi-czar, should be for qserv results, temporary data, and possibly empty local copies of qserv database tables for creating result tables (and user query verification)."
Answer: 132748.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-muliczar-tests.sh successfully starts the containers and loads the data, but the tests fail due to connection issues with the czar. All the tests need to be run on all the czars that are started in the test."
Answer: 179964.0

User story: The cmsd.pid file can have two different names depending on the configuration. In multi-czar the information is different inside and outside the container (or in the different containers) making it so that they are looking for differently named files. When starting the container (qserv-start.sh), the file is named "/qserv/run/var/run/master-shared/cmsd.mangr.pid" and when the container is trying to check that the container is running (qserv-status.sh), it looks for  "/qserv/run/var/run/master-shared/cmsd.pid".
Answer: 71993.0

User story: "Having individual empty chunks files is not a good solution. Having the empty chunk files represented by tables in the shared database is easier to manage. For now, the loader should create both the empty chunk files and the tables and the czars should be able to read both. This should make the transition easier."
Answer: 51941.0

User story: "This issue is here to describe the reason for making the epic invalid.  This work was no longer needed and/or folded into the MTAOS CSC."
Answer: 111.0

User story: "This ticket will be done in two parts  * Refactor the interface used to write PipelineTasks, with knowledge learned prepairing for the gen3 demo, in preparation for a design review  * Take input from a design review and create the final interface"
Answer: 105038.0

User story: "Jérémy Neveu has implemented Yannick Copin spectrum extraction software.    He has tested it again simulated images.    He is currently re-processing part of the CTIO 0.9-m observations.    All the observations are on lsst-dev at /project/photocalData/data/ctio0m9    I shall inform on the result."
Answer: 175349.0

User story: "Create a Jenkins job to build the SAL library RPMs, push them to the AWS S3 buckets and then push them into the Nexus3 yum repo."
Answer: 1160.0

User story: "CFHT MegaPrime has its rotator angle set to NaN in {{astro_metadata_translator}}, and its rotator type to UNKNOWN. Since it is on an equatorial telescope, we can just pre-compute the correct value, set {{rotType=SKY}} and set those in the translator and they will be correct for everything (or at least correct enough to provide an initial guess).    There are diagrams on this page that may help figure out the correct on-sky rotation angle, though it's not as helpful as the DECam diagrams:    https://www.cfht.hawaii.edu/Instruments/Imaging/Megacam/specsinformation.html    One open question is whether we need to set a {{rotatorHandedness}} (when +Y is north, is +X is east or west?) value in {{VisitInfo}}, or whether we can easily get that from the camera geometry. At present, {{VisitInfo}} does not preserve this information, because [~<USER> assumed it would be managed by the camera geometry."
Answer: 10045.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: "DECam has its rotator angle set to NaN in {{astro_metadata_translator}}, and its rotator type to UNKNOWN. Since it is on an equatorial telescope, we can just pre-compute the correct value, set {{rotType=SKY}} and set those in the translator and they will be correct for everything (or at least correct enough to provide an initial guess).    The diagram on this page should help figure out the correct on-sky rotation angle.    http://www.ctio.noao.edu/noao/node/2250    One open question is whether we need to set a {{rotatorHandedness}} (when +Y is north, is +X is east or west?) value in {{VisitInfo}}, or whether we can easily get that from the camera geometry. At present, {{VisitInfo}} does not preserve this information, because [~<USER> assumed it would be managed by the camera geometry."
Answer: 9981.0

User story: "Update the ts_wep to Use the eimage. The [DM-19837|https://jira.lsstcorp.org/browse/DM-19837] had updated the phosim_utils and obs_lsst to ingest the eimage by butler."
Answer: 5645.0

User story: "Sometime today I suddenly lost all email from May 8th until 1:20pm today  It's gone from the Atlantis view, and my local Thunderbird inbox.  Can you get it back ?"
Answer: 29792.0

User story: "The time of needed for AssociationTask increased by a factor of a few due to the switch over to pandas from afw. This ticket will investigate where the majority of the time is being spent."
Answer: 64896.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're hoping to start attaching improved initial WCSs using cameraGeom + boresight and rotation (DM-20154), but this depends on the quality of:   * the cameraGeom models   * the boresights from the raw headers   * the rotation angles (when appropriate) from the headers    Looking at the "easy" dataset [~<USER> has been collecting, pick one _full_ visit from each of (HSC, DECam, CFHT, LSST/DC2), and:   * Process the data through at least CalibrateTask (so we can consider those fitted WCSs "truth", at least for now, because "easy" means we should be getting good fits).   * For each detector, load the raw and apply the new function to create the from-raw WCS that [~<USER> will provide as a Python snippet.   * Compare the fitted WCS and from-raw WCS.  I recommend starting by looking at how the calexp bounding boxes transform onto the sky (the notebook attached to DM-19731 does this for HSC and may be useful as a starting point).  But looking at other points is of course fine, too, and would avoid some rotational degeneracies.    We're interested in the following questions:   * Does the from-raw WCS function not run at all for one of the cameras of interest, because:   ** the Visitinfo doesn't include boresight or rotation?   ** the cameraGeom lacks a coordinate system we need?   * If the function appears to work but produces garbage, is it because:   ** the VisitInfo boresight values are bad?   ** the Visitinfo rotation values are bad (or perhaps inconsistently defined across cameras)?   ** the cameraGeom does not attempt to include optical distortion at all?   ** the cameraGeom has distortion, but it's not very good?   ** all of the above appear in order, but there's a scaling problem aligned with the zenith direction (i.e atmospheric refraction, which this model doesn't account for but perhaps could)?    I think I already know that the answer for HSC will be "it appears to work but produces garbage because the cameraGeom distortion has a units problem".  It would be nice to hack something together to address that problem, in order to see if there are *other* problems, but I haven't thought much about how best to do that.
Answer: 11505.0

User story: "After the issue on Friday with the EFD writers was fixed, the writers indicated that they were functioning. However, no information was received and inserted into the DB."
Answer: 194469.0

User story: Presenting "Local monitoring of atmospheric transparency from the NASA MERRA-2 global assimilation system" at PCWG telecon, the question of how reliable the PWV determination in MERRA-2 is above ocean/island.    I don't know, I think it depends :)  
Answer: 176737.0

User story: "set up windows ASC host, get SpatialAnalyze license sorted out, connect to T2SA application, exchange information between ASC and T2SA"
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: "On Slack there has been a request for fix_header to work for DECam data. Currently there is no search path available. Update to allow CFHT and DECam to have search paths defined. It may also be necessary to patch the obs packages to call fix_header."
Answer: 54922.0

User story: "As discussed at the DM SST meeting on 2019-06-14, provide a set of draft conventions on the use of  notebooks vs libraries of code covering: framework of policies for moving from notebooks to libraries of code, conventions, which notebooks are works in progress, which can be CI'd, how is library code stored etc. "
Answer: 373061.0

User story: "The long term ideas for decomposing the photometric fits into the wcs jacobian term and the illumination correction are described in https://community.lsst.org/t/photometric-calibration-and-astrometric-jacobians/3232.  Over the near term, {{fgcmcal}} has been ignoring the WCS jacobian and simply constraining the combined calibration term, as this is what can be handled in the {{PhotoCalib}} objects.  However, in the case of the tract-based {{fgcmcal}} (DM-16704), this might not work as well because there is not as many star observations (compared to a global fit) to constrain the relevant spatial variation terms.  This ticket investigates, in conjunction with DM-20161, whether performance can be improved in tract-based {{fgcmcal}} by distinguishing these terms.  If so, some functionality of combining a WCS jacobian BoundedField (DM-15431) with a Chebyshev BoundedField will need to be added to {{afw}}.  If this is not necessary, we can wait for the longer term solution when calexp images will be fluence images thus taking the wcs jacobian out of the equation when it comes to photometric calibration."
Answer: 302460.0

User story: "In conjunction with DM-16704 {{fgcmcal}} needs to be run and evaluated on the HSC RC2 dataset, including a comparison to the performance of the full global fit (DM-18015)."
Answer: 110750.0

User story: "We need to fix the stackclub notebooks so that users in the science collaborations can make use of scarlet v0.5 and the new {{meas_extensions_scarlet}} package. This ticket includes updating the stack club tutorials and using a selection of the last scarlet DESC-BTF slides for a quick presentation to stack club."
Answer: 95350.0

User story: "It seems a Qserv operator for k8s would be useful. I'll study how to build that first."
Answer: 151246.0

User story: "Update containers and write documentation on deploying docker containers. [https://confluence.lsstcorp.org/pages/viewpage.action?pageId=110233227]         Specific CSCs included are Electrometer, LinearStage, Monochromator, ATSpectrograph (built by Tiago deployed by Eric, but remains untested)."
Answer: 11419.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 close of DM-19951 describes a new design for how we create an initial WCS from the raw exposure VisitInfo metadata. This ticket is to implement that design. In summary:    * Write tests against sensor bounding boxes on known data (e.g. {{testdata_*}}).  * Write a new function to create a SkyWcs from VisitInfo and Detector ({{createInitialSkyWcs}}?).  * Call that function from {{exposureFromImage}}.  * Reorder the reading of raw VisitInfo and WCS metadata to deal potential metadata stripping problems.  * Check that all existing cameras use this code path, and not some custom Exposure metadata handling.  * Turn off {{addDistortionModel}} in ISR for all cameras, so that the above WCS does not get overwritten."
Answer: 101247.0

User story: "Delete unused content from ts_externalscripts:  * unused utility functions  * CalSysTakeData (use the version in ts_standardscripts instead)  * LaserCharacterization (superseded by a Jupyter notebook)"
Answer: 151.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: "Please update the LaserCoordination script in ts_externalscripts to be compatible with dds salobj (ts_salobj v4.1) and schema-based scripting (ts_scriptqueue v2.1).    I suggest you update the script for ts_scriptqueue v2.1, which means the schema is returned using a property named {{schema}}. There is an update in review that will make trivial further changes (truly trivial and I'm happy to do the work), but I think we'd really like to have a version of ts_externalscripts that works with ts_scriptqueue v2.1 before I make the additional changes for ts_scriptqueue v2.2.    Please also fix flake8 issues. scons found the following:  {code}  /home/saluser/tsrepos/ts_externalscripts/python/lsst/ts/externalscripts/coordination/laser_coordination.py:22:80: W505 doc line too long (101 > 79 characters)  /home/saluser/tsrepos/ts_externalscripts/python/lsst/ts/externalscripts/coordination/laser_coordination.py:23:80: W505 doc line too long (105 > 79 characters)  /home/saluser/tsrepos/ts_externalscripts/python/lsst/ts/externalscripts/coordination/laser_coordination.py:24:80: W505 doc line too long (104 > 79 characters)  /home/saluser/tsrepos/ts_externalscripts/python/lsst/ts/externalscripts/coordination/laser_coordination.py:82:13: F841 local variable 'set_electrometer_mode_ack_coro' is assigned to but never used  /home/saluser/tsrepos/ts_externalscripts/python/lsst/ts/externalscripts/coordination/laser_coordination.py:83:13: F841 local variable 'set_electrometer_integration_time_ack_coro' is assigned to but never used  /home/saluser/tsrepos/ts_externalscripts/python/lsst/ts/externalscripts/coordination/laser_coordination.py:111:13: F841 local variable 'setup_ack' is assigned to but never used  /home/saluser/tsrepos/ts_externalscripts/python/lsst/ts/externalscripts/coordination/laser_coordination.py:119:25: F841 local variable 'move_ls1_ack' is assigned to but never used  /home/saluser/tsrepos/ts_externalscripts/python/lsst/ts/externalscripts/coordination/laser_coordination.py:125:29: F841 local variable 'move_ls2_ack' is assigned to but never used  /home/saluser/tsrepos/ts_externalscripts/python/lsst/ts/externalscripts/coordination/laser_coordination.py:134:29: F841 local variable 'electrometer_scan_ack' is assigned to but never used  /home/saluser/tsrepos/ts_externalscripts/python/lsst/ts/externalscripts/coordination/laser_coordination.py:146:17: F841 local variable 'stop_propagate_ack' is assigned to but never used  {code}    Here are some resources:  * https://community.lsst.org/t/changes-in-salobj-4-the-dds-version/3701/2  * https://community.lsst.org/t/changes-to-sal-script-schemas-and-dds/3709/2  * DM-20089 shows the same update for some scripts in ts_standardscripts  * I am happy to answer questions about the conversion process  * [~<USER> wrote LaserCoordination and can answer questions about the script"
Answer: 67389.0