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: "DM-18735 created code paths for reading and writing Pandas into the Ppdb using the standard Pandas sql interfaces. It's not currently known now efficient these interfaces are for read/writes. This ticket will investigate this using [~<USER>'s test code in dax_ppdb and ap_pipe the difference in run time between the two methods."
Answer: 17460.0

User story: "Speed up certain operations by allowing vectorized dimention entry inserts."
Answer: 15825.0

User story: Workshop "Hotwiring the Transient Universe 6", Aug 19-22 2019, Evanston IL. Serve on the SOC, and give an invited talk on "The future: LSST data products".    [https://sites.northwestern.edu/hotwired6/]
Answer: 188812.0

User story: "Rewrite ts_salobj to use OpenSplice dds and IDL files generated by ts_sal, instead of SALPY libraries."
Answer: 49393.0

User story: "Create a notebook using updated fit results from DM-18707 to investigate whether fast Gaussian fits can be used to 1) improve Sersic model initialization and 2) set reasonable joint flux-size priors"
Answer: 69327.0

User story: "[~<USER> reports that ingest of BOT is failing because there is a typo in the dark time calculation. This code has not been tested before since DARKTIME has never previously been written to files. The fix is trivial."
Answer: 46.0

User story: "At DRP Team meeting April 3 2019, we discussed the steps in ISR that could be reordered in order to support storing pre-interpolated pixels (that have had ISR applied to them so that they can be meaningfully swapped in downstream processing).     The interpolation step before brighter-fatter is necessary. Therefore, we decided to reorder ISRTask as follows:    * First ISR Steps…  * Interpolate  * Do Brighter-Fatter Correction  * Put the pre-interpolated pixels back into the now BF-corrected raw.   * …Continue ISR…  * Saturated/NaN pixels and defects are *masked only*  (no interpolation)  * Second to last step: write out pre-interpolated pixels  * Last step:  Interpolate the *union* pixels masked for interpolation (sat/bad/nan)    [~<USER> pointed out that it is more correct to interpolate the union of all regions that need to be interpolated rather than  in separate stages for each of SAT, BAD, NaN. In addition to the extra steps of reinserting pre-interp pixels, this tickets also includes refactoring to separate the masking step and interpolation steps in {{maskAndInterpNan}}, {{maskAndInterpDefects}}, and maybe {{saturationIntepolation}}.  "
Answer: 58689.0

User story: "This story represents the portion of the hardware budget that is remaining for equipment not yet received at NCSA/NPCF"
Answer: 388587.0

User story: "This story will represent the incremental expenses recognized for equipment that has been received at NCSA/NPCF,  The Story points on this story will be updated monthly to reflect the percentage of the budget that we have used."
Answer: 1.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "This story will represent the incremental expenses charged for Power and Cooling,  The Story points on this story will be updated monthly to reflect the percentage of the budget that we have used."
Answer: 1.0

User story: Investigate storing and retrieving of a defects list calibration product from gen 3 butler.    It's not yet clear where the code for doing this would end up. Special formatters will need to be written to ensure that "list of defect" is returned and not an afw Catalog. Need to decide whether it's meas_algorithms or obs_base.
Answer: 9826.0

User story: "When pipetask makes an empty QuantumGraph it would be useful to notify user about that, people get confused if everything looks OK and there are no messages, but then nothing is executed. I think it deserves a WARNING message if graph is empry, maybe we can also print some INFO like number of quanta in a graph.  Understanding why graph is empty is a more complicated (existential) problem, it will be addressed on a separate ticket."
Answer: 1358.0

User story: "The utility {{cameraGeom.showCamera}} (which calls {{cameraGeom.makeImageFromCamera}}) obeys {{Detector.nQuarter}} even though that has already been applied by the ISR.    This is (probably) only an issue for HSC, which is indeed where it showed up.  "
Answer: 39.0

User story: "Each time a release is done, the relevant reference of scipipe_conda_env need to be tagged accordingly.    SQR-016 need to be updated to include this extra manual step."
Answer: 368634.0

User story: "To better support the SLAC build and test system for CCS, the OpenSplice RPM needs to be made relocatable."
Answer: 301273.0

User story: "Take new dataset for monochromator characterization using new configuration values for calsys_takedata.py to see if an issue with an earlier data set is fixed.    Fixing calsys_takedata.py as it somehow became broken. Code was added to finish writing a csv file to user supplied directory that downloaded electrometer and fiber spectrograph fits files. The code was copy and pasted from the narrowband version of the script and was not completely changed over.         Fixes were implemented as part of the following PR - [https://github.com/lsst-ts/ts_externalscripts/pull/4]"
Answer: 35977.0

User story: "Invited presentation on LSST data products for time domain science  at   http://www.mpia.de/homes/calj/ats2019/"
Answer: 20360.0

User story: "Prepare and give a ~50 minute talk to the DSC PSF Task Force, on DM's perspective on PSF modeling."
Answer: 130.0

User story: "In version 3.9 of SAL, it looks like the the function {{mgr.salEvent}}  to publish an event is no longer supported and needs to migrated to {{mgr.salEventPub}} now."
Answer: 10334.0

User story: "Once the Unit tags are filled into the XML, a table or tables need to be generated that map the topic.attribute to a unit and placed in the EFD."
Answer: 273103.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 AT Dome vendor provided a new version based on comments provided as part of DM-18454. This ticket is to test this new version both at the TCP/IP vendor interface level and the CSC level."
Answer: 32700.0

User story: "As an SOC member, assist with proposal for DESC funding for this workshop, logistics, and the scientific content of the meeting. Create a presentation on DM data products (and alerts in particular), attend the meeting, deliver presentation, chair sessions, and take notes. Afterwards, continued participation as DESC prepares their statement regarding DESC needs for an LSST alert broker (their Letter of Non-Intent, LONI).    DESC Brokers Workshop, Feb 21,22   [https://rbiswas4.github.io/BrokerWorkshop/index]    <USER>also created this summary of the meeting https://community.lsst.org/t/report-from-desc-broker-workshop/3601     "
Answer: 28573.0

User story: Invited speaker at the STScI workshop on "Enabling Multi-Messenger Astrophysics" in Baltimore MD, April 25-26. Talk title "The LSST Data Management Systems: Infrastructures for EMMA".    http://www.stsci.edu/institute/conference/emma
Answer: 41269.0

User story: "Prepare and submit LSST-related white papers for the 2020 Decadal Survey.    Astro2020 Science White Paper: Discovery Frontiers of Explosive Transients - An ELT & LSST Perspective, Graham et al. (2019), arXiv:1904.05957    LSST Narrowband Filters, Yoachim et al. (2019), arXiv:1903.06834    Astro2020 Science White Paper: Science Platforms for Resolved Stellar Populations in the Next Decade, Olsen et al. (2019), arXiv:1903.05130         These are three Astro2020 papers on which I’m first or second author, which are related to LSST (and thus informed by my DM-SST work), that were all submitted on March 11 2019 to the call for white papers… but one (my ELT-LSST) was sent to arXiv later (in April; no reason just forgot to post)."
Answer: 28603.0

User story: "Participate, as a DM representative, in Canadian astronomers' efforts to plan for LSST. Assist in creating and interpreting a survey of Canadian astronomers and how they would use LSST data, and help with the creation of an initial document to inform grant proposals for funding to support data centers hosting LSST products (https://www.authorea.com/users/44077/articles/352813-canadian-participation-in-the-lsst). This document will serve as the basis of a full white paper to be submitted in response to a call for white papers for the 2020 Long Range Plan (the equivalent of the decadal survey in the US)."
Answer: 213089.0

User story: "Verification Element issues LVV-4 and LVV-175 both refer to DMS-REQ-0004-V-01 verification element and have the same title.         Only one shall be kept  ([~<USER>) and the other shall be removed ([~<USER>)."
Answer: 200162.0

User story: "Since a count(*) apparently will hit all the worker nodes, seems like a good idea to add it to the queries the monkey runs.  Also we should fix the NN query to select 'monkey' first to keep it separate from other queries."
Answer: 54.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: "Write job specification and recruit"
Answer: 139813.0

User story: "for example {{select MAX(psfFlux) - MIN(psfFlux) as amp from Source;}}  does not parse with {{as amp}}"
Answer: 143938.0

User story: "The system for identifying defects on DM-17490 could be more effective if it could simply flag whole (or partial) columns as bad when they contain obviously-suspicious patterns (e.g. alternating on/off pixels)."
Answer: 77597.0

User story: "Examining the results of the code developed on DM-19334 shows “wiggles” at low count rates. Where are they coming from?"
Answer: 40105.0

User story: "Our first guess at an adequate algorithm to meet the goals of DM-17490 is simply to identify n-sigma outliers, both positive and negative, in AuxTel and TS8 data. Implement that."
Answer: 39023.0

User story: "The HSC detector name was being read from the T_CCDSN header but this value does not match common usage.  The names are defined in the obs_subaru camera geom files of the form RAFT_NUMBER where raft is 0 and 1 and numbers are zero-padded two digits.    Currently raft is not a concept used in obs_subaru."
Answer: 11687.0

User story: "While tech talk where we discussed SAL XML Unit Definition, we suggested that SAL could have a method to get the unit for a value inside the topic. Ideally we would like to do something like;    {{Component_type_topicC.value.unit}}    but I understand this may not be easy to implement. So maybe something like    {{Component_type_topicC.units.value}}    For instance, for ATCamera, wreb, ckPOV, we could either do:    {{SALPY_ATCamera.ATCamera_wrebC.ckPOV.unit}} (preferable)    or     {{SALPY_ATCamera.ATCamera_wrebC.units.ckPOV}}  "
Answer: 319671.0

User story: "ComCam will be taking data soon. Once data files exist with standard headers, update obs_lsst to allow comCam data to be ingested."
Answer: 142855.0

User story: "While validating the fix in DM-19265, it was noted that there are differences in the uber calibration results from both {{jointcal}} and {{meas_mosaic}} between recent weekly runs of the RC2 dataset.  As the plots on DM-19265 show, there have been some subtle changes from {{w_2019_06}}\-to\-{{w_2019_10}}\-to\-{{w_2019_14}}.  The differences are small (stdev of difference is at the sub mmag level), but it is still important that we understand where they originated.  Since both algorithms are affected, the route cause must be something that effects both.  A first guess would be something about how object selection is being done."
Answer: 7562.0

User story: "Implement RFC-591: validate script configuration using jsonschema     Update ts_scriptqueue and also existing scripts in ts_standardscripts and ts_externalscripts"
Answer: 53159.0

User story: "IIPBase class contains logic for configuration file loading and logging. OCSBridge C++ files should inherit from IIPBase class."
Answer: 2975.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: "So trying out the astroquery generic TAP client (called TapPlus), I can make sync requests to the TAP service at lsst-lsp-stable.ncsa.illinois.edu but not async queries.    The main problem seems to be that the async queries don't properly set the phase to run.  Astroquery thinks it did, and is waiting for the phase to end up in COMPLETED, but the server thinks it is in PENDING and never got the change to run.  I'm not sure if this is allowed in the spec and who is in breach of the spec.  Maybe both, even.    Once I set the phase out of band, then I get another exception about retrieving the result, which looks like it's comparing against a 200, although this might end up being a redirect as well.  So that needs to be fixed.    Seems like the astroquery client is promising but could use some work and bug fixes against the CADC TAP service."
Answer: 272051.0

User story: "Currently to run ci_hsc in the Gen3 pipelineTasks,  the config overrides are read from [https://github.com/lsst-dm/demo_hsc_pipelinetask/tree/master/config]     It'd be nice if these config are moved to be within lsst_distrib and kept with the weeklies.     obs_subaru/config cannot be used directly because for example config files for CharacterizeImageTask and CalibrateTask are bundled inside processCcd.  Restructure them to make using them in Gen3 easier. "
Answer: 21088.0

User story: "Give demo of LSST science platform at AURA member reps    Time allocated for each demo is 25 +10 mins.  There will be 3 *  25+10 min identical presentations to 3 groups in the one afternoon."
Answer: 31259.0

User story: "Talk  and demo on LSST science platform  at AURA member reps.     10 mins for the talk and 25 +10 mins for the demo.     There will be 3 *  10 (talk) + 25(demo) +10 (questions) min identical presentations to 3 groups in the one afternoon.         Provide draft to [~<USER> 1 week before meeting "
Answer: 21785.0

User story: "New rafts are being tested in TS8. We need to update the contents in the policy files in obs_lsst to register the new detector serials and locations."
Answer: 1221.0

User story: "Part 2 of the thermal software skeleton."
Answer: 19842.0

User story: Lead the development of [DMTN-107|http://ls.st/dmtn-107]: "Options for Alert Production in LSST Year 1". This is intended to serve mainly as an inward-facing document but will be accessible by the community.
Answer: 30231.0

User story: Lead the development of [DMTN-102|http://ls.st/dmtn-102], "LSST Alerts: Key Numbers" and circulated it to the community.
Answer: 274.0

User story: "Apparently coincident with the merge of DM-18643, there was a significant regression in astrometric metrics associated with validate_drp as tracked by SQuaSH. (e.g. between 2019-04-13 and 2019-04-16, AM1 went from 7.9 to 12.3 mas, AD1 from 14.6 to 119.6 mas, etc). Please investigate what happened and (if appropriate) put in a fix."
Answer: 2977.0

User story: "{{processCcd.py}} on HSC data now writes the {{postISRCCD}} dataset, which needlessly takes up disk space."
Answer: 1193.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: "C++ code files share code for logging and loading configuration files. Those should be put into one class and other classes should inherit from parent class."
Answer: 1342.0

User story: "[~<USER> has pointed out that afw can write a {{ZQUANTIZ}} header keyword (e.g., it is picked up when we read a compressed FITS header we wrote, and then that header is transferred to a new file), which can break ds9's handling of mask extensions.    {{ZQUANTIZ}} is related to how FITS tile compression is done, and so we should never read or write it (we leave it up to cfitsio)."
Answer: 1334.0

User story: "Write the March monthly report "
Answer: 482.0

User story: "To chair the Science Organizing Committee for the 2019 LSST Project and Community Workshop.     To do:    (1) Assemble SOC members (by late April).    (2) Decide on a parallel science workshop (by late April).    (3) Release call for proposed sessions. Liaise with community and solicit submissions.    (4) Review proposals, choose sessions, assign chairs.    (5) Create session schedule, minimizing conflicts.    (6) Liaise with session chairs to ensure they have content and tools for their sessions.    (7) Attend PCW 2019, facilitate Unconference."
Answer: 193142.0

User story: "This ticket is to effectively repeat the relevant portions of the DMTN-006/DMTN-021 analysis for our current HiTS processing to bound our false positive rates.  This ticket is simply to perform the work in a notebook, but it is expected that future work will incorporate relevant portions into the metrics system."
Answer: 66252.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 the way salobj handles command acknowledgement and timeout is a bit odd. Basically, the command workflow is     1 - Remote sends command to a CSC and waits   2 - CSC acknowledge with ack code SAL__CMD_ACK (300)  3 - If long duration command, CSC sends ack SAL__CMD_INPROGRESS (301)  4 - If fast command or when command is completed CSC sends ack code SAL__CMD_COMPLETE (303)    To get the acknowledgment salobj (or any sal subscriber), needs to pool. If no response is seeing the method returns SAL__CMD_NOACK (-301). That behavior occurs regardless if the component is executing a command or not. For instance, once you send a command, and before the component sends the first SAL__CMD_ACK, the sender will receive SAL__CMD_NOACK. The same also happens between SAL__CMD_ACK and SAL__CMD_INPROGRESS and between SAL__CMD_INPROGRESS and SAL__CMD_COMPLETE.     To clarify, assume you send a command to a component and poll the acknowledgment every {{X}} seconds, and the receiving component acknowledges every {{3*X}} seconds. You will basically get    t = 0 - Command send  t = X - SAL__CMD_NOACK  t = 2*X - SAL__CMD_NOACK  t = 3*X - SAL__CMD_ACK  t = 4*X - SAL__CMD_NOACK  t = 5*X - SAL__CMD_NOACK  t = 6*X - SAL__CMD_INPROGRESS  t = 7*X - SAL__CMD_NOACK  t = 8*X - SAL__CMD_NOACK  t = 9*X - SAL__CMD_COMPLETE    On current version of SalObj, when a user sets the timeout it applies to the entire process, until the SAL__CMD_COMPLETE is received.     Nevertheless, most of the time, the user worry about the first acknowledgement (the SAL__CMD_ACK) and not the entire command execution time.    I think we need to improve the way SalObj handles command acknowledgments and timeouts to reflect this behavior.           "
Answer: 32605.0

User story: "read chiller docs, learn about how it likes its packets assembled. This is a duplicate of TSS-3457, which was accidentally created under the wrong project"
Answer: 21640.0

User story: "Confluence page link:   * [https://confluence.lsstcorp.org/display/LTS/17-4-19+Meeting+notes]"
Answer: 11055.0

User story: "h2.    start software development of chiller csc.    Phase 1 includes planning and developing hardware communications layer    this ticket duplicates TSS-3458, which was accidentally created under the wrong project. "
Answer: 41728.0

User story: "There are regular IVOA Exec and IVOA Technical Control Group telecons. Prepare for and call into those."
Answer: 80647.0

User story: "early april work on the ASC, including meetings and reviewing the requirements doc and CSC/T2SA API spec. This ticket duplicates TSS-3459, which was created under the wrong project."
Answer: 12893.0

User story: "Attend the IVOA interop meeting in Paris in May 2019 in my capacity as IVOA Exec member and vice-chair of Data Curation interest group."
Answer: 50354.0

User story: "Update docsteady to add Verification Elements to the Test Spec.         Relevant traceability, including VE status and Test Case status shall be added also."
Answer: 90421.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "During initial refactoring, it wasn't apparent how the Scoreboard and its subclasses were being utilized.  In looking at it now, it appears it has always been doing a reload of the configuration file the main class was loading.  This was discovered  when doing DM-19240 and loading of Credentials had to be put in there until the config reload could be dealt with.  I'm creating this ticket to eradicate the reloading of the config/credential files."
Answer: 2549.0

User story: "[~<USER> writes:  {quote}  I found that some of the defect masks set in hscPipe 6.7 were not  optimal, particularly mis-alignment of defined masks for ccd=78 sometimes  contributed to visible artifacts on coadds. Can we involve these  updates in the next release cut?    Correction to obs_subaru/hsc/defects/201X-XX-XXX/defects.dat  (left:current --> right:updated)    * ccd=12       12    540      0      2    393 -->  12    540      0      3      393    * ccd=23       23    530   3961      8      8 -->  23    530   3961     10      10    * ccd=78       78    163   1892      1   2283 -->  78    164   1892      1      2283       78    166   1898      1      3 -->  78    167   1898      2      4    {quote}"
Answer: 2682.0

User story: "STScI has asked me ([~<USER>) to give an engineering colloquium about LSST's documentation engineering work. Although this is a general talk, it's relevant to the  DM-16250 epic because such a talk describes in detail the template ecosystem that technote creation via Slack exists within."
Answer: 21861.0

User story: "After Robert visit we discussed ways to reorganize the way we write and store SAL Script so the code is mode re-usable from other SAL Script and usable from notebooks. I will implement this reorganization to the currently existing scripts and will write some example notebooks to show how that is achieved. "
Answer: 20302.0

User story: "The script makeSkyMap.py currently uses command line tasks to create and ingest a skymap into a gen2 butler. This ticket will create an equivalent script for the gen3 butler.    This ticket will have a simple command line parser that will not attempt to capture all options or allow setting configs from the command line. That work will be captured by a future ticket which will encompass command line parsing for scripts in a generic way to work across all gen3 middleware scripts."
Answer: 66379.0

User story: "Registering a skymap with a gen3 butler should be done in a transaction block, this should greatly speed up registering."
Answer: 21744.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 paper  _Local monitoring of atmospheric transparency from the NASA MERRA-2 global assimilation system_ is in its final version for internal review ([https://www.overleaf.com/read/yryfbzrdryhm).]    One of the finding is the annual modulation of the various parameters, a signal that is not recovered by the SNFactory observations. The comparison of the MERRA-2 data with the SNFactory findings should be rerun and extended to a larger set of nights in an attempt to  recover the expected seasonal variations."
Answer: 267094.0

User story: "Updated the time I spend this sprint on documentation to focus on getting the csc overview completed. The original titles of this task was to get the templates created for the various code repo's."
Answer: 20209.0

User story: "It looks like we lost the Jacobian from the meas_mosaic photometric solution with this deletion from DM-10156:   [https://github.com/lsst/meas_mosaic/commit/6e395ac11a625c877374f99e2bed771b427835b6#diff-ad69537790bfe1f2b36095cbbc6f80a9L709]   I noticed this in comparing meas_mosaic-calibrated magnitudes between the w_2019_10 and w_2019_14 RC2 reprocessings, which look like:   !compareVisit-v1228-diff_base_GaussianFlux-sky-gals.png|width=450!     "
Answer: 6175.0

User story: "On DM-17549, I wrote some code to “fully resolve” fastavro schemas which are defined in terms of other fastavro schemas.    This feature might be of interest upstream (see e.g. [fastavro#314|https://github.com/fastavro/fastavro/issues/314]). Extract the relevant code from the LSST codebase, package it appropriately, and offer it to the upstream project."
Answer: 781513.0

User story: "The configuration loading and logging are common across all services.   This should be moved into the base class to avoid code duplication and/or errors in referencing."
Answer: 5677.0

User story: "This is to undo DM-18367 changes after Butler close method was removed in DM-18839"
Answer: 7.0

User story: "After DM-19240 and DM-19260 are completed, remove all references to all user/passwd pairs from L1SystemCfg.yaml (and any other YAML files), and remove all of those users from the RabbitMQ broker.    Also do a regression test after removing all this information, and update the software as needed."
Answer: 27127.0

User story: "I added a new credential file into $HOME/.lsst/iip_cred.yaml that should be used as the single user/passwd pair to connect to RabbitMQ.   All C++ code that uses RabbitMQ needs to be updated to use this single user/passwd pair loaded from this directory.  It also needs to check permissions on the directory and file to make sure they're secure, and if they're not, the service should exit."
Answer: 25628.0

User story: "e.g. the query {{SELECT foo from Object}} causes qserv to crash.    InfileMerger correctly returns false when it can't get schema from a query (to create the results table) but somewhere up the chain that false is not getting handled in a way that returns an error to the user, and instead qserv crashes, which is bad."
Answer: 5944.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: "Need to update EXPTIME to capture the request exposure time from the takeImages command.    The computed exposure time from shutter motion profile will be now directed to SHTTIME. Finally, DATE-BEG will be added to comply with LSE-400."
Answer: 14546.0

User story: "DM-18393 requests some DM work to support SLAC.  The lower-level changes are made and ready for review/merge, so I'm moving the rest to this ticket.  Specifically:  {quote}   1) Conversion from Segment & and pixel row, column to global pixel row, column - note that this differs from e2V to ITL    2) Inverse method from X,Y to Raft,Sensor,Segment,pixels that works without knowledge of which Raft,Sensor you are in.    5) X,Y in the CCS (note that this is only a 90deg rotation from the FP system.  {quote}"
Answer: 10485.0

User story: "The bright object masks are set at the database level, but unfortunately only for the tract (or patch?) which contains the bright object.  This means that objects near the edge of a tract are *not* properly masked in the neighbouring tracts.    You can see this by e.g. using hscMap to show masked objects around a bright star near a tract boundary"
Answer: 56516.0

User story: "Help Andrew with TSSW documentation.    Met with <USER>and Andrew to discuss documentation tooling.    Wrote a barebones Java documentation example using Orchid."
Answer: 20459.0

User story: "thorlabs flipper has a purpose as a potential part of a csc. Explore the potential communication protocols. Looking into pyusb as a possible library. Working on solving pyusb permission error. Probably need to write a udev rule to give the device the proper permissions."
Answer: 20460.0

User story: "The notebooks on pontus need a reorganization. Things should be located by username."
Answer: 14675.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: This task will evaluate the integration between influxDB and influx_writer of SAL. This task will also benchmark the performance of InfluxDB to use the SSD, NVME, or hard disk.    Compare the MariaDB quary language and InfluxDB quary language.    Evaluation steps:   # Check with the AT CSC owners with the telemetry rate according to the page: [https://confluence.lsstcorp.org/display/SYSENG/Auxiliary+Telescope+Control+Computers+in+Tucson]   # Clone the ts_sal repository to the /home/<USER> Install the SAL and build the AT CSC test scripts I need. Make sure the sal version is 3.9 and opensplice version is 6.9.   # Change the test telemetry script to run infinity times (iseq in C++) with the correct telemetry frequency (delay_1s in C, the first argument is sec and the second is nano-sec).   # Run the test for SSD, NVME, and Disk.   # The path variable of "LSST_EFD_HOST" gives the IP_address of influxDB.   # I can do "./some_writer >& log.1 &" to run the writer in the background. And I can use "tail -f log.1 to see the log file".   # Once I changed the cpp file, I can go to the "stand_alone" directory and do "make -f Makefile.sacpp_blahblak_pub" to build the code in the same directory.   # I can also do the above modifications by python.
Answer: 18902.0

User story: "This task will document the change of code at this moment and test the sphinx as the documentation tool."
Answer: 24949.0

User story: "This task will use the yaml to manage the configuration files. This task is the phase 2. I need to merge the lsst an comcam configuration files."
Answer: 24952.0

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

User story: "Investigate Kafka for Influx EFD implementation."
Answer: 41365.0

User story: "The flake8 utility needs to be run on the python code."
Answer: 25618.0

User story: "Give software support to M2 at the summit"
Answer: 27019.0

User story: "Put simulator and ATHexpod into a docker container"
Answer: 87567.0

User story: Currently the only directory that can be accessed using WebDAV interface is /datasets, and its only readable, not writable. Opening the home directory with read and write permissions has security issues that might take time to solve.    Firefly needs to be able to create, list, rename, delete directories and files in the workspace.    Create a "playground" WebDAV accessible directory to test Firefly-WebDAV communication. 
Answer: 25867.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:      Queries like "SELECT COUNT( * )  WHERE w1mpro_ep<4.2" where w1mpro_ep is an unknown column can wedge the worker scheduler as the error is failing to trip the error logic in the worker. Improvements should be made so this error is detected.   Further, when sending the result back to the czar, an error is detected in the transmission, which should really cause the task to fail instead of just logging a message.
Answer: 31761.0

User story: "DM-15597 introduced a notebook for analyzing the results of MultiProFit fits to COSMOS galaxies. The existing notebook has become large and unwieldy and needs to be refactored into a package with relevant plotting functions and a separate notebook for each specific science question."
Answer: 79498.0

User story: "Ground based astronomy is often assuming that atmospheric transmission above a telescope is axis-symmetric. The MERRA-2 data allow to test this hypothesis for the various atmospheric components :    the result is reported in manuscript   https://www.overleaf.com/read/yryfbzrdryhm  by combining the lat-lon gradients (bottom panels figures 1, 3, 4) and z-profiles (figures 2, A.5).    The aerosol profiles need to be plotted.     "
Answer: 6728.0

User story: "C++ files have log directory set to current running directories. Those log files should move out from the repo and store at the place where config file specifies log directory is."
Answer: 10201.0

User story: "Async queries don't work well with pyvo, because of uws:result XML elements in the response it looks like.  Works with TOPCAT.  Works without those elements around (this is how pyvo tests it)"
Answer: 85283.0

User story: "Give support to run the m2controller inside the cRio"
Answer: 11709.0

User story: "http://pdc.iaaweb.org/"
Answer: 36676.0

User story: "We need non-root users specified in all Notebook Aspect components in order to meet NCSA security requirements."
Answer: 7927.0

User story: "In connection to DM-18695, create minimal C++ multi thread test program that can be built and run easily with an arbitrary lsstsw stack build. This program is expected to be easier to debug by gdb tools than a pybind wrapped python example."
Answer: 23148.0

User story: "LSP with Authentication and TAP"
Answer: 321369.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "After v18 is released, we can remove the deprecated {{getCalib}}/{{setCalib}} accessors on {{Exposure}} (both in table, and image), {{ExposureInfo}}, and the deprecated {{Calib}}-style interface in {{PhotoCalib}}. "
Answer: 304368.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 Mar 2019 monthly report (/)  - Circulate upcoming milestone list to dm-cams (/)  - Audit and update https://confluence.lsstcorp.org/display/DM/DM+PMCS+Update+Requests (/)"
Answer: 1058.0

User story: "This ticket is to gather minor updates to LDM-612 and LDM-682."
Answer: 77.0

User story: "Add explanatory text to the exploratory dask notebooks so users can follow along."
Answer: 11940.0

User story: "Add fields to settingsVersions event and allow payloads to be maximum  variable string size"
Answer: 202143.0

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

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

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

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

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

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

User story: "As requested by the camera team, some good runs of the old TS8 data are in the dev area so dev runs need to be ingested too. It'd be good if all the TS8 runs were in a single bulter repo. "
Answer: 30690.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 qa scripts in {{pipe_analysis}} were written and tuned based entirely on HSC-SSP data.  Now that we are moving to generalizing the scripts to work on any dataset produced by the lsst stack, certain hard-coded values need to be adapted to be appropriate for the dataset of interest.  As [~<USER> points out in DM-18635, one such setting that requires adjustment is the minimum flux limit used for computing the basic statistics (mean and stddev) for the various metrics.  While it is currently a config parameter (whose default was set for HSC and specified by RHL), it would be even better to set this limit based on a S/N cut (e.g. S/N>100 would also match what {{validate_drp}} is using).  Once the new setting has been tested and shown to be the better option, make it the default, but allow for an override option in the configs to force a fixed mag cut (i.e the current behavior)."
Answer: 254106.0

User story: "Following discussions on DM-18170 and with <USER> I am going to add infrastructure support to astro_metadata_translator to allow files to be written that will contain updates to headers.    I am proposing:    1. Pre-examine the header, determine the instrument and obsid.  2. Look for a file of name relating to the OBSID (yaml or maybe JSON containing override values for specific headers).  3. Apply the corrections from that file to the header.    There will be a standalone function for automatically updating a header, and support inside the ObservationInfo constructor to apply the correction automatically. The location of the correction files is an interesting discussion but will probably be per-translator specific but allow overrides using a PATH-like environment variable."
Answer: 4766.0

User story: "Covers all organizational aspects of and attendance at the Community broker workshop not covered in other specific tickets"
Answer: 151916.0

User story: "Our LaTeX templates are current part of [https://github.com/lsst/lsst-texmf.] Let's move them into the centralized templates repository so that we can make it available to sqrbot/templatebot."
Answer: 31319.0

User story: "Forwarder source has both header and source codes in one place. It should be split into a Forwarder.h."
Answer: 15369.0

User story: "Prepare a poster for the Planetary Defence Conference describing pytrax and the comparison between it and classical MOPS described in DM-16760"
Answer: 38152.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: Some CSCs publish the large file object available event, to inform the EFD of the availability of a file that needs to be stored in the Large File Annex. That is the mechanism used, for instance, by the cameras and header service to broadcast the availability of new images. Other components (like the electrometer and fiber spectrograph) also use this mechanism to broadcast data availability. The currently implemented method is to broadcast an URL so that the EFD can "{{wget}}" the data. This requires to setup and run a http server on the CSC machine to allow the data to be captured.     This task is to provide support for this task in the baseCSC so we don't have to worry about start and monitor the state of a separate process (the http server) concurrently with the CSC.     My proposal is that baseCSC has an option that will make it run a http server. 
Answer: 333329.0

User story: "Validate performance on the SFA 7990 with understanding that it is currently only populated with 20 drives for the initial configuration."
Answer: 5003.0

User story: "1) Build disk pools on the SFA 7990    2) Create GPFS L1 Cluster on the SFA 7990    3) Create GPFS L1 File System on the SFA 7990    4) Create racking/un-racking procedures for the SFA 7990"
Answer: 23681.0

User story: "Get the 2 L1 Handoff Servers set up with a base image and prepare them so that they can be provisioned and re-provisioned once installed at the base.     1) Build OS Raid virtual disk    2) Get MAC addresses for integration with base xcat"
Answer: 23679.0

User story: "Need to update and test the HS once CCS is updated on the NCSA L1 TestStand to remove the 1e6 factor in the timeStamp that went from micro seconds to seconds"
Answer: 1307.0

User story: "Forwarder log file are in the format Forwarder-001. That causes confusion when forwarder is restarted and cannot store the same file since the only distinguisher between old and new log file is incremental number at the end.     So, new format will be Forwarder-YYYY-MM-DD-001."
Answer: 12039.0

User story: "Python3 is used to be installed in custom place. Right now, it is in default python install location and systemd unit files need to be updated to reflect python3 location."
Answer: 215315.0

User story: "Run.py currently does not support timer option. Timer is used to add sleep timer between running commands."
Answer: 60.0

User story: "Currently toolsmod.cpp file doesn't have log output and hard to debug. It should have a separate log file."
Answer: 120568.0

User story: "Forwarder would break when it is compiled with different versions of boost from dependency libraries. One way to fix this is add a rule on Forwarder makefile to recompile everything whenever forwarder is changed."
Answer: 15765.0

User story: "This also involves updating how {{validate_drp}} discovers specs in the report making process."
Answer: 13200.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_18. Steps include {{makeSkyMap.py}}, {{singleFrameDriver.py}}, {{mosaic.py}}, {{skyCorrection.py}}, {{coaddDriver.py}}, and {{multiBandDriver.py}}. "
Answer: 50713.0

User story: "Following RFC-575 and DM-17029, Update the 5 reference catalogs in {{/datasets/refcats/htm/}} to have nJy fluxes using meas_algorithms/bin/convert_refcat_to_nJy.py    More details at https://community.lsst.org/t/photocalib-has-replaced-calib-welcoming-our-nanojansky-overlords/3648     The code convert_refcat_to_nJy.py updates the catalogs from {{v0}} to {{v1}} refcats in place.  So before converting, make a copy of all directories remained in {{v0}}, and keep those copies around for people using the stack older than w_2019_14.     For consistency of the HSC-RC2 DM-18300 run, don't start the actual converting before the w_2019_14 run is done. "
Answer: 102332.0

User story: "Per request on DM-17121 by [~<USER>, this report should include a discussion of computational performance (not just the “Computational performance metrics were not re-measured for this release”) line."
Answer: 135631.0

User story: "This ticket exists to capture issues blocking the 18.0 release of the Science Pipelines."
Answer: 147316.0

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

User story: "We need to auxiliary diagnostic scripts to monitor the payload from the LFO messages from HeaderService and EDF. These need t be updated."
Answer: 5895.0

User story: "Adding globus functionality to the Data Transfer Client or DTC     "
Answer: 165962.0

User story: "Run jointcal with HSC-RC2 and w_2019_14"
Answer: 5.0

User story: "Special considerations must be allowed for:   # Test stand simulated Chile Network Link   # WAN simulator   # Test Stand simulated NCSA network link. Unable to render embedded object.      "
Answer: 298151.0

User story: "testing to be completed by developers"
Answer: 343328.0

User story: "Unpack, rack, and cable the forwarder systems for ComCam."
Answer: 166083.0

User story: "This is a story in our epic for when the ComCam systems arrive in Tucson. They will need to be unboxed and racked and ready for our team to begin configuring on the start date of the epic (July 15th)"
Answer: 166085.0

User story: "HTCondor execute directories will need to be located inGPFS to have sufficient capacity. SET suggests we start by using existing space in /scratch for our initial testing"
Answer: 206323.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: "Evaluate resource needs for the VMs (schedd/submit in particular, also central mgr) will need to be evaluated and increased/managed during testing. Capacity is available in the near-term to scal RAM and CPU for the schedd/submit VM even beyond what is available on spare lsst-dev-01-like hardware if needed (24 cores, 256G), but can likely proceed incrementally"
Answer: 298294.0

User story: "follow-on work related to findings of security vetting"
Answer: 475655.0

User story: "Security vetting of HTCondor test clusters"
Answer: 439564.0

User story: "Create and implement group for access to schedd nodes. Ensure that administrative functions are restricted to sysadmins"
Answer: 166150.0

User story: "Configure HTCondor to make sure that jobs execute as the user who submitted the job, not root (also not a slot user)."
Answer: 166151.0

User story: "Determine how many/what LDAP users and groups are required. Create them and implement HTCondor to use them"
Answer: 206269.0

User story: "Add configuration where necessary via Puppet in consultation with offline services staff"
Answer: 206269.0

User story: "Currently the output generated from the c++ single file programs are not descriptive enough. This makes it difficult to be parsed by the current automated test pipeline in place. This task is to modify the output to be more descriptive.     Example of the desired output is in the following link  https://docs.google.com/document/d/1M3ZDKKYpGXBDOgwese2kYT_cisGXg8y6JT040SHNxPU/edit"
Answer: 24746.0

User story: As of 2019-04-08, [Jenkins is failing|https://ci.lsst.codes/job/sqre/job/infra/job/documenteer/436/display/redirect]. Error is:  {code}      File "/j/ws/sqre/infra/documenteer/doc_template/home/.local/lib/python3.7/site-packages/sphinx/environment/__init__.py", line 785, in get_doctree      with open(doctree_filename, 'rb') as f:  FileNotFoundError: [Errno 2] No such file or directory: '/j/ws/sqre/infra/documenteer/doc_template/_build/doctree/py-api/lsst.meas.base.PhotoCalib.doctree'    Exception occurred:    File "/j/ws/sqre/infra/documenteer/doc_template/home/.local/lib/python3.7/site-packages/sphinx/environment/__init__.py", line 785, in get_doctree      with open(doctree_filename, 'rb') as f:  FileNotFoundError: [Errno 2] No such file or directory: '/j/ws/sqre/infra/documenteer/doc_template/_build/doctree/py-api/lsst.meas.base.PhotoCalib.doctree'  {code}
Answer: 10795.0

User story: "Fix forwarder sender so that it can be used in multiple test stands."
Answer: 96.0

User story: "The estimation of the annual and overnight variations of the atmospheric parameters were based on 1-sigma RMS statistics. Given the non normal distribution of the recorded values, a percentile interval does a better job at capturing the parameters' space -> the text in the paper (1 ) has been edited and the last figure has to be redrawn.  (1) https://www.overleaf.com/read/yryfbzrdryhm"
Answer: 11273.0