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-19873 is changing the API of PropertySet.get() such that it will now return a default value rather than raising KeyError. Before that can happen, all extant calls to {{get()}} must be replaced to avoid any surprises.    The approach I will take is to change get() so that it always throws an exception and then wait for tests to fail. This may lead to some remaining usage of {{get()}} in code that is not used."
Answer: 1425.0

User story: "The Script and ScriptQueue XML both use topic-specific enumerations when shared would probably be better (and certainly more common).    This is especially important for Location but also useful for ScriptState and ScriptProcessState. I am less convinced about the three metadata enumerations, but using the same technique for all is simplest."
Answer: 285.0

User story: "Following the adoption of RFC-596:  * Add getitem support (returning scalars in all cases)  * Undeprecate {{get()}}, modifying it to return scalars and to support a default value.  * Investigate adding {{update()}} method."
Answer: 7070.0

User story: "The bootstrap scripts added on DM-19638 upgrade Gen2's dates to Gen3's datetimes without adding one day to the end dates.  Because those intervals are inclusive instead of half-open, that means we end up with a day-long gap between adjacent intervals."
Answer: 1429.0

User story: "bench-marking of DTC w/globus"
Answer: 167123.0

User story: "Add tests on ts_xml for <Unit> and <Description> fields, in accordance with [https://confluence.lsstcorp.org/display/LTS/SAL+XML+Unit+Definition+-+Discussion].  Also, add tests for XML Version; see VERSION file in the repo."
Answer: 27774.0

User story: "Now that we have a new way to ingest DECam defects, we need to update ap_verify and the two ap_verify datasets (ap_verify_hits2015 and ap_verify_ci_hits2015) to use this new mechanism."
Answer: 43018.0

User story: Please increase the vertical space available in the MOTD div on the LSP landing page, so that more of each message can be displayed.  Roughly 2.5x the current space available would be about right.    If possible, please detect when the message is truncated and automatically supply a "More..." or similar link to indicate to the user that it has been truncated and that there is a way to see it all.    Also, please add a link below this div that provides the "Click here for the complete message history" functionality which is currently being manually inserted into every message.    It would also be useful to have a space on the page, _not_ part of any individual message, for the "mission statement" for the instance on which it's deployed.    Finally, please find a way to support both instances at the same time at the tip of the {{master}} branch and with the same container image.
Answer: 194071.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: [~<USER> suggested that there is a better way to write a query that selects datasets when there are multiple collections defined. Presently we do a JOIN of two sub-queries where one of them does a GROUP BY to determine "best" collection for the dataset. The same can be rewritten using the window/anlytics functions instead.
Answer: 222976.0

User story: "This task also includes adding the INSTPORT keyword as well as the WCS keywords that are specific to the instrument (pixel/plate scale)."
Answer: 198701.0

User story: "The generation of Quantum Graphs is currently taking enough time that we'll need the ability to start with an existing Quantum Graph.  This will greatly speed up debugging BPS bugs as well as help the current milestone since the generation of RC2 sized Quantum Graphs is currently taking multiple hours."
Answer: 17230.0

User story: "DM-19566 implemented gradient and Jacobian evaluation for Gaussian mixture models in MultiProFit. This ticket will actually use the Jacobians in fitting by determining the mapping from fit parameter gradients -> Gaussian parameter gradients."
Answer: 60435.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: "Dear Paul-san, Jim-san, and all,    As we discussed before, I am reviewing the defect masks which are set  in singleFrameDriver.py. I realized the singleFrameDriver.py produces  very high values in area masked by defect list, especially for CCD=33  that has a large defect area. Such high values around the CCD edges  sometimes cause undesired streaks surviving on coadd images.    See the attached figure (stripes_z_101092_101096.jpg) (left: coadd in  a patch, middle: a warp in the same coordinates, right: another warp).  In the warp figures, light green areas corresponds to the defects. We  see that streaks on coadd presumably caused by the outlying values  around the CCD edges due to defects mask. Particularly, the largest  rectangular green is for the defect mask of CCD=33, which covers  neighboring 2 channels. For reference, I also attached snapshots of  CORR images for CCD=33 and 0, where CCD=33 has a large defect area on  the entire left-handed side of the pixels, and CCD=0 has a 1-channel  defects located between the healthy ch-1 and 3.  The defect on CCD=0 seems to be somehow interpolated, but CCD=33's  seems to be disturbed.    These resultant (high) values are undesired themselves, but if the  mask bit (BAD) works perfect, those would be eliminated on coadds, and  that should be ok. However, the actual coadd shows some fraction of  streaks.  (CCD gaps are filled by NaN on warps, and those seem to be decently  clipped by coadds).  Note that CCD=33 is the most prominent CCD that causes the present  problem, but the other CCDs are also set defect masks around the edges  and middle of the CCD.    I think we want to gently ignore pixels masked by defect list, rather  than having such high and regular values, or reasonably interpolated  or filled with more harmless value.  Also mask bit should cover these defect area on coadds more carefully?    I think this is a relatively highly demanded fix, but understand time  is pressing.  Do you have ideas of something we could try to track down this issue  before going into the upcoming production?    Hisanori"
Answer: 28936.0

User story: "Fix landing page and get it to deploy."
Answer: 142576.0

User story: "The PSF calculated for DcrCoadds in DM-19517 fails in some cases for Decam data. The source detection task that was used incorrectly scales the source detection threshold, and can result in no sources being detected. The detection Task should be switched to the base version, and it should possibly only be a warning if psf measurement fails, rather than an error."
Answer: 41421.0

User story: "We need to get SODA and metaserv and maybe image serve running in the new clusters.  Now that we've agreed to new namespaces, I also need to fix that.  There are also unused PVs in places that need to be cleaned up."
Answer: 114.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: Support the use of PhoSim eimage in scientific pipeline. After the discussion with Simon, it looks valuable to support this function in obs_lsst level.         He suggested to create a task class inherited from PhosimParseTask in:    [https://github.com/lsst/obs_lsst/blob/master/python/lsst/obs/lsst/phosim.py]    Override the getDestination() in ParseTask class for the hard coded "raw_filename":    [https://github.com/lsst/pipe_tasks/blob/master/python/lsst/pipe/tasks/ingest.py]    Use the ingest.py for the retargeting of eimage if it is needed:    [https://github.com/lsst/obs_lsst/blob/master/config/phosim/ingest.py]    We should be able to ingest the eimage directly by the changing of configuration.         For the data access, we could just reuse the template in eimage in lsstCamMapper.yaml:    [https://github.com/lsst/obs_lsst/blob/master/policy/lsstCamMapper.yaml]    This means we should not need to modify the code to access the eimage data. When the data butler tries to get the data, we only need to set the data set as the "eimage".
Answer: 33208.0

User story: "Go from dax-int to lsst-lsp-int-dax, dax-stable to lsst-lsp-stable-dax"
Answer: 187.0

User story: "We've done some work with figuring out the ingress rule for auth, so I'm checking that in (which did work) before the migration today.  There's also some helper scripts to turn it on and off and replace it with the other rule."
Answer: 19.0

User story: "learn about scripting tools, and write integration test for aux tel slewing"
Answer: 28961.0

User story: "need to setup a windows server with a static IP on the LSST network, with a SpatialAnalyzer license. It will host the vendor's T2SA application, which is an intermediary between the alignment CSC and the laser tracker hardware."
Answer: 110817.0

User story: {{newinstall.sh}} currently executes (at least) two {{conda}} commands that have changed semantics in miniconda 4.6 (we are currently using 4.5.12).    {{conda clean --lock}} in line 505 is no longer supported (this functionality has been removed).  The fix is to remove the line.    {{conda env update --file}} in line 532 insists on a {{.yml}}, {{.txt}}, or {{.yaml}} extension on the filename.  One simple fix is to add {{tmpfile="$\{tmpfile\}.yml"}} at line 511.
Answer: 240791.0

User story: "https://jupyter-workshop-2019.lbl.gov/    I'm giving a half-hour talk."
Answer: 54416.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: In working on DM-19189, I have been looking at the S/N distributions of the various fluxes  (raw instrumental and calibrated) from single frame processing (where here {{S/N = flux/fluxErr}} from the catalog).  The S/N distributions look as expected for the raw instrumental fluxes, the calibrated values based on application of the photoCalib of {{jointcal}} outputs, and the {{meas_mosaic}} solution using the "old style" calibration (i.e. using {{meas_mosaic}}'s own {{applyMosaicResultsExposure()}} function – which uses the persisted {{fcr}} dataset to apply the calibration).  However, the S/N distribution when applying the {{photoCalib}} from {{meas_mosaic}} is not at all as expected (plots to be attached). Look further into this pathology and what might be causing it.
Answer: 24424.0

User story: "set up the review slide deck .. help to structure the sessions ahead of DMLT F2F"
Answer: 20079.0

User story: "It was noted on DM-19818 that the interaction between Butler construction and pickling is quite fragile due to overuse of positional arguments.  We should consider forcing kwargs for everything past the first positional argument to {{Butler.\_\_init\_\_}}, but this will require a change to pickling, which relies on {{\_\_reduce\_\_}} and hence requires positional arguments.  Using {{\_\_getnewargs_ex\_\_}} may be an alternative"
Answer: 364365.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 Apr 2019 monthly report (/)  - Circulate upcoming milestone list to dm-cams (/)  - Audit and update https://confluence.lsstcorp.org/display/DM/DM+PMCS+Update+Requests (/)"
Answer: 41985.0

User story: "Implement a stress safety limit based off discussions with Ed and Doug.         Ed is providing the matlab code to be implemented in C++."
Answer: 5627.0

User story: "* Capture the experimental code branches in {{ip_diffim}} that implements the same renormalization principles in AL kernels but use different Gaussian sigmas.  * Attach notes about the running results of these experiments."
Answer: 115337.0

User story: "Development on New Scarlet during the Deblender Integration Sprint was rapid. Run the latest version of the scarlet and subsequent steps (which will run without crashing) the the chosen validation dataset.     "
Answer: 9.0

User story: "This package should be a re-runable repository that does the same processing as ci_hsc, but using gen3 middleware. This package will not duplicate the data stored in ci_hsc but link against it, and thus will depend on ci_hsc"
Answer: 73492.0

User story: "https://nbviewer.jupyter.org/github/lsst-dm/demo_deblender_sprint/blob/notebook_cmodel_scarlet_vs_sdss/notebooks/scarlet_vs_sdss_cmodel.ipynb"
Answer: 167.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: "Prototype landed on https://github.com/lsst/scarlet/tree/new_shift.        https://github.com/lsst-dm/demo_deblender_sprint/tree/master/images   See callstack_profile2.png for speed improvement of prototype. "
Answer: 171.0

User story: "[~<USER> will present the Options for alert processing LOY1 at the PST F2F meeting 1-2 July.  The presentation should summarise the options presented in the paper"
Answer: 54694.0

User story: "The consensus on RFC-597 was that the [return value policy rule|https://developer.lsst.io/pybind11/style.html#the-reference-internal-policy-shall-be-used-for-functions-or-properties-giving-write-access-to-internal-data-members] in the pybind11 style guide is unneccessary, so remove it. Developers will be expected to directly apply the pybind11 documentation concerning return value policies."
Answer: 28479.0

User story: "Setup the linux desktop returned by IT. The system OS was re-installed. This task will install the needed application and personal settings for the software development environment."
Answer: 4389.0

User story: "SLAC needs a copy of the Hexapod Rotator management pc software"
Answer: 37525.0

User story: "Building QuantumGraphs at even moderate scale with deferred dataset_id queries (as is required by SQLite) is quite slow, probably because we're running many more of these queries than we need.  See if we can cache the results in Python while iterating over results from the big query instead."
Answer: 12969.0

User story: "The savepoints used to implement nested transactions are taking the bulk of the time in raw and calibration in Oracle.  See if we can implement lighter-weight, Python-side nested transactions for at least some operations."
Answer: 450575.0

User story: "The AOD determination from the gemini observations are difficult to interpret and    an hypothesis is that the large scatter maybe due to cloud coverage. This appear not to be the case when looking at MERRA-2 inst3_3d_asm_Nv tables, (CLOUD from [https://gmao.gsfc.nasa.gov/pubs/docs/Bosilovich785.pdf])     see result --> [^ctio_CLOUD.list]"
Answer: 5106.0

User story: "Per https://github.com/lsst-dm/alert_stream/issues/23, when {{sendAlertStream.py}} tries to read a file which contains no data, it throws a {{ValueError}} with a pretty obscure traceback. Please handle this more gracefully."
Answer: 9973.0

User story: "Run full ci_hsc in Gen3 using weekly software release and Pegasus. Use Oracle backend if possible, otherwise sqlite3. Report any issues to appropriate dev teams.  "
Answer: 22720.0

User story: "Run full ci_hsc in Gen3 using weekly software release and Pegasus. Use Oracle backend if possible, otherwise sqlite3. Report any issues to appropriate dev teams.  "
Answer: 5829.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: With stack {{w_2019_19}} and a {{ci_hsc}} repo, I can run the "processCcd" of one CCD:      {noformat}  pipetask -d "visit=903334 and detector=22" -j 1 -b /project/<USER>bps_ci_hsc/w_2019_19/ci_hsc/DATA/butler.yaml -p lsst.ip.isr -p lsst.pipe.tasks  -i raw,calib,ref/ps1_pv3_3pi_20170110  -o out run -t isrTask.IsrTask:isr -C isr:$OBS_SUBARU_DIR/config/hsc/isr.py -t characterizeImage.CharacterizeImageTask:cit -C cit:$OBS_SUBARU_DIR/config/charImage.py -C cit:$OBS_SUBARU_DIR/config/hsc/charImage.py -t calibrate.CalibrateTask:ct -C ct:$OBS_SUBARU_DIR/config/calibrate.py -C ct:$OBS_SUBARU_DIR/config/hsc/calibrate.py  {noformat}    This finishes without problems.      Using DM-19638 we now can build a Gen3 HSC-RC2 repo. I got a repo with sqlite registry, and did the equivalent for another CCD:   {noformat}  pipetask -d "visit=1228 and detector=40" -j 1 -b /project/<USER>gen3repos/w_2019_19/lite/repo/butler.yaml -p lsst.ip.isr -p lsst.pipe.tasks  -i raw/hsc,calibs/hsc/default,refcats/ps1_pv3  -o out run -t isrTask.IsrTask:isr -C isr:$OBS_SUBARU_DIR/config/hsc/isr.py -t characterizeImage.CharacterizeImageTask:cit -C cit:$OBS_SUBARU_DIR/config/charImage.py -C cit:$OBS_SUBARU_DIR/config/hsc/charImage.py -t calibrate.CalibrateTask:ct -C ct:$OBS_SUBARU_DIR/config/calibrate.py -C ct:$OBS_SUBARU_DIR/config/hsc/calibrate.py  {noformat}    After the log messages   {noformat}  calibrate INFO: Loaded 1474 reference objects  calibrate WARN: Catalog pm_ra field is not an Angle; not applying proper motion  {noformat}  it failed with     {noformat}    File "/software/lsstsw/stack_20190330/stack/miniconda3-4.5.12-1172c30/Linux64/meas_astrom/17.0.1-8-g7a3d54a+18/python/lsst/meas/astrom/astrometry.py", line 152, in run      res = self.solve(exposure=exposure, sourceCat=sourceCat)    File "/software/lsstsw/stack_20190330/stack/miniconda3-4.5.12-1172c30/Linux64/pipe_base/17.0.1-2-g3e5d191+31/python/lsst/pipe/base/timer.py", line 150, in wrapper      res = func(self, *args, **keyArgs)    File "/software/lsstsw/stack_20190330/stack/miniconda3-4.5.12-1172c30/Linux64/meas_astrom/17.0.1-8-g7a3d54a+18/python/lsst/meas/astrom/astrometry.py", line 196, in solve      epoch=expMd.epoch,    File "/software/lsstsw/stack_20190330/stack/miniconda3-4.5.12-1172c30/Linux64/meas_algorithms/17.0.1-13-g1d86082b+1/python/lsst/meas/algorithms/loadReferenceObjects.py", line 324, in loadPixelBox      return self.loadRegion(outerSkyRegion, filtFunc=_filterFunction, epoch=epoch, filterName=filterName)    File "/software/lsstsw/stack_20190330/stack/miniconda3-4.5.12-1172c30/Linux64/meas_algorithms/17.0.1-13-g1d86082b+1/python/lsst/meas/algorithms/loadReferenceObjects.py", line 415, in loadRegion      if not hasNanojanskyFluxUnits(refCat.schema) or not getFormatVersionFromRefCat(refCat) >= 1:  TypeError: '>=' not supported between instances of 'NoneType' and 'int'  {noformat}      Don't think this has to block the merging of DM-19638 tomorrow, hence a separate ticket. 
Answer: 988.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: "Generate Coadds with Fakes.  Run Multiband with both the SDSS Deblender and Scarlet Deblender on coadds with and compare output on fakes. "
Answer: 5452.0

User story: "Identify which patches from 3 different SkyMaps overlap HST (COSMOS and CANDELS) data. Create a notebook to demo how to present Scarlet models side by side with HST and HSC.. "
Answer: 5460.0

User story: "Specifically, look at the runtime as a function of footprint size and number of peaks.  Provide plots indicating distributions and cumulative functions for both."
Answer: 5413.0

User story: "Profile New Scarlet call stack to see where time is being spent. First step in speeding up the new deblender to a scalable run time.    Results:   [https://github.com/lsst-dm/demo_deblender_sprint/blob/master/docs/callstack_profile.md]   [https://github.com/lsst-dm/demo_deblender_sprint/blob/master/images/callstack_profile.png]"
Answer: 5410.0

User story: "dds ts_salobj has switched to using VOLATILE durability for command_<name> and ackcmd SAL topics (both for publishers and subscribers), in order to prevent historical data from confusing CSCs and remotes. CSCs should only respond to new commands, not historical commands, and similarly historical replies are not useful for remotes.    I have two questions:  - Do our EFD requirements prevent this?  - Will it be a problem if ts_salobj does this and other SAL components (written in other languages) do not?    Note: ts_salobj does not call {{wait_for_historical_data}} for these topics, since there won't be any historical data."
Answer: 172609.0

User story: In ts_salobj DM-19385 I coded {{Domain.tai_utc}} to return a hard coded number, with the intention that the code be changed to use a better solution (e.g. emulate ts_sal) at some point. This ticket is for that "better solution".    Also we need a function that returns the current TAI, not just tai_from_utc. Most of the time we only want the current time. The main use case for tai_from_utc is converting the received time sample metadata provided by DDS to the private_rcvStamp field in read DDS samples. See DM-21097 for that function.    I propose to use astropy. But we have to update astropy whenever a leap second was due and it will probably give slightly incorrect answers near a leap second. To quote a warning from the documentation for {{astro.py.time.TimeUnix}}:  {code}  NOTE: this quantity is not exactly unix time and differs from the strict      POSIX definition by up to 1 second on days with a leap second.  POSIX      unix time actually jumps backward by 1 second at midnight on leap second      days while this class value is monotonically increasing at 86400 seconds      per UTC day.  {code}  and {{astropy.time.Time.now()}} uses {{datetime.utcnow}} and the {{datetime}} library does not handle leap seconds.
Answer: 188435.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: "Skip sources with no flux in {{meas_extensions_scarlet}} to speed up runtime. This will require keeping track of the index for each source before and after scarlet is run to make sure that the correct sources are matched together."
Answer: 590847.0

User story: "Wrong unit in meas_extensiosns_scarlet.   "
Answer: 5760.0

User story: "Fix the two bugs identified by Yusra in DM-19759:    1. When exposures have different sized PSFs in different bands it fails AFW fails to make a PSF image.  2. Some sources have so little flux that the sum of flux across all bands is less than zero, indicating that the source is just noise.    To fix (1) the plan is to fix {{afw.MultibandExposure.computePsfImage}} in {{meas_extensions_scarlet.deblend}} for the current sprint, and implement the change into {{afw}} next week.    To fix (2) the plan is to skip all sources that are too faint to be initialized as a {{PointSource}}."
Answer: 5773.0

User story: "Produce a revised version of the requirements proposal in LCR-1554, to take into account concerns expressed at the voting stage by Austin and Bill G."
Answer: 172740.0

User story: "We need to make the query progress available to the user. We think we want to do this via SHOW PROCESSLIST - but this should be verified with [~<USER>"
Answer: 9970.0

User story: "Provide feedback on  https://test-www.lsst.org/lsst-information-scientists    especially the key-numbers pages (if nothing else)     Feedback to be provided via:   https://forms.gle/23N71QNxWtaAzPrW8"
Answer: 291930.0

User story: "Compiled C++ program does not detect the USB Spectrograph (FiberSpectrograph) connected to the Linux machine. Debugging to figure out if its a hardware or software issue"
Answer: 38673.0

User story: "NOAO/Tucson CIS is planning to re-plumb the core network on Saturday, 2019-05-18.  DM Jenkins OSX builds will need to be disabled/reenabled before/after this work and a console cable will need to be connected to the SQRE layer3 switch for manual reconfiguration."
Answer: 6032.0

User story: "Debug CFITSIO library error and get the .so file working with the current version of fits library. This is a prerequisite to update FiberSpectrograph code to use SAL version 3.9."
Answer: 38730.0

User story: "<USER>has started working on Rotator and has sent us a bunch of questions. This task will be used to support SLAC and also to backup harddrive of Management PC without which Tony would not be able to operate the rotator. "
Answer: 13225.0

User story: "{{--longlog}} is logging times with 12-hour formatting and no timezone.  Fix this in Gen2 CmdLineTask and Gen3 cmdLineFwk."
Answer: 365.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: "Since we didn't have a refcat with coordinate errors, I couldn't write a test of jointcal's use of them. And thus I got it wrong: disabling {{config.astrometryReferenceErr}} resulted in an exception because the error field is {{coord_raErr}} not {{coord_ra_err}}!    Unrelatedly, but I might as well fix it as part of this work: it looks like jointcal is trying to apply colorterms when loading the astrometry reference catalog. That is both not necessary, and unhelpful when the astrometry refcat doesn't have useful photometry (e.g. Gaia). Might as well fix that on this ticket, too."
Answer: 19894.0

User story: "Integrate the WEP into MTAOS."
Answer: 16.0

User story: "The test should set a starting altitude, azimuth and tracking_duration. It will then check that as tracking occurs that no CSCs go into a fault state. "
Answer: 48824.0

User story: -I have created a "symlink repository" for HSC at {{/scratch/parejkoj/hsc}} (should be group-writeable by {{lsst_users}}), which we can use to do a trial run of processing data with the Gaia DR2 catalog in jointcal and/or processCcd. This is easier than moving data or symlinking into the read-only {{/datasets/ref_cats}}.-    We now have a {{/datasets/refCats/htm/v1/gaia_DR2}} symlink to my {{/scratch}} gaia refcat, which we can use to do a trial processing run with this new catalog in jointcal.    [~<USER>: can you please help me start an appropriate HSC run (PDR1, RC2 or something else small-ish I don't really care) using this? I'm not sure what we need to do to test it other than just demonstrating that it runs to completion: it has more sources than Gaia DR1, but not more than PS1, and it's still only usable for astrometry.
Answer: 30535.0

User story: "Prepare for the upcoming workshop, review code and build instructions, review documentation and suggest improvement, update agenda and add details"
Answer: 49130.0

User story: "Review the current EAS XML and add items as necessary to cover the entire EAS sensor suite in type and number. Create ts_sal runtime thereof."
Answer: 184312.0

User story: "Rebuild the SAL  V3.9 and OpenSplice V6.9 for the Raspberry Pi environment and create an SDK image for use by the EAS contractor"
Answer: 48983.0

User story: "A dataset defined in one section of a policy (e.g. {{datasets}}) can be re-specified in a different section (e.g. {{exposures}}) causing problems.  (Of course, if the re-specification is in the same section in separate policy files, the policies are merged, as intended.)  Add a check to raise an exception in this case."
Answer: 77.0

User story: "Take a free course ([Scalable Microservices with Kubernetes)|https://classroom.udacity.com/courses/ud615] on Udacity to learn the Kubernetes with the microservice."
Answer: 9936.0

User story: "Test the AOCLC with PhoSim and the WEP and OFC interface classes. This is to test the updated code in the [DM-19749|https://jira.lsstcorp.org/browse/DM-19749]."
Answer: 15627.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 the AOCLC (simulation only, not a CSC) to use the WEP and OFC interface classes). This is to make Chris easier to integrate the PhoSim with MTAOS. This is because both the simulation (without MTAOS) and control modes (with MTAOS + SAL) will use the same WEP and OFC interface classes."
Answer: 15587.0

User story: After evaluating {{minikube}}, {{microk8s}} and {{k3s}} we decided to use {{ks3}} for a single machine deployment of the DM-EFD which will be tested at the lab.    This story captures the work to adapt ourTerraform deployment to support k3s and test the deployment locally (on a laptop) and on the "EFD machine" at the lab.      If necessary we can have an actual cluster adding more workers to k3s.
Answer: 14609.0

User story: "Create documentation for:   * Document how M2 is connected to the computer   * Document how to configure AuxTel Dome cRios    * Document how to configure PI Hexapod"
Answer: 51631.0

User story: "Test new release for the cRio software for ATDome. This should stop shutter commands when using the emergency stop."
Answer: 9763.0

User story: "Update the atptg_ataos integration test to include getting target status from the atmcs instead of the atptg component for the ataos."
Answer: 41936.0

User story: "DM-19731 revealed that some of other logic for using cameraGeom to manipute WCSs is bad, at least on HSC (captured in DM-19734 and DM-19735).  We should check (I'm thinking visual inspection of CCD boundaries, but I'm open to ideas) that TAN_PIXELS is doing what we think it ought to be doing as well.    I should add that it's not entirely clear to me what TAN_PIXELS should be doing, and particular whether it ought to make sense from the perspective of looking at the whole focal plane."
Answer: 72273.0

User story: "In order to implement symmetry in the new deblender we need to move to a model that allows components to have more control over the parameters they require (to include fractional pixel shifts dy and dx) and how their updates are calculated (to calculate updates to dy and dx). This requires an update to scarlet."
Answer: 43494.0

User story: "Gen3 ingest needs to be able to generate inclusive on-sky regions for all visits, using raw WCS and potentially camera geometry.  As those initial WCSs are inaccurate, we expect to need to pad somehow to ensure the region always includes the true region, even if it's much larger.    As a result, we need to look at the difference between some initial HSC WCSs and their post-astrometry counterparts.    This investigation could also be informative for future attempts to fit initial astrometry with as few free parameters as possible."
Answer: 5622.0

User story: "Per RFC-595 and the prep-work done in DM-18739, convert {{obs_decam}} to use the new style defects.  This will require creating a repository called {{obs_decam_data}}."
Answer: 60333.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: "Per RFC-595 and the prep-work done in DM-18739, convert {{obs_cfht}} to use the new style defects.  This will require creating a repository called {{obs_lsst_cfht}}."
Answer: 60334.0

User story: "Per RFC-595 and the prep-work done in DM-18739, convert {{obs_lsst}} to use the new style defects.  This will require creating a repository called {{obs_lsst_data}}."
Answer: 60312.0

User story: "It turns out that the Indexed refcat ingester does not output parallaxes, even though there are config options for them. We need parallaxes, so we need to fix this. First step would be adding parallax and parallax error fields to {{test_htmIndex.py}} and showing that they don't show up in the output files."
Answer: 106459.0

User story: "The {{prometheus-operator}} chart, in addition to providing CRDs for configuring prometheus scraping, bundles some extra goodies, such as grafana dashboard, that are not present in the {{prometheus}} chart."
Answer: 55823.0

User story: "Used to be study gravitational perturbation terms (and for general familiarization with algorithm, etc)."
Answer: 377549.0

User story: "What is the contamination fraction of valid clusters from pytrax?"
Answer: 377394.0

User story: "Summarize the results from DM-16761 and DM-16219 in [DMTN-109|https://github.com/lsst-dm/dmtn-109]."
Answer: 230974.0

User story: "Modify multiband.py deblender command line task to use meas_extensions_scarlet instead of the scarlet functionality in meas_deblender"
Answer: 8448.0

User story: "[LDM-502|https://docushare.lsst.org/docushare/dsweb/Get/Version-46336/LDM-502.pdf], which was never issued,  contains descriptions of verification techniques, data and code for performance metrics. These should be migrated to the Jira based LVV project     "
Answer: 69893.0

User story: "Prepare a template in a shared presentation for all participants to add one slide about either themselves or their team"
Answer: 67832.0

User story: "To ensure that certain essential pieces of information are communicated by each science collaboration, we should prepare a template for presenters. "
Answer: 8772.0

User story: "To ensure that certain essential pieces of information are communicated by each proposer of a community broker, we should prepare a template for presenters. "
Answer: 36005.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: "Older HSC files can have incorrect DATA-TYP headers, causing some science frames to be ingested as calibrations and probably vice versa.  The OBJECT headers seem to provide values that could be used instead if we can completely enumerate the values used for calibrations; given the finite time duration of the problem.  [~<USER> also reports that the STARS database at NAOJ should be updated with correct values for these, so we could also query that to obtain more complete corrections for all potentially-incorrect files.    Priority for this ticket should be to get in a fix that enables the correct Gen3 Butler ingestion of all affected science frames in the RC2 dataset, which I can provide a complete list of later.  We can create a new ticket for a more thorough fix if the solution here is more localized.    [~<USER>, please steal this if you think you'll have time to work on it today.  If not I'll be bugging you about the best way to approach putting the corrections in astro_metadata_translator."
Answer: 4911.0

User story: "Lab testing of ComCam motivates a first pass at developing some long-overdue calibration product production code, as this will allow the ComCam commissioning team to efficiently assess performance as a function of temperature (among other things) as they acquire lab data over the (past and) coming weeks.    The ticket will cover making a first pass at writing a defect finding task to support this work.    Defect Task:   * Find bright & dark pixels from darks and flats   * Persist as ASCII text files so they can be treated as defects in the normal (old & bad) way   * Summary stats for each amp (and for each sensor)    Task should be able to run on either single master calibs (both darks and flats), or a list or raw input files, processing each as it should, and applying pixel-wise cuts to reduce the false-positive rate, _i.e._ making use of being fed multiple raw inputs."
Answer: 145603.0

User story: "I am preparing the visit to Paris' LSST team of Nick Mondrick from Harvard :    We will work on the Gemini measurement of Aerosols."
Answer: 15335.0

User story: "Update logging on the salpytools section of ATHS to be directed to a file in addition that to the screen."
Answer: 5431.0

User story: "In preparation for the tests in Chile, I'll finalize the ATAOS CSC by making it a configurable CSC and adding support for the lookup tables. "
Answer: 27041.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: "Create a script that sent commands such that the max speed of the dome will be tested. The initial step of the task was going over the context of the task. Initially edge cases that did not need to be covered were planned for. For example covering the case in which the azimuth produced a longer list than the elevation and also the case where the elevation produced the longer list.    I spoke with Tiago to discuss some python tools and get a better understanding of what is meant when something just needs to be cranked out. Moving forward I feel more comfortable overlooking certain processes that I am used to following during code design when necessary. "
Answer: 1418.0

User story: "make Release Policy ready to be submitted for approval"
Answer: 98156.0

User story: I propose that the {{ackcmd}} topic be enhanced to add a field for the "origin" datum of the command that triggered the ack and another field for "host" if "origin" is not unique. This will make it simple for the commanders to only pay attention to ackcmd messages meant for them.    The present situation is risky because there is no way to tell which commander an ackcmd topic is intended for. A recent change to the way private_seqNum was incremented makes this far more likely because the starting number is now the same for all commanders (for a given command).    Also I suggest adding field to commands that identifies the command (perhaps the integer position of the command in the list of commands, or a hash generated from the command name -- anything the commander wants as long as it is a 1:1 mapping between command name and identifier). The component being commanded will copy this field to the ackcmd topic.     This is less crucial than the first suggest change, but it seems simpler than relying on ranges of sequence numbers. If nothing else we can more easily debug problems since the person doing the debugging won't have to work out the range of sequence numbers that applies to a particular command.    I suggest that this ticket replace DM-19579 as a more thorough solution.
Answer: 171458.0

User story: "Since moving Jenkins to NCSA one of the ci_hsc tests fails because the clean up code attempts to clear out a directory but some files are still open and owned by the process. On local filesystems this works fine but on NFS deleted but open files become temporary files and {{rmtree}} gets upset when they hang around.  tempfile.TemporaryDirectory does not know about those open files and does not run rmtree with the flag to ignore errors.    The fix is either to move the clean up code to tearDown or else see if a {{del}} works."
Answer: 309.0

User story: "Currently, the internal table that holds the defects in {{Defects}} is not presized, so is not contiguous in memory.  This is to make sure the table is contiguous from construction time."
Answer: 409.0

User story: "Some of the DAYOBS keys in this range of data are off by one; please fix     "
Answer: 128.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 is possible to compare AOD determination from Spectrometry in     [https://arxiv.org/pdf/1806.02422.pdf] and [https://arxiv.org/pdf/1210.2619.pdf]    against my paper   "Local monitoring of atmospheric transparency from the NASA MERRA-2 global assimilation system"https://www.overleaf.com/read/yryfbzrdryhm   not submitted yet :(  And AOD from photometry [https://arxiv.org/pdf/1706.01542.pdf]    also against my paper . See attachment [^mai2019.pdf]
Answer: 16600.0

User story: "DM-19674 is fixed, but I didn't have time to get a test in before merging. I'd like to take the test case provided by [~<USER> and distill it into a unit test to lock the barn door. I'll also search for similar bugs."
Answer: 11000.0

User story: "Sometimes the near neighbor queries in the query monkey timeout, and we think this is because the entropy allows for too big of a range sometimes.  This means that NN queries might return too many results or take too long to run."
Answer: 1291.0

User story: "For a while now we have known that causing a kernel to cross the memory threshold in the JupyterLab environment presents as a hung cell.  I.e. the cell just sits there and the asterisk never goes away.  The only real way to tell what is going on is by opening a terminal and looking for the kernel process with e.g. {{top}}.    It turns out that running the notebook in the classic view produces a more useful error in this situation.  See this screen grab.     !image-2019-05-08-15-21-10-734.png|thumbnail!     We should look into whether notebooks running in JL can give a similarly useful error."
Answer: 305386.0

User story: The matplotlib plots rendered in notebooks served within JupyterLab do not have the standard interactive controls.  I believe this is a conscious decision, but users find the interactive controls useful enough that, in some cases, users are specifically using the classic ("tree") view of the notebooks in order to have this feature.    [~<USER> suggested that we look into whether the JL position is flexible on this.
Answer: 87832.0

User story: "Try to pinpoint the slowdown in SAL command acks that [~<USER>, [~<USER> and I are seeing. In particular:  - See if it is present OpenSplice 6.10  - If it still present there then try to come up with a simple case that shows the problem.  - If the problem is in dds file an ADLink support ticket. If not, try to figure out how SAL could be improved.    Note: I see the problem (or what I think is the problem) in dds salobj."
Answer: 109177.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: "For the QA dashboard project, we need to deliver a test dataset to work on.  This will be the output of DM-18300, processed with the {{matchVisits.py}} task.  This ticket involves:   # Running {{matchVisits.py}} on all tracts/filters for the {{/datasets/hsc/repo/rerun/RC/w_2019_14/DM-18300-jointcal/}} dataset.   # Delivering this dataset to Quansight in a way that they can use.    For 2., there are different ways we could do it, but I would lean towards having them use the stack, so they can butler-load the tables they need (easier reproducibility for us, and guarantees fewer surprises later).  One thing that I don't know is how to copy a data repo to an arbitrary location where the full root repos wouldn't necessarily be available."
Answer: 38575.0

User story: "Bucket for writing and working on my IVOA Paris talk!"
Answer: 18537.0

User story: "[~<USER> reported that the gen2 butler dayObs quantity is not being calculated correctly. It is always assumed to be calculated from the date and not from the DAYOBS header. This needs to be fixed to only use the date if DAYOBS is missing.    Additionally, since this is a gen2 ingest model parameter and not part of the gen3 data model, the value does not get corrected if there is a FITS header correction file. Update ingest so that header fixups occur on ingest even outside of metadata translation."
Answer: 1246.0

User story: "https://developer.lsst.io/coding/intro.html#stringency-levels currently refers to the TCT and the “lead developer”, neither of which are meaningful."
Answer: 28766.0

User story: "In order to implement DM-18739, we need a function that can tell if a particular dataset type is supposed to be standardized.  This is only necessary for image or exposure like types.  This will be a utility in obs_base."
Answer: 27.0

User story: "Per [discussion on Slack|https://lsstc.slack.com/archives/C2JPMCF5X/p1557330175343800?thread_ts=1555439400.008300&cid=C2JPMCF5X], {{ProcessCcdTask}} should set {{doWrite=False}} on it's {{IsrTask}} subtask.    And please also make sure there aren't unnecessary overrides in obs packages."
Answer: 218.0

User story: "This will include an initial meeting.  After that, there will be support in ingesting raw images and master calibration frames.  Finally, we will need to configure ISR and the image characterization task to work with the AuxTel focus data."
Answer: 594703.0

User story: "This domain has been replaced by eups.lsst.codes and can now be retired."
Answer: 38894.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: "Minimal test case from [~<USER>:  {code:java}  import lsst.afw.image as afwImage  import lsst.afw.geom as afwGeom    exposure = afwImage.ExposureF(1, 1)  wcs = afwGeom.makeSkyWcs(      crpix = afwGeom.Point2D(0.0, 0.0),      crval = afwGeom.SpherePoint(180.0, 0.0, afwGeom.degrees),      cdMatrix = [[1.0, 0.0], [0.0, 1.0]],      projection = 'TAN',  )  exposure.setWcs(wcs)  print(exposure.getWcs().getCdMatrix()) # [A]  afwImage.ExposureF('FRINGE-2015-07-23-HSC-Y-006.fits')  print(exposure.getWcs().getCdMatrix()) # [B]  # [A] succeeds but [B] fails.   {code}  The referenced file can be downloaded [here|https://hscdata.mtk.nao.ac.jp/hsc_bin_dist/temp/FRINGE-2015-07-23-HSC-Y-006.fits].    While it's highly likely there's something wrong with the offending fringe frame, this kind of behavior implies either bad global variables or bad memory access, in either our code or AST.     "
Answer: 421676.0

User story: "Due to an incompatibility between the stack and {{pytorch}}, it would be beneficial to switch the gradient calculation in scarlet from {{pytorch}} to {{autograd}}."
Answer: 135.0

User story: "We need to make a smaller-scale sky subtraction for the next Subaru release.  One option would be to use the configs from S16A     "
Answer: 49086.0

User story: [~<USER> is running into problems with {{Butler.makeRepo}} whereby the registry specified from his external config (which happens to be an in-memory sqlite) is being overwritten by a default value assuming a SQLite file on disk with butlerRoot.    I think it is reasonable to assume that if makeRepo is being called with a populated config and that that config has {{registry.root}} defined, that the caller of makeRepo does not want makeRepo to override the values. Should makeRepo attempt to create the tables in the provided root? What about {{datastore.root}}?    It's a fairly small change to allow setConfigRoot to not override root if root is already present in config (we have to call it anyhow because it copies items over as well as updating the root). I think a flag to setConfigRoot ("overrideRoot"?) defaulting to False would work which would be True when called from makeRepo and would be forwarded to overrideParameters or else not even pass toUpdate to overrideParameters.
Answer: 1643.0

User story: "During working on DM-17825, some missing docstrings marked as TODO in DM-17458 were updated."
Answer: 14411.0