udaykiran19491/user-stories-from-tawos-for-llm-fine-tuning huggingface dataset:
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "There is a logging system on Roundtable, but there isn't any user or deployment documentation yet. These are some things we can do now that will be useful:    - Document how to port-forward into the Kibana front-end  - Tips for using the Kibana front end and links to Kibana docs and tutorials.  - Minimal documentation for the logging deployment (following our standard pattern)"
Answer: 1891.0

User story: "The fake insertion script in https://jira.lsstcorp.org/browse/DM-23631 for Gen 2 was purposefully very rough.  This ticket is to develop a production-ready pipeline under Gen 3 with similar capabilities.  Further discussion of requirements should be undertaken with [~<USER> before beginning to ensure our design is future-proof."
Answer: 243620.0

User story: "Set up the repository for scale testing.  I'm going to try out the safir parts and see how that works!  It uses aiohttp which is something I want, and has a lot of good boilerplate in there."
Answer: 1366.0

User story: "* Create account for Felipe on lsst-git.ncsa.illinois.edu   * Allow access to lsst private hiera repo   * Review docker in puppet documentation with Felipe     "
Answer: 80480.0

User story: "A regularly occurring task; update SAL tests after an XML release, to pick up interface changes."
Answer: 18585.0

User story: "Related to DM-23907 but may include additional configuration to allow troubleshooting in the NCSA Test Stand."
Answer: 139435.0

User story: "Test deployment of headerservice in a docker container (as it would be deployed in production.)    Test machine is lsst-testvm30.ncsa.illinois.edu. It is already configured to run docker.    Add comments about any issues."
Answer: 130893.0

User story: "Continue update of software interface documentation, to make consistent with the new partition of development of control software by Rubin Observatory and EIE contractor, as we continue to settle on details. This is continuation of DM-23756"
Answer: 18420.0

User story: "Prepare and coordinate weekly meetings on dome control software with EIE contractor. This is continuation of DM-23754"
Answer: 18429.0

User story: "Test and create SAL 4.1.1 release candidate branch in github. Test with python 3.7.6 and bug fixed version of OpenSplice 6.9 , and XML 4.8"
Answer: 18887.0

User story: "Update the community editioh of OpenSplice  V6.9 with the pydds memory leak fix provided by ADlink. Build and distrubute RPM and update Nexus and github repos"
Answer: 18890.0

User story: "List out the summit services that need support and TMG should be watching for tickets 7*24.  "
Answer: 133021.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 February 2020 monthly report (/)   - Audit and update [https://confluence.lsstcorp.org/display/DM/DM+PMCS+Update+Requests] (/)"
Answer: 87.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "If a Script with index=0 is launched then it reads commands for every Script. This is a terrible thing, so modify BaseScript to reject index=0.    I will do the work on DM-23757, since it is a trivial change and fairly urgent."
Answer: 9846.0

User story: "In DM-23731 we're building LTD Events, a service that takes webhook payloads over HTTP and converts them into Kafka messages.    This ticket will add functionality to LTD Keeper to emit those webhook requests when events happen. So far we have a single event recognized by LTD Events ({{edition.updated}}), but we can plan to add a comprehensive suite of events in conjunction with the DM-23731 ticket."
Answer: 5471.0

User story: "Test the new MTMount CSC with the real camera cable wrap and/or the PXI simulator (preferably both) and fix any problems that show up."
Answer: 76057.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: "Improve scripts so LSST_SDK_INSTALL is autopopulated if not specified, removed nested if..fi blocks. Streamline script operations."
Answer: 32889.0

User story: "Integration testing"
Answer: 31812.0

User story: "Reprocessing HSC-RC2 with stack w_2020_11    Reference: w_2019_38    Tasks done (so far):   * makeSkyMap     * singleFrameDriver     * jointcal     * skyCorrection     * coaddDriver   * multiBandDriver   * forcedPhotCcd     * visitAnalysis     * compareVisitAnalysis     * coaddAnalysis     * colorAnalysis   * compareCoaddAnalysis     * matchVisits     * dispatch_verify_colorAnalysis     * matchedVisitMetrics     * dispatch_verify_matchedVisit     * validateDrp     * writeObjectTable     * transformObjectCatalog     * consolidateObjectTable"
Answer: 29381.0

User story: "Contribute use cases to the NSF FABRIC testbed proposal"
Answer: 40910.0

User story: "Learn how are command passed from ts_m1m3support C/C++ controller to FPGA, and replies passed back."
Answer: 16473.0

User story: "Resolve the PXI software issues at hand. In other words.    - Obtain the following software modules   NI-RIO IO Scan - MISSING, MIA from NI package manager  NI Common Instrument Design Libraries - MISSING  LabVIEW SoftMotion Module - MISSING  NI 1588-2008 Network Management - MISSING  NI-TimeSync Time Reference for IEEE 1588-2008 - MISSING    - In parallel to this, attempt to run the software alone and let labview complain. Petr suggested that this may give more clues on how to obtain the software packages. "
Answer: 16213.0

User story: "This is continuation of tests from DM-23604, for the next round of tests I want to try an approach outlined in that ticket:   * use finer partitioning, MQ3C level=10 could be optimal   * do not filter on pixelId in queries, all filtering is done on client side    This should reduce number of queries that we send to Cassandra and hopefully solve scaling issues that we saw."
Answer: 66458.0

User story: "Start work on the Helm chart for handling the two simplest flavors of CSCs."
Answer: 65728.0

User story: "Preparation work for alignment acceptance test. This included updating the alignment model with new methods, prepping a jupyter notebook, parsing and evaulating offsets received from T2SA, and beginning writing the correction loop logic for the ASC. Work is here: [https://github.com/lsst-ts/ts_MTAlignment/commit/81331b31dfe2d9b0922b6f7f15b6e7b783729e95]"
Answer: 3819.0

User story: "Add native OIDC support to jwt_authorizer and eliminate oauth2_proxy from the flow to simplify the authentication flow and the number of code bases we have to maintain. This will also allow us to remove the complicated handling of oauth2_proxy sessions in favor of simpler state management.    Ensure the new OIDC support handles CILogon and GitHub."
Answer: 60404.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 logMessage topic is defined in several places: generics, Script and LOVE, at least.    I recently updated the generic version but forgot to update the other versions.    Note: we can get rid of the copies once SAL 4.1 is released. It will require an update to SALSubsystems.xml to list which generic topics Script and LOVE use."
Answer: 110.0

User story: "Add a clearError command to NewMTMount that includes a field for a bitmask of which errors to clear.    Also fix moveToTarget command to eliminate the unwanted azimuth direction flag and clean up the axis state enums a bit."
Answer: 161.0

User story: "forcedPhotCcd.py with w_2020_08    with {{--config externalPhotoCalibName=fgcm}}"
Answer: 66245.0

User story: "pipe_analysis colorAnalysis.py     -I'm using-   * -pipe_analysis c11be5b-   * -qa_explorer 4a24f54-   * -obs_base 5b52ea6-   * -with w_2020_08 lsst_distrib stack-    -This is the same as the updated stack setup in DM-23831.-    Overwrote the rerun folders ({{DM-23243/ANALYSIS/DEEP}} and {{DM-23243/ANALYSIS/WIDE}}) to use this updated setup:   * lsst_distrib w_2020_15  * lsst_sims sims_w_2020_15  * qa_explorer 4a24f54 (master as of Apr 14)  * pipe_analysis 6269f0b (master as of Apr 14)"
Answer: 51654.0

User story: "So while testing my load thing, I found an interesting spawner / timer bug.  If I do a create, the first time, it fails, but then the second time it will succeed.  Even if I do it a few minutes apart from each other.  The other steps (logging into the hub, etc) are done automatically, so pretty fast.  So there may be a timing issue that was exposed."
Answer: 25750.0

User story: "Reflect the change of expiration period for internal JWTs to 30 days in the Argo CD configuration."
Answer: 155.0

User story: "The OODS doesn't have the timestamp output that the CSCs have.   "
Answer: 20253.0

User story: "One or two mixed-units fields in the Hexapod XML still don't have proper units descriptions, including application.error. Fix that and look for similar issues."
Answer: 634.0

User story: "The Kafka producer Helm chart deployments need to expanded to all of the CSCs running at the summit and at NCSA."
Answer: 57582.0

User story: "We need to use these helm charts"
Answer: 8538.0

User story: "writeObjectTable , transformObjectCatalog, consolidateObjectTable with w_2020_08"
Answer: 27326.0

User story: "Recent versions of astropy download a leap second table on demand, the first time one requests TAI time. This introduces an unexpected delay in the first call to the current_tai() function. That broke a unit test in ts_sal (DM-23826) and seems a bit risky overall. The function should return quickly.    In order to eliminate that delay and catch issues with downloading that table early, call {{current_tai()}} once while loading salobj.    Note that the current_tai function is fundamental to ts_salobj: no topics can be read or written without it. So it's reasonable to fail to load it if that function cannot be used."
Answer: 17048.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: "Put the rotator PXI into the standby state after clearing the error. This task will need to update the Simulink model for the state machine transition. This task also needs to write the related test in Simulink to testify this change. After this, I will need to generate the C/C++ code and put back to ts_rotator_controller and test the new built. I need to think I can test this in C/C++ level in additional to the Simulink level or not."
Answer: 41884.0

User story: "It'd be nice to have some way users can run something to report the node they're on."
Answer: 10028.0

User story: "The current implementation of the mock controller doesn't exactly follow the proposed communications protocol. Fix please."
Answer: 160.0

User story: "Now that SALOBJ has been added to the project, it is time to implement the azimuth motion control commands."
Answer: 11692.0

User story: "We need to plan for SAL 4.2 (and add a note to [https://confluence.lsstcorp.org/display/LSSTCOM/SAL+and+ts_xml+Release+Plans)]     "
Answer: 1.0

User story: "We've finished our Puppet configuration of lsst login nodes and we are ready for final vetting and opening of ssh from the internet. Note that we do still have some feature adds to do in future tickets, but general availability to use them as bastions is complete.    Security vetting ticket for reference: [LSST-2980|https://jira.ncsa.illinois.edu/browse/LSST-2980]   [~clausen] Would you prefer these be revetted before pfsense changes are made?    The hosts are:   lsst-login01: 141.142.181.16   lsst-login02: 141.142.181.17   lsst-login03: 141.142.181.18"
Answer: 20164.0

User story: "I tried to build pipelines.lsst.io following the instructions at https://developer.lsst.io/stack/building-pipelines-lsst-io-with-documenteer-job.html, specifying {{d_latest}} as the EUPS tag. That fails:  {code}  Ignoring unsupported tags in VRO: d_latest  setup: Unsupported tag(s): d_latest  + eval false  ++ false  script returned exit code 1  {code}    (https://ci.lsst.codes/blue/organizations/jenkins/sqre%2Finfra%2Fdocumenteer/detail/documenteer/806/pipeline/)    When I gave it the tag {{d_2020_03_10}}, it passed (https://ci.lsst.codes/blue/organizations/jenkins/sqre%2Finfra%2Fdocumenteer/detail/documenteer/807/pipeline/).    Please either make {{d_latest}} work as expected, or change the documentation to avoid giving the impression that it'll work."
Answer: 3463.0

User story: "Update environment and dependencies for the stack, and include conda compilers.    Revives DM-20864"
Answer: 85201.0

User story: "Work to enable running the AP pipeline within a Condor environment in the NCSA Test Stand     "
Answer: 138373.0

User story: "I wasn't clear if I could do this at the same time as adding it to lsst_distrib; simplest answer is a separate ticket."
Answer: 125062.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: "{{matchVisits.py}}, in the past, has been able to pull visitAnalysis parquet tables for all possibly relevant visits.  Now, apparently, there are not FGCM calibrations available for some (presumably barely-overlapping) visits.  {{matchVisits.py}} needs to handle this gracefully so it can continue despite some missing tables. "
Answer: 836.0

User story: "Implement RFC-658."
Answer: 317.0

User story: {{coaddAnalysis.py}} gave the following error for some data:   {noformat}  Traceback (most recent call last):    File "/home/<USER>PDR2/pa_stack/pipe_analysis/bin/coaddAnalysis.py", line 3, in <module>      CoaddAnalysisTask.parseAndRun()    File "/software/lsstsw/stack_20200220/stack/miniconda3-4.7.12-984c9f7/Linux64/pipe_base/19.0.0-9-g0ae078d+2/python/lsst/pipe/base/cmdLineTask.py", line 610, in parseAndRun      resultList = taskRunner.run(parsedCmd)    File "/software/lsstsw/stack_20200220/stack/miniconda3-4.7.12-984c9f7/Linux64/pipe_base/19.0.0-9-g0ae078d+2/python/lsst/pipe/base/cmdLineTask.py", line 221, in run      resultList = list(mapFunc(self, targetList))    File "/software/lsstsw/stack_20200220/stack/miniconda3-4.7.12-984c9f7/Linux64/pipe_base/19.0.0-9-g0ae078d+2/python/lsst/pipe/base/cmdLineTask.py", line 385, in __call__      result = self.runTask(task, dataRef, kwargs)    File "/software/lsstsw/stack_20200220/stack/miniconda3-4.7.12-984c9f7/Linux64/pipe_base/19.0.0-9-g0ae078d+2/python/lsst/pipe/base/cmdLineTask.py", line 447, in runTask      return task.runDataRef(dataRef, **kwargs)    File "/home/<USER>PDR2/pa_stack/pipe_analysis/python/lsst/pipe/analysis/coaddAnalysis.py", line 356, in runDataRef      repoInfo.dataId, forcedStr="unforced " + self.catLabel, **plotKwargs)    File "/home/<USER>PDR2/pa_stack/pipe_analysis/python/lsst/pipe/analysis/coaddAnalysis.py", line 881, in plotPsfFluxSnHists      "Flux>{:.1f}".format(highFlux), "psf_used"])    File "/home/<USER>PDR2/pa_stack/pipe_analysis/python/lsst/pipe/analysis/analysis.py", line 605, in plotHistogram      axes2.set_ylim(0, 1.05)  UnboundLocalError: local variable 'axes2' referenced before assignment  {noformat}    I was using w_2020_08 + pipe_analysis {{09a7675}} 
Answer: 253128.0

User story: "The decam convert tests in DM-22655 rely on a gen2 repo that does not exist in our CI system. To make those tests able to be run as part of CI, we need to shrink the calibration data that lives in ap_verify_ci_hits2015, and make a gen2 repo with it. If the data is small enough, that data could even live in obs_decam.    [~<USER>'s suggestion is to not zero all the data, but to set each data array to the HDU number, so that we can still test that gen3 and gen2 read the same pixel data."
Answer: 6107.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> reports that the test of getCurrentTime is failing on two different systems. Adam helped me get credentials on a system that showed the problem and it turns out that it is due to a recent change to astropy: astropy now downloads a leap second table at need, and this was occurring in the middle of the test, making measured time differences much larger than expected.    I looked at both the 4.0 and 4.1 branches of ts_sal and concluded that only the 4.0 branch needs a fix, which is to get astropy time once before running the time-critical portion of the test.    The test is radically different in SAL 4.1 (it uses the new getLeapSeconds function) and is immune to this problem."
Answer: 149.0

User story: "This ticket includes all work to create a presentation on deblending for the algorithms workshop. Many slides will be recycled from previous talks comparing scarlet to the deblender but additional introductory material on the current deblender, noise replacement, and measurements has to be written, with accompanying figures."
Answer: 49995.0

User story: "New version of header service needs a container to run on the summit asap.    "
Answer: 86.0

User story: "The Subsystem.xml file is woefully out of date and/or just wrong.  Hoping to fix it a bit."
Answer: 6141.0

User story: "Forwarder config file has `NAME: f99` that is used as the name of the forwarder and that should come from the system hostname or ip address."
Answer: 90067.0

User story: "We discussed the following   - How to access the rot/hex server   - How the VNC's are configured   - How the GUI is being automatically being brought up using Systemctl   - The CSC to PXI communication   - Turning on the Hexapod   - Enabling SAL control   - Shutting down the Hexapod"
Answer: 1231.0

User story: "The efd deployment currently expects storage that looks local on the machine the pod is running on. The efd export should be natively mounted on the k8sdev kub nodes so that the pods have access to their global storage without the need for a persistent volume or persistent volume claim.    This is a puppet change that will effectively do:   $ mount lsst-nfs.ncsa.illinois.edu:/dac/services/efd /efd"
Answer: 10586.0

User story: "Update the M2 xml based on the M2 test result at Mar., 2020. The ICD is LTS-162. After the [M2 test|https://confluence.lsstcorp.org/display/LTS/M2+Testing+on+Summit+at+March+2nd+-+6th%2C+2020], we realized that we may need to update the xml to fulfill the condition now and extend the original xml for the need."
Answer: 22788.0

User story: "Add log name to the logMessage topic. I originally thought that since logMessage is associated with a particular CSC the information was redundant, but I am wrong because components of the CSC may use child logs with component-specific names and presently that information is lost.    Update ts_salobj to set this field -- probably conditionally on it existing, so that salobj is compatible with older XML."
Answer: 4576.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "I initially implemented a fix in the DM-22605 to unblock Bo and let him make more rapid progress.  In retrospect that was a mistake.  The fix appears to be more generally useful and seems to actually fix a bug in the amp assignment that breaks amp assembly.    The work has been completed on that ticket, but needs to be pulled out of that ticket onto a separate branch to merge to master.  Review of that code will happen on this issue."
Answer: 8756.0

User story: "We do not currently write any weather station values to the header. LSE-400 lists:    AIRTEMP  PRESSURE  HUMIDITY  WINDSPD  WINDDIR  SEEING - DIMM seeing value  Please add them in their own section of the header.    Updated information values in     https://confluence.lsstcorp.org/display/SYSENG/Auxiliary+Telescope+Header+Information+Topic+Mapping"
Answer: 4083.0

User story: "Change the type of the azimuthEncoderPosition field of the position telemetry topic for ATDome from {{unsigned long}} to {{long long}}. The current field is too short."
Answer: 5802.0

User story: "Use w_2020_08 stack with qa_explorer at commit ab69304 and pipe_analysis at commit 09a7675. (same as DM-23579)     The command line will look like this, with all tract/filter IDs pairs, with either DEEP or WIDE accordingly   {noformat}  coaddAnalysis.py /datasets/hsc/repo/ --calib /datasets/hsc/calib/20200115/ --rerun DM-23243/MULTIBAND/DEEP:DM-23243/ANALYSIS/DEEP --doraise --config doWriteParquetTables=True --id tract=08766 filter=NB0921  {noformat}  "
Answer: 54887.0

User story: "Looks like the landing page on summit isn't deploying, after looking I think it's the chart."
Answer: 15917.0

User story: "DM-23169 added a notebook comparing CModel and MultiProFit photometry to DC2 truth catalogs; this ticket will do the same for ngmix fits."
Answer: 110967.0

User story: "Write a review of the authentication and authorization design constraints for the Rubin Science Platform and propose a design."
Answer: 90662.0

User story: "Document use of Docker Hub credentials and its integration with GitHub. Bring up to date with the neophile work. Add Kubernetes security concerns. Raise the priority of Google authentication and two-factor authentication in general."
Answer: 239362.0

User story: "ts_salobj warns if the DDS queue starts to fill up, but the warning is too crude. At present it warns if it reads >= 10 messages and never again, until it resets the warning when it reads only 1 message.    What we want to know is something on the order of:  - reached 10%  - reached 50%  - reached 90%  - reached 100% (error: data likely lost)    Also the warning should be reset in some fine-grained fashion, e.g. if we reach 10% then report that we have improved, and warn at 50% again.    Use the {{QueueLengthChecker}} for this (it is already used for messages about the Python queue).    Also there are two warnings about queues: one for the DDS queue and one for the Python queue. Improve the text for each so it is completely clear which warning applies to which cache."
Answer: 4595.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 "Contributing" entry in index.rst is wrong for ts_ATDomeTrajectory and possibly others of my packages as well. T&S Jira tickets should be specified by label, not component (unlike DM).
Answer: 96552.0

User story: "Review the rotator PXI code to have some understanding of it. This task will try to compile the code by the autotool as well."
Answer: 29043.0

User story: "{{scons install}} will not install {{bin}} unless it already exists, but it usually doesn't already exist because it's built as part of the {{shebang}} target."
Answer: 396.0

User story: "Add an opinionated manager for schemas for producers that follow the RecordNameStrategy. The functionality of this manager is:    * Load schemas embedded in the package  * Preregister these schemas  * Add suffixes to schema names to dynamically create staging subjects  * Assist in serialization (i.e. serialize X data given schema named Y)."
Answer: 34667.0

User story: "Create a kafkit.ssl module that contains utilities to create an SSL context for Strimzi-secured brokers."
Answer: 24510.0

User story: "Update the package of https://github.com/lsst-sqre/kafkit to match the patterns developed for https://github.com/lsst-sqre/safir. This brings improvements to testing and code styling."
Answer: 18871.0

User story: "This ticket explores two simple empirical approaches towards fixing the known amp-to-amp offset issue in HSC CCDs. Multiple attempts to provide a meaningful hardware-related solution to the amp-offset issue have been explored, with work ongoing in this regard. In the meantime, we provide these simple per-CCD fixes as a proof of concept. Should more desirable corrections not be forthcoming, this work serves as a potential future fix which can be applied to future datasets.    Techniques explored are per-amp background subtraction and amp-edge pattern continuity corrections. Both methods have their merits, however, per-amp background subtractions remain vulnerable to stray light (ghosts, ghouls, etc) or strong flux gradients. Conversely, amp-edge pattern continuity corrections perform well across multiple scenarios, with most remaining weaknesses solveable in the short-term. Therefore, if subsequently required, we recommend amp-edge pattern continuity corrections for future use.    Attachments below contain both example notebooks, a brief PDF presentation, and all postage stamps used within the PDF.  Full processing outputs can be found at: https://github.com/leeskelvin/amp2amp"
Answer: 46522.0

User story: "Deploy nublado at the summit"
Answer: 5958.0

User story: "Learning how M1M3 cell shall operate, difernces from know LBT design. Connect & run simulator."
Answer: 34513.0

User story: "Create script for building rpms for forwarder. "
Answer: 4449.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 all convolutions in scarlet are done in k-space. In general this is faster than doing them in real space, especially for large blends, but back propagating the derivative in autograd is an expensive procedure. There is also a possibility that numerical artifacts exist in back propagation though the FFTs, since this is effectively a deconvolution, but this is not yet clear. We expect to save cpu cycles by implementing convolutions in real space as well as potential numerical stability.    There are two other side benefits to using real space convolutions:    1. We can potentially avoid using autograd, which has an overhead in terms of memory used and extra processing.    2. If we decide to run scarlet on an entire patch in the future then we'll be forced to implement a spatially varying PSF, which is possible with real space convolutions but not using a single PSF in k-space."
Answer: 96708.0

User story: "Implement Infante-Sainz model of extended PSF as a Task.    Collaborate with visitor Raul Infante-Sainz.         Main processing steps:   * Determine bright stars to use from Gaia catalog   * Extract afw exposures around each   * Estimate flux within a certain pixel radius   * Stack stars together    Bypass first step by using existing bright star masks at first.    As is the case in the reference for SDSS, we will likely need to a(n at least) 2-step approach, with a first subtraction (DM-23786) of the extended psf profile obtained from this Task, a rerunning of detection (still on individual calexps) to further remove objects within the bright star wings, then re-applying this task with the new detection masks.         Ref: Infante-Sainz, R., Trujillo, I. and Román, J., 2020. The Sloan Digital Sky Survey extended point spread functions. _Monthly Notices of the Royal Astronomical Society_, _491_(4), pp.5317-5329."
Answer: 135171.0

User story: "Use the crowded field simulations generated in DM-20958 to run difference imaging using DCR and CompareWarp templates. Analyze the results for a variety of ranges in seeing, and compare the number of false detections from using the two different algorithms."
Answer: 86386.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 ticket covers work performed on the known HSC amp-to-amp offset in Q1 2020. Initial reporting ticket is DM-20303. Prior exploratory work is covered in DM-22804, and completed exploratory conclusions are shown in DM-23794. Code implementation in the stack is ongoing (at time of writing) in DM-24389.    This ticket covers further exploratory work analysing the amp-to-amp offset issue in HSC data, attempting to determine its origin, constructing analysis plots, and testing various fixes.     Many of the plots in this ticket are produced in the attached deltaoverscan.ipynb jupyter notebook. A summary of what has been found:   * tested for variability in amp-to-amp offset as a function of observed band via delta overscan plots - all bands appear to exhibit similar/identical offsets (i.e., issue is not band specific).  * tested for incorrect gain being applied per amp (performed reruns with flatfielding turned off to generate signal-variance plots, essentially a PTC) - gain appears to be being applied correctly.   * potential for gain differential across an amp. gaincheck plots below are color-coded according to distance from readout corner. The magnitude of this effect is not large enough to explain the amp offset issues we see here and (to first order) would be cancelled by the flat field.  * amp offset level appears consistent at ~1 ADU - this manifests as a relatively larger effect (i.e., more noticeable) for shorter exposures.  * it appears that prescriptive approaches towards fixing this issue may not be forthcoming (although work is ongoing looking at non-linearity effects). Empirical per-amp or per-CCD approaches may be more practical in the short term.     It was decided to pursue two empirical per-amp/per-CCD based approaches towards fixing this issue: per-amp background subtraction (i.e., piston corrections) and per-CCD amp-edge pattern continuity corrections. Although much of this work was exploratory, all results relevant to that work have been moved to DM-23794.    All source material has been stored on GitHub at: https://github.com/leeskelvin/amp2amp"
Answer: 87323.0

User story: "The {{LSSTClusterClient}} doesn't work with the version of {{dask.distributed}} that ships with the most recent weekly.  Specifically the way timeouts work has changed in {{dask.distributed}}, so the exponential back off loop in {{LSSTClusterClient}} does not work as expected.    Anecdotally, the problem with {{dask.distributed}} that we were working around with that backoff loop seems to not be a problem anymore, so we can probably take that out.    It may now be that {{LSSTClusterClient}} can be slimmed down to be just a subclass of {{Client}} that overrides the {{__repr__}}.    The {{ClusterProxy}} seems to have bit rotted.  The link to the scheduler status page works, but the links to the status page for the individual workers end up in 500s."
Answer: 19849.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> pointed out during the review of DM-22655 that we have gen2 repos to test obs_lsst gen2-3 conversion. We will also need to specify some configs specific to this package. Implementing `test_convert2to3.py` would be an easy start, once the right test data is identified.    [~<USER>: In your comment you said "This repo even comes with a bunch of gen2 repos...": where are they, and what to they contain? We do have `testdata_lsst`, but that's not in lsst_distrib (how big is it? The readme isn't helpful.) and it doesn't contain premade gen2 repos.
Answer: 25589.0

User story: "Allow authnz to be configured to use GitHub as an authentication provider so that we can put it in front of the notebooks in nublado without using CILogon."
Answer: 68074.0

User story: "Deploy a version of authnz in nublado using CILogon (but don't put it in front of the notebooks) so that we can test outside of stable and int."
Answer: 27364.0

User story: "Fix outstanding issues with TunableLaser CSC and perform upgrade to TunableLaser CSC"
Answer: 59670.0

User story: "Currently the TunableLaser CSC's detailed states duplicate the summary states and only include a propagating detailed state. The duplicated summary states should be removed and a nonpropagating state should be added."
Answer: 28863.0

User story: "Add a CscCommander class to salobj, much like the one in ts_hexrotcomm. This should allow making trivial scripts to exercise a CSC. It should handle simple commands automatically and allow overrides for more complex commands."
Answer: 2311.0

User story: "I made a profile to allow groups/users to ssh to nodes from the new lsst-login nodes. These profiles should have their data configured with the proper users and groups."
Answer: 9462.0

User story: "Information values in:  https://confluence.lsstcorp.org/display/SYSENG/Auxiliary+Telescope+Header+Information+Topic+Mapping      {noformat}  DOMEAZ         ATDome ATDome.position.azimuthPosition                      SHUTLOWR ATDome ATDome.position.dropoutDoorOpeningPercentage   SHUTUPPR ATDome ATDome.position.mainDoorOpeningPercentage  SEEING         DIMM   DIMM.logevent_dimmMeasurement   {noformat}      "
Answer: 1337.0

User story: "The StarFast simulation tool needs to be brought up to date with changes to the LSST stack from the last six months. The changes are minor, and links to the pull requests will be in a separate comment."
Answer: 10.0

User story: "Clarify requirements on user access to the alerts database and the intention requirement OSS-REQ-0185: Transient Alert Query  "
Answer: 2784.0

User story: "Take the parquet files at {{/datasets/hsc/repo/rerun/RC/w_2020_07/DM-23564_obj/deepCoadd-results/merged/*/*parq}} as inputs and ingest into Qserv.     This gives me a chance to update my understanding and improve the manual process in DM-22483.     As DM-15656 has merged in {{lsst-dm/parquet_tools}},  use the parquet_tools {{pq2csv}} this time. "
Answer: 23218.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 LSSTCam, check that the bad chip book-keeping in `ptc.py` is being done correctly and set the entire amp as bad in the defects file. "
Answer: 83451.0

User story: "ts_idl is now required by make_idl_file in ts_sal. Update the ups table accordingly."
Answer: 3249.0

User story: "I have tested out the process for building the extension and it seems to work using {{jupyter-lab}} version 1.2.6 on my laptop.    I followed the instructions [here|https://github.com/mgckind/jjs9] with the exception that I also needed to install {{pandas}}."
Answer: 132821.0

User story: "Update software interface documentation to make consistent with the new partition of development of control software by Rubin Observatory and EIE contractor. This is continuation of DM-23562"
Answer: 12952.0

User story: "When sending commands through the pyserial library to start storing values into the electrometer's buffer, the electrometer becomes non-responsive. However, sending the same commands through a system serial connection works as intended and the electrometer remains responsive. I have spent time looking through the manual to see if I could find any answers as well as experimenting with sending commands in a different way. By the end of the sprint, I have still not determined the problem."
Answer: 21.0

User story: "Prepare and coordinate weekly meetings on dome control software with EIE contractor. This is continuation of DM-23563"
Answer: 12951.0

User story: "Train Andrew the use of hexapod."
Answer: 7229.0

User story: "Assist with any debug and preparation work required to get the M1M3 control  system to the state where it is ready to install the SAL 4 compatible software  and execute tests"
Answer: 13.0

User story: "Create feature branches and then release for the new SAL4 compatible   versions of the M1M3MT and MTVMS packages as tested in Chile"
Answer: 37709.0

User story: "Update the VMS software for SAL 4 and OpenSplice 6.9 compatabilty.  Install on summit cRIO and PC and test (no real telemetry yet though)  basic function and logging of telemetry to summit EFD"
Answer: 26.0

User story: "Update the M1M3 software on the summit computers and support  testing campaign (update test scripts accordingly)"
Answer: 13036.0

User story: "When DM-20956 was closed, the test exemption should have been removed."
Answer: 9751.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 Roundtable service that indexes web-based content and reduces that content into records for Algolia. Initially, it should expect to index documents based on SQuaRE Events triggers either directly from LSST the Docs (see DM-23731) or from sqrbot-jr.    It's possible that this service could eventually incorporate an HTTP API and DB to allow it to become a metadata service for LSST's search service.    The code design should anticipate being able to route the triggers into queues that can be processed by a cluster of workers so that the public-facing service itself doesn't get backlogged by the task of downloading content and indexing it.    Based on some initial brainstorming we're going to call this service Ook after the Discworld librarian."
Answer: 38697.0

User story: So that the new search service can respond to events such as an edition on LSST the Docs being updated, or a new product being created, we want to integrate LSST the Docs with Roundtable's SQuaRE Events. Events, which is Kafka-based, is the main system for event-driven service coordination in Roundtable. The excepted outcomes are:    Given that LTD Keeper is Flask based, I think it makes sense to have the integration with SQuaRE Events as a separate microservice. This allows LTD Keeper to focus on maintaining the DB and service its REST API. Thus LTD Events will a microservice that integrates both SQuaRE Events and LTD Keeper.    # Create an "ltd-indexer service based on the roundtable_aiohttp_bot template.  # Receive posts from ltd-keeper (i.e. a webhook) indicating that an edition is updated (via an internal in-cluster endpoint)  # Add this webhook functionality to LTD Keeper  # Send a Kafka message on SQuaRE events indicating an edition is updated.
Answer: 40070.0

User story: "In DM-22655 there was a hack left in place where cpBias and friends were listed in daf_butler as storage classes and also listed the formatters. This is not correct. Instead we need to generalize the raw->formatter mapping in obs packages to allow ingest to support arbitrary instrument specific dataset types."
Answer: 19093.0

User story: "In order to help get DM-22655 merged sooner, I'm going to move the work of converting ci_hsc to use the new script onto this ticket, instead of doing it there. I'd already started on that process, and will move that work onto this ticket."
Answer: 43647.0

User story: "Acceptance review for T2SA software"
Answer: 38759.0

User story: "SPIE paper number: 11450-16: Documentation automation for the verification and validation of LSST software'"
Answer: 102820.0

User story: "Implementation of headers into the ComCam Forwarder code"
Answer: 23034.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 debugging DM-22655 we realized again that the dataset type definitions for input datasets in pipeline task connectors are not validated against dataset type definitions already understood by the registry. This led to a strange bug where cpBias had a ExposureF when the file was ingested but the isrTask definition said it was an ImageF.  This led to the pipeline creating a DatasetType object that was at odds with the registry definition and caused an error on get.    At the very least we should warn if there is an inconsistency between the two when the pipeline runs."
Answer: 18856.0

User story: "Propose LDM-639  acceptance tests that can be run as part of the  LDM-503-11 operations rehearsal"
Answer: 164969.0

User story: "Write the portion of the MTMount CSC that controls the camera cable wrap.    I will probably do this work before finishing the PXI simulator DM-23118 because we should have an existing hardware simulator to talk to, as well as the real hardware, and I consider it higher priority."
Answer: 12908.0

User story: -In DM-23717 we were reminded that filters can have spaces in them and these end up in file names.-    Dots in the file part of templates cause confusion when extension manipulation occurs in the {{Location}} class. To be safe replace dots in the file name with underscores. Do not change dots in directory parts of path though.    This fix is essentially the same fix as was done in DM-23503 for "/".
Answer: 4263.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: [Build #31303|https://ci.lsst.codes/blue/organizations/jenkins/stack-os-matrix/detail/stack-os-matrix/31303/pipeline] failed on node mojave-1 in obs_decam {{test_ingest.py}}. Four test cases failed; example error is:    {code}  from lsst.afw.image import makeExposure, makeMaskedImage  > full = makeExposure(makeMaskedImage(self.readImage()))  ../../stack/DarwinX86/obs_base/19.0.0-21-gaaa92db+7/python/lsst/obs/base/fitsRawFormatterBase.py:338:  _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _  self = lsst.obs.decam.rawFormatter.DarkEnergyCameraRawFormatter(FileDescriptor(Location('file:///Users/square/j/ws/stack-os-m...mage.TransmissionCurve'), 'metadata': StorageClassPropertyList('PropertyList', pytype='lsst.daf.base.PropertyList')})))  def readImage(self):  index, metadata = self._determineHDU(self.dataId['detector'])  > return lsst.afw.image.ImageI(self.fileDescriptor.location.path, index)  E lsst.pex.exceptions.wrappers.FitsError:  E File "src/fits.cc", line 1402, in void lsst::afw::fits::Fits::readImageImpl(int, T *, long *, long *, long *) [T = int]  E cfitsio error (/Users/square/j/ws/stack-os-matrix/6ab9d5fd5e/lsstsw/build/obs_decam/tests/tmpbmqgsnz8/raw/raw/r/r DECam SDSS c0002 6415.0 1480.0/415282/raw_r_r DECam SDSS c0002 6415.0 1480.fits): non-CFITSIO program error (1) : Reading image  E cfitsio error stack:  E decompression error: hit end of compressed byte stream  E {0}  E lsst::afw::fits::FitsError: 'cfitsio error (/Users/square/j/ws/stack-os-matrix/6ab9d5fd5e/lsstsw/build/obs_decam/tests/tmpbmqgsnz8/raw/raw/r/r DECam SDSS c0002 6415.0 1480.0/415282/raw_r_r DECam SDSS c0002 6415.0 1480.fits): non-CFITSIO program error (1) : Reading image  E cfitsio error stack:  E decompression error: hit end of compressed byte stream  E '  {code}    
Answer: 1659.0

User story: "Create a client server system to allow dax_data_generator to generate synthesized data on several workers concurrently while keeping track of what has been created."
Answer: 244955.0

User story: "To continue with the CSC build process, we need to start with the deploy-env image.  This needs a Jenkins build to ensure consistency."
Answer: 18757.0

User story: "This ticket is to make a branch for new updates to notebooks. Specifically the creation of notebooks for AuxTel verification tasks."
Answer: 327046.0

User story: "We have been discussing on Slack how to allow gen3 configs to be combined from multiple sources.  One option is for the EUPS table file to add a search directory to DAF_BUTLER_CONFIG_PATH.  This works fine but can be unpredictable since the contents of the configuration can depend on precisely which packages have been set up.    On this ticket we will extend {{includeConfigs}} support to allow an environment variable to be specified in addition to a full path or relative path."
Answer: 374.0

User story: "- Get PXI software installed onto Labview Realtime target in my office    - If time permits other tools as well which have been sent by Russell "
Answer: 18964.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 order to do our visualization bake-off, I'll need access to a cluster local JS9 server.  I'm still unclear whether it would be better to have a singleton, or to spawn a server in everyone's namespaces, but I guess we'll go with the former first.    Eric Mandel has supplied an image that can be used to spin up a server using docker.    {{docker run -dit -p 8080:80 -p 2718:2718 ericmandel/js9server}}"
Answer: 135312.0

User story: "memory guarantee is not being substituted in template"
Answer: 33045.0

User story: "We have a cookie affinity setting that appears to be superfluous.  Until we have an HA Hub it doesn't seem to do us any good."
Answer: 38.0

User story: "Basically, some of the testing documentation is out of date (bad links, old data) and is missing some recent developments, like the CI/CD process.    Attached in an email from Andy with his thoughts.  I will break out the points in that email into bulleted items in this ticket or make new tickets, depending on required effort."
Answer: 20159.0

User story: "The configuration format for {{FgcmFitCycleTask}} has some elements that must be specified in band order.  While this was fine (such as it was) with 5 bands (g,r,i,z,y), with the addition of several narrow-bands this has become more obviously unwieldy.  It would be easy to change these configs to use dictionary mappings instead of ordered lists which would remove ambiguity and make mis-configurations much less likely."
Answer: 11901.0

User story: "In DM-23394, [~<USER> reports that there are a number of PDR2 visits that did not produce {{photoCalib}} outputs from {{fgcmcal}}.  This will happen when a visit is deemed to be unsolvable (but this should be logged clearly).  However, there are a number of deep-field N387 visits in the deep fields that were deemed to be unsolvable but from cursory inspection should have been usable."
Answer: 5877.0

User story: "Task has been re-prioritized with getting a server EUI installed. It currently is running and operating in my office.     Russell is able to teamviewer into it.    The NSV simulator has been verified and communicated properly with it. "
Answer: 13019.0

User story: "Support the M2 force test on the summit. This test will use the M2 GUI and script to test the force and steps in open/ closed loop control. The output data will be in the binary file and EFD."
Answer: 7381.0

User story: "What are dense patches of sources that crop up in out catalogues?    We take a re-run of tract 9615 and look at the r-band deepCoadd forced src catalogue. Images below are r-band when monochrome, and gri when RGB. We will use these data to determine dense regions in the catalogue, performing an n-th nearest neighbour match. Having identified suitably clumped regions, we will take a closer look to see what's going on."
Answer: 18171.0