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: "This task is to capture time spent figuring out how we're going to handle alarm codes from the chiller. In the time that DM-22339 was on hold, the ability to leave the error code parameter blank on BaseCsc.fault() was deprecated. Spent a lot of time working on how to pass through hex values sent by the chiller itself in a way that will be useful/readable for someone writing rules for the Watcher, eventually after consulting with Tiago, we decided to go back to my original plan, which is to just have a single error code for all chiller alarm(s), and then include the detailed description of the alarms (as well as the raw hex from the chiller) in the report string. This is simplest since chiller has so many possible alarms, and multiple can be present at once. "
Answer: 2481.0

User story: "Write the low-level communications code for the MTMount CSC:  - command and reply classes  - tests for same  - a commander that will send a few commands (star with the camera cable wrap commands) and report all replies  - a trivial mock responder, so I can exercise the commander"
Answer: 17000.0

User story: "Spring 2020"
Answer: 146638.0

User story: "Perform rolling reboot on verify-worker nodes and perform validation of maintenance task as/after the complete. Since this is the first time we are attempting this procedure for LSST (and with Slurm in general) I am going to keep a bit of a closer eye on the nodes than I might otherwise."
Answer: 5554.0

User story: "ADLink claims to have fixed the memory leak discussed in DM-23255. Test their fix and make sure neither the reader nor writer are leaking."
Answer: 24218.0

User story: "Identify changes to xml that will be needed to correspond to API changes    (API changes should be freezing after this)    Consistency in formats across all topics that contain spatial coordinates"
Answer: 2643.0

User story: "In test_ptc.py of cp_pipe there are multiple calls to fitPtcAndNonLinearity. Check the return value of that function with any one (or all) of those. "
Answer: 43555.0

User story: "Travel to Chile and update and test the M1M3 Controller code and Monitor process to   use SAL 4 and DDS 6.9"
Answer: 4216.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: On macOS high sierra builds daf_butler is falling over in S3 tests with the following error:    {code}  >       return fileDescriptor.storageClass.pytype(fileDescriptor.location.path, **parameters)  E       lsst.pex.exceptions.wrappers.FitsError:   E         File "src/fits.cc", line 1561, in lsst::afw::fits::Fits::Fits(const std::string &, const std::string &, int)  E           cfitsio error: tried to move past end of file (107) : Opening file '/var/folders/d4/hc0hbfss6_d5vtlcchxpdx5h0000gn/T/tmpg5x4hnge.fits' with mode 'r'  E       cfitsio error stack:  E         ffopen could not interpret primary array header of file:   E         /var/folders/d4/hc0hbfss6_d5vtlcchxpdx5h0000gn/T/tmpg5x4hnge.fits  E        {0}  E       lsst::afw::fits::FitsError: 'cfitsio error: tried to move past end of file (107) : Opening file '/var/folders/d4/hc0hbfss6_d5vtlcchxpdx5h0000gn/T/tmpg5x4hnge.fits' with mode 'r'  E       cfitsio error stack:  E         ffopen could not interpret primary array header of file:   E         /var/folders/d4/hc0hbfss6_d5vtlcchxpdx5h0000gn/T/tmpg5x4hnge.fits  {code}    We are seeing these now because the new conda env includes moto/boto3.    The relevant code in s3Datastore.py is:    {code:python}  with tempfile.NamedTemporaryFile(suffix=formatter.extension) as tmpFile:      tmpFile.file.write(serializedDataset)      formatter._fileDescriptor.location = Location(*os.path.split(tmpFile.name))      result = formatter.read(component=getInfo.component)  {code}    The problem is that between the write and the read the file is not closed. Closing the file would delete the temporary file so the minimalist fix is to add a {{flush()}} between the write and the read.    It seems like linux and macOS mojave have different buffering allowing the same process to read from something that is still open for write without flushing.
Answer: 45.0

User story: "To clear up the Argo CD OutOfSync status for nubaldo-users, set an Argo CD annotation to make Argo CD not try to prune users or let them contribute to the status of the overall application."
Answer: 5848.0

User story: "The refactoring of ATArchiver code in support of CCArchiver required a shift in where get_config_pkg was implemented.  This was fixed for CCArchiver, but not for ATArchiver.  This ticket will add that."
Answer: 7045.0

User story: "* Make plots similar to those used for evaluating variable PSFs, comparing number of false detections.  * Also compare how variable PSFs interact with crowded fields.  "
Answer: 95454.0

User story: "Add SALObj dependency to the project and implement a skeleton dcs CSC."
Answer: 10252.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 {{ConfigurableCsc}} to output the {{settingsApplied}} event. The logical place to do this is in {{begin_start}}, which calls {{configure}}. Also update {{BaseCsc}} to output the {{softwareVersions}} event    See https://confluence.lsstcorp.org/pages/viewpage.action?pageId=120786640 for details.  I believe the format of the {{settingsApplied}} field should be {{config_file}}:{{version}}, though that is a bit unclear from the Description field of the XML. The current default version is available as {{self.evt_settingVersions.data.settingsVersion}}.    Note that CSCs which want to set the {{otherSettingsEvents}} field should do that in the constructor, by setting {{self.evt_settingsApplied.data.otherSettingsEvent}}. Document that in "How to write a CSC".    Finally try to figure out how to output {{settingsVersions}} and {{settingsApplied}} in {{BaseCsc}}. These will be nearly empty. The trick is doing this in a way that does not interfere with {{ConfigurableCsc}}.
Answer: 68017.0

User story: "Going up the summit to change the password of the Cisco switch of the CCW cabinet.     While on the summit I also helped with IP changes of the hexapod. Ultimately Heinreich was able to get the IP change working.     I installed Labview on windows and began getting the proper licenses to be able to view the device on NI Max. However because Heinreich resolved this issue I no longer continued working on this. "
Answer: 59.0

User story: "Get all of our GCP Kubernetes clusters onto the latest regular channel versions for both the control plane and the nodes.    To-do:  - api-lsst-codes  - <USER>agena  - efd  - gitlfs-prod  - influxdb-demo  - nublado-lsst-codes  - quijibo-lsst-codes  - scipipe-publish-jhobitt-curly  - scipipe-publish-prod  - squash  - squash-demo    Already done:  - roundtable"
Answer: 8449.0

User story: "I'm doing artificial star tests on some HSC data to measure completeness, and find that I need to adjust {{insertFakes.py}} a little."
Answer: 8628.0

User story: "The current version of the OODS requires a message to trigger ingestion;  the work for this ticket will do a small bit of refactoring to support messages from ComCam."
Answer: 8373.0

User story: "templatekit's explicit click <= 7 pin conflicts with cookiecutter 1.7's click dependencies. Let's unpin the click depenency in templatekit (verifying that it works)."
Answer: 144.0

User story: "DM-23169 began analysis of fits of DC2 data plotting measurements vs truth for matched sources only. This ticket adds code and a notebook for plots of completeness and purity, quantifying the performance of detection (and deblending and measurement, to some extent)."
Answer: 10355.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, upgrading authnz in the int and stable environments is dangerous because it takes both the Argo CD UI and gRPC interface off-line. (I believe this is true of the gRPC interface, although I haven't verified this; it's definitely true of the UI.)    Find a mechanism to maintain UI access when authnz is down without introducing too much of a security problem. Ideally this would have some stronger security gate than just the Argo CD admin password, although that may be good enough for now if NCSA VPN is required."
Answer: 109707.0

User story: "Action from [DMLTVF2F|https://confluence.lsstcorp.org/display/DM/DM+Leadership+Team+Virtual+Face-to-Face+Meeting%2C+2020-02-25+to+27] - [~<USER> should write a technote describing his understanding of schema management."
Answer: 283866.0

User story: "Create Helm charts for a subset of the Kafka producers and a single CSC that can facilitate exercising the producers. Create an ArgoCD deployment for those charts. Deploy the charts to the GKE sandbox and show that data flows into the EFD."
Answer: 39233.0

User story: "This ticket is to create a script to run scarlet (not meas_extensions_scarlet) on the extracted blends that contain fake sources from the dataset generated during the fall deblending sprint and generate a photometric catalog similar to the ones output from the stack.    This ticket was opened for two reasons:  * There are about 3000 blends containing fake sources that generated last fall out of ~23k total blends (since most blends did not contain fakes). So we're wasting a lot of time to run the full patches on the server, including measurement algorithms that we don't need because for now we're testing the scarlet measurements.  * It has been difficult to get time on {{lsst-dev}} with the algorithms workshop coming up so it is faster to check changes/improvements on only the blends of interest (that contain a truth value).  * There is a lot of overhead in taking the scarlet outputs and putting them in a form that the LSST stack can recognize that can sometimes contain a bug. Checking scarlet on the same blends inside and outside of the stack is a good way to make sure that things are consistent."
Answer: 282175.0

User story: "Checkout [https://github.com/lsst-dm/s20-hsc-pdr2-reprocessing/tree/master/07_multiband]     The environment is at  the file {{07_env.sh}}; i.e. use {{w_2020_08}}    The 729 pipe_drivers commands are in the file {{07_multiband_wide.sh}}   You can change the number of nodes/procs-per-nodes/time ({{\-\-nodes}} ,  {{\-\-procs}}   ,{{\-\-time}}) as appropriate, or the job names (but leave {{x7w*}} in the string)     There are 729 jobs in total. Similar to DM-23301 and DM-23395, we will want the slurm job IDs of the successful jobs.     Copy the good job logs to {{/datasets/hsc/repo/rerun/DM-23243/logs/multiband/wide}} "
Answer: 56267.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: "matchedVisitMetrics.py using w_2020_08   per tract*filter      Each command looks like this:  (for either WIDE or DEEP)   {code:java}  matchedVisitMetrics.py  /datasets/hsc/repo/rerun/DM-23243/JOINTCAL/WIDE     --output /datasets/hsc/repo/rerun/DM-23243/validateDrp/matchedVisitMetrics/WIDE/[tractID]/[filterName]      --doraise --config instrumentName='HSC' datasetName='HSC-PDR2'     doApplyExternalPhotoCalib=True doApplyExternalSkyWcs=True externalPhotoCalibName=fgcm      --id ccd=0..8^10..103 tract=[tractID] visit=[visits]  {code}  "
Answer: 40229.0

User story: "So for the int vault secrets operator stuff, when we switched over to using the one in the lsp-deploy repo, it didn't have a namespace.  As the vault-secrets-operator is something we want to be able to install by itself, it should make its own namespace, but can't really do that in the way normal apps do.  This is because we want to be able to install this first."
Answer: 7241.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 noticed when reviewing recent ap_pipe logs that there are some deprecation warnings we should probably deal with.  {code}  /software/lsstsw/stack_20200220/stack/miniconda3-4.7.12-984c9f7/Linux64/obs_decam/19.0.0-6-gb5bb71e+12/config/isr.py:95: FutureWarning: Config field ccdProcessor.isr.doAddDistortionModel is deprecated: Camera geometry is incorporated when reading the raw files. This option no longer is used, and will be removed after v19.  /software/lsstsw/stack_20200220/stack/miniconda3-4.7.12-984c9f7/Linux64/ap_association/19.0.0-13-g744ec97+3/python/lsst/ap/association/mapApData.py:185: YAMLLoadWarning: calling yaml.load_all() without Loader=... is deprecated, as the default Loader is unsafe. Please read https://msg.pyyaml.org/load for full details.  /software/lsstsw/stack_20200220/stack/miniconda3-4.7.12-984c9f7/Linux64/pex_config/19.0.0-5-g9aa49c1+1/python/lsst/pex/config/configurableField.py:150: FutureWarning: Config field ccdProcessor.isr.doAddDistortionModel is deprecated: Camera geometry is incorporated when reading the raw files. This option no longer is used, and will be removed after v19.  /software/lsstsw/stack_20200220/stack/miniconda3-4.7.12-984c9f7/Linux64/ip_diffim/19.0.0-7-g2f7a0e4+3/python/lsst/ip/diffim/imagePsfMatch.py:785: FutureWarning: Call to deprecated method getImageF(). (Zero-argument overload is deprecated; use one that takes an ``interpStyle`` instead. To be removed after 20.0.0.)  /software/lsstsw/stack_20200220/stack/miniconda3-4.7.12-984c9f7/Linux64/ip_diffim/19.0.0-7-g2f7a0e4+3/python/lsst/ip/diffim/imageDecorrelation.py:421: FutureWarning: Call to deprecated method setCtrX. (Use `setCtr` instead. To be removed after 20.0.0.)  /software/lsstsw/stack_20200220/stack/miniconda3-4.7.12-984c9f7/Linux64/ip_diffim/19.0.0-7-g2f7a0e4+3/python/lsst/ip/diffim/imageDecorrelation.py:422: FutureWarning: Call to deprecated method setCtrY. (Use `setCtr` instead. To be removed after 20.0.0.)  /software/lsstsw/stack_20200220/stack/miniconda3-4.7.12-984c9f7/Linux64/pipe_tasks/19.0.0-28-g53bcf5f6+2/python/lsst/pipe/tasks/imageDifference.py:759: FutureWarning: Call to deprecated method makeSourceCatalog. (Replaced by SourceDetectionTask.run(). Will be removed after v20.) {code}"
Answer: 78974.0

User story: "Add the text agreed in RFC-670 to the developer guide, to allow for post-review commits when squashing them is impractical and when the commits meet our existing quality standards."
Answer: 27302.0

User story: "AuxTel job management code no longer scales to ComCam and this ticket addresses that issue."
Answer: 17282.0

User story: "Make it easier to debug LSP tickets and tokens. This probably looks like:  * A Jupyter notebook that analyzes the token information found in the notebook  * A new jwt_authorizer endpoint that takes a ticket or token and returns as much information about it as possible in some reasonable format (probably JSON)  * Server and client libraries underlying that code"
Answer: 31979.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 authentication and authorization framework for the LSP is currently deployed manually with Helm in int and soon will be in stable. Switch to using Argo CD to manage the application in all environments."
Answer: 52223.0

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

User story: "Ever since we turned the macOS nodes back on in Jenkins the nightly build has been failing:  {code}  >   from .base import *  E   ImportError: dlopen(/Users/square/j/ws/scipipe/lsst_distrib/osx-10.13.clang-1000.10.44.4.py3/lsstsw/build/astshim/python/astshim/base.so, 2): Library not loaded: libastshim.dylib  E     Referenced from: /Users/square/j/ws/scipipe/lsst_distrib/osx-10.13.clang-1000.10.44.4.py3/lsstsw/build/astshim/python/astshim/base.so  E     Reason: image not found  {code}    This looks like a SIP issue so it pointed us to a repeat of DM-21999 (the long shebang). I think that DM-23098 using a longer conda environment name may have pushed us slightly over the 127 character shebang limit (by 1 or 2 characters)."
Answer: 1796.0

User story: "Can sky object statistics be used to help quantify how much flux is being over-/under-subtracted around bright sources?    Here we use sky objects generated on DEEP data to explore the sky level ('local sky') as a function of regional source flux. A sky object is a pseudo-object artifically injected into the coadd processing run prior to the measurement step. They are defined to have a radius of 8 pixels, and are placed such that no pixel within this radius overlaps with any other detection footprint. Pointings are tested as to whether or not they meet this criteria, stopping when it reaches 100 successful pointings per patch or 500 attempts, whichever comes first.    In the first half of this notebook, we create a re-run of DM-21386 for tract 9813, patch 2,2 in the r-band on the command line. The second half of this notebook expands our analyses to the entire tract.    All outputs (including processing notebooks) can be found [on GitHub|https://github.com/lsst-dm/drp-analysis-sprint-feb20/tree/master/local_sky_oversub]."
Answer: 1117.0

User story: "Use w_2020_08    The pipe_drivers commands are in 07_multiband_dud.sh  in https://github.com/lsst-dm/s20-hsc-pdr2-reprocessing/tree/master/07_multiband"
Answer: 24436.0

User story: "In the DM-21335 work, I need the `ParquetTable` object to have a `.filename` attribute, so I added that in the qa_explorer version.  This ticket is to add that to ParquetTable in pipe_tasks."
Answer: 131003.0

User story: "Add unit tests to config packages to test the config files.    Add a base class for such tests to ts_salobj and a unit test to exercise it."
Answer: 2741.0

User story: "Create a simple script to insert fakes for AP using the HiTS2015 dataset. Likely this will be on an un-merged ticket of ap_verify.    This script will be fairly hacky as it will copy data around in the ap_verify_hists2015 dataset and edit the DecamMapper on the fly."
Answer: 33184.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: fgcmcal fails on master with the latest conda environment on Ubuntu 18.04.4. The failure is in one of the new tests comparing the `photoCalib.getCalibrationErr()` with the `fgcmZptGrayErr`:    {code}  tests/test_fgcmcal_hsc.py:154:   _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _   tests/fgcmcalTestBase.py:407: in _testFgcmOutputProducts      (np.log(10.0)/2.5)*testCal.getCalibrationMean()*fgcmZptGrayErr)  ../../stack/Linux64/utils/19.0.0-7-g686a884+2/python/lsst/utils/tests.py:656: in assertFloatsAlmostEqual      testCase.assertFalse(failed, msg="\n".join(errMsg))  E   AssertionError: True is not false : 1/1 elements differ with rtol=2.220446049250313e-16, atol=2.220446049250313e-16  E   0.00223844323512219 != 0.0022384434 (diff=2.3283064e-10/0.0022384434=1.0401453e-07)  {code}    We are not seeing this on other machines (CentOS, macOS), so there's probably a "fun" interaction with system libraries going on here. Adding {{rtol=2e-7, atol=None}} to the above test prevents the error, but may not be the actual solution we want. This suggests to me that there's a float32 calculation going on under the hood somewhere.    I can provide an Ubuntu account to test on.
Answer: 105.0

User story: "We know that we're not yet able to do everything we want. New features include, but are not limited to:   * Direct image scaling and subtraction   * Leveraging information in both m=+1 and m=-1 orders (for coarse grating)   * Using the wcs, or a fit to the wcs (when possible) to get an exact centroid for the main star    We probably also want to improve some of the priors once we know how things are working, which will improve fit robustness, and perhaps also allow finer sampling of some of the pre-computed grids which are fit against.    Likely will need to be split once we know more about this work."
Answer: 345540.0

User story: "Run some of the new LATISS data through in bulk. Don't look at results in detail, just sufficient to identify failure modes, and start fixing those. Will include adding new filter and grating definitions to Spectractor. Will likely need input from Jérémy but not necessarily. That will become clear as the ticket progresses."
Answer: 345541.0

User story: "Dual purpose: test out the crosstalk measurement code and ensure it works well for this kind of data, and add a crosstalk matrix so that the AuxTel can use it.    If it doesn't work well for some reason, either fix it, or work out what kind of input data would make it happy, and if that's on-sky, add it to the observing plan for the next run.    Also, compare to nominal ITL values as provided by camera team, and see which works better for correction."
Answer: 61901.0

User story: "Implement code that propagates IOD orbits and calculates residuals from observations in a heliolinc cluster."
Answer: 70439.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 seems like no matter what I do, I end up running my workflows in containers with a CPU limit of 4 and a mem limit of 6GB.  This corresponds to a medium size container.  Even if I ask for a small or large container, I get the same limits.  This is a problem because some of the notebooks I want to test require around 10GB of memory."
Answer: 5635.0

User story: "To more fully test DM-22655, we should run as much of the gen3 pipeline as we can on a converted ap_verify test dataset. As a first test, lets run on ap_verify_ci_hits, instead of the much larger non-ci dataset.    I'll provide the command to run in a comment. You'll need to get three packages on branch {{tickets/DM-22655}} and scons'd: daf_butler, obs_base, and obs_decam. -If you setup ap_verify_ci_hits2015 before sconsing obs_decam, it will run a few extra tests.-"
Answer: 44633.0

User story: "Add documentation in the repository with more clear descriptions what the repo stores and its role in maintaining the LSST Science Data Model (SDM)   "
Answer: 110609.0

User story: "Two things that I'm going to address in the same ticket.    1) Make it easier to see the contents of the noninteractive command once you've spawned a workflow.    2) Ensure setting ACCESS_TOKEN env var appropriately on spawned workflows."
Answer: 1285.0

User story: "Upgrades are not expected to cause issues, but I want to run through a test on Puppet on my test cluster."
Answer: 13.0

User story: Changes needed in slurm.conf on verify-worker nodes + lsst-dev[01-03],lsst-test7 (any Slurm submit/scheduler nodes).   * set the program Slurm will run when the node is idle and you call 'scontrol reboot'; this will only really be relevant on verify-worker nodes, so it's OK that the; script won't exist on lsst-dev*,lsst-test7   RebootProgram="/root/update_os/update_os.sh"     * set this so that the node has time (way more than enough) to come back before being marked offline   ResumeTimeout=3600    Updating this via Puppet will likely restart slurmd/slurmctld so there should be no need to run 'scontrol reconfig'.
Answer: 1525.0

User story: "Servers that are managed by pup-npcf or lsst-pup-ncsa."
Answer: 13139.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 none of the pipeline tasks being developed ever need to work with specific components at the registry level.  This leads us to think that registry does not need to know about components and does not need to list every single component of each dataset in the registry.    We therefore want to go back to the original design (and early implementation) where registry only knows about the single dataset and datastore knows about components. Datastore configuration controls whether assembly/disassembly should happen for a given dataset (and different datastores could do their own thing).  This will mean that when disassembly does not occur, significant savings in row count in the registry will be made.    To support composite datasets where a wcs can come from one place and pixel data from another, we need to implement the concept of a virtual dataset (with a new API) where registry can tell datastore that a new dataset exists that is a combination of components from different datasets already known to datastore.    Not seen as a blocker for Gen2, but will lead to some additional registry instability (which may require us to support both registry concepts together)."
Answer: 207646.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: Before DFTs were integrated into scarlet, the earliest version of the code calculated the difference kernel needed to do partial convolutions from the narrow model PSF into the wider observed PSFs in each band using scarlet itself.     The basic algorithm is as follows:  * In scarlet we typically define a model PSF {{M}} that is a nyquist sampled gaussian with {{sigma=1/sqrt(2)}}. Fitting sources in the model to the observed images in each band requires convolving the PSF in each band ({{P_b}} with a difference kernel, the kernel needed to match the PSF in the model seeing to the PSF in the observed seeing. So the difference kernel {{D}} is given by {{P=M*D}}.  * The current version of scarlet uses the same technique as the one described in the galsim paper ([Rowe 2014|https://arxiv.org/abs/1407.7676] to calculate the difference kernel in k-space, however the first version of scarlet made this calculation in real space.  * In real space we defined the observed image as the observed PSF and the "difference kernel" used to convolve the model was the model PSF. This works because convolution commutes, so {{P=M*D=D*M}}. In other words, if we define our _model_ to be the difference kernel and convolve it with the model PSF, we can fit the result to the observed PSF and use the same algorithm used in scarlet to fit the model to find the best fit observed PSF without ever going into k-space.  * This worked quite well but was not as fast as matching the kernel in k-space, since the real space calculation required an iterative solution with the k-space version took only one pass. However, the problem with the k-space solution is that performing deconvolution, going from a wider PSF to a narrower PSF is ill-defined in k-space and leads to divergences in the difference kernel, making it numerically unstable.  * Earlier work in DM-20127 attempted to see if we could live with the numerical artifacts produced by the k-space deconvolution but the results were dependent on how different the model PSF and observed PSF were, with limitations on the upper-bound of the observed PSF before numerical artifacts dominated and the initialization was made worse.  * This ticket is to explore using the same real space PSF matching used in the previous version of scarlet, using the improved optimization algorithms of scarlet 1.0, to calculate the deconvolution kernel (the kernel to go from model PSF to observed PSF) to see if it can produce a more numerically stable result. 
Answer: 73975.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Run coaddDriver for HSC-PDR2 WIDE    Environments set as in:   https://github.com/lsst-dm/s20-hsc-pdr2-reprocessing/blob/master/06_coadd/06_env.sh    Note that this uses w_2020_07 from the old shared stack at {{/software/lsstsw/stack_20191101/}} , not the default shared stack.       pipe_drivers commands as in:   https://github.com/lsst-dm/s20-hsc-pdr2-reprocessing/blob/master/06_coadd/06_coadd_wide.sh    There are 3411 jobs in total.  Similar to DM-23301 and DM-23395, we will want the slurm job IDs of the successful jobs.  Also, please copy the good job logs to /datasets/hsc/repo/rerun/DM-23243/logs/coadd/wide  There should be 3411 * 2 = 6822  log files.   "
Answer: 18576.0

User story: "We need to understand what is happening on server side in Cassandra when it serves APDB queries. Cassandra provides wide range of monitoring metrics (http://cassandra.apache.org/doc/latest/operating/metrics.html) and they are accessible with standard Java JMX tools and Cassandra-specific tools ({{nodetool}} command uses JMX to query/control Cassandra nodes).    Some research is needed to understand if there is any existing tool that we can use to gather statistics that we need, or whether we need to implement something Java-based ourselves."
Answer: 33056.0

User story: "Run coaddDriver for HSC-PDR2 DEEP+UDEEP     "
Answer: 9658.0

User story: "Performance and verification of March 2020 PM"
Answer: 76149.0

User story: "pup-nts is deployed and running but puppet agent from testvm30 cannot find pup-nts on the network."
Answer: 65878.0

User story: "pup-nts is deployed and running but puppet agent from testvm30 cannot find pup-nts on the network."
Answer: 5286.0

User story: "Connection to RabbitMQ server fails sometimes because credentials fail, server not found or all kinds of problems. Yet, RabbitConnection class does not throw exception and instead, waits until things turn around. This should have a timeout of 5 seconds to try and fail the application."
Answer: 310741.0

User story: "There has been a request that instead of using the system date as the directory to write files to, that instead it should be written to a date that is UTC - 12 hours.   This would effectively cause all the files to be written to the same directory for an entire observing night.  This only affects where the Forwarder writes the file, and where the DBB and OODS initially receive the file."
Answer: 1218.0

User story: Investigate the backgrounds that are currently being subtracted from deepCoadd images in the stack. The question prompting this study was "What do the subtracted backgrounds look like in _gri_?"         In addition to the current default background scale of 128x128, try other scales (64, 256, and 512-pixel) to see how the resulting backgrounds look.
Answer: 7418.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: "LTD Conveyor has a {{--travis}} mode to automatically pick up the current Git ref from the Travis environment. For GitHub Actions we'd like a similar mode that uses the {{GITHUB_REF}} environment variable ([Default environment variables|https://help.github.com/en/actions/configuring-and-managing-workflows/using-environment-variables#default-environment-variables]). Note that this variable includes the full ref, including a {{refs/heads/}} prefix. We'd want to remove that prefix."
Answer: 7582.0

User story: "Refactor the Checkerboard service to use the Safir framework and standard Python package configuration. Use this as an opportunity to learn Safir and the templates and to provide feedback and possibly merge some code into Safir."
Answer: 19918.0

User story: "Tonight the LATISS filters were changed. A corresponding change has to be made to lsst.obs.lsst.filters.  The updated list can be found at https://confluence.lsstcorp.org/display/LTS/AuxTel+Filters"
Answer: 2130.0

User story: "Create test fake sources for injection into the CI-HiTS2015 dataset. Use the [~<USER> created tasks to insert said fakes into both the calexp and coadd. Reconfigure ImageDifference/ap_pipe to run over these fake inserted data. Make first check for results to see that the fakes are indeed processed. More detailed results tested on a later ticket."
Answer: 8635.0

User story: With both jointcal & fgcm photoCalib existing, compareVisitAnalysis can do a comparison of the {{photoCalib}}s.     Use this config:  {noformat}  externalPhotoCalibName1="fgcm" externalPhotoCalibName2="jointcal"  {noformat}    This is in the lowest priority of the PDR2 run right now. 
Answer: 141168.0

User story: "visitAnalysis with fgcm photometric calibration  "
Answer: 63311.0

User story: "This should be as simple as doing {{pip install lsst-efd-client}}.  See https://efd-client.lsst.io for more detailed installation instructions, if necessary."
Answer: 7.0

User story: "There is currently no way with gen3 to ingest a directory of files without writing a small program each time.  We need the equivalent of the gen2 ingestImages.py task.    This could go into obs_base although we have to understand how it's configured, and how it would differ for DECam data where there are multiple datasets in a single file.    There are open questions concerning how we tell the command what type of instrument is being ingested and whether there should always be a separate command to prepare a butler repository for that instrument."
Answer: 199302.0

User story: "{{kafka-connect-manager}} is the project that manages the different connectors used in the EFD https://kafka-connect-manager.lsst.io/    By adding the Replicator connector to {{kafka-connect-manager}} we can script the connector configuration and upload it to the Kafka Connect REST API, as we did for the InfluxDB connector.    https://docs.confluent.io/current/connect/kafka-connect-replicator/index.html "
Answer: 20176.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: "Planning for CY2020Q1 PM  This ticket had been created automatically Primavera ID: None"
Answer: 13224.0

User story: "I was getting     {noformat}  WARN: Parquet files will not be written (qa_explorer is not setup).  {noformat}    despite that qa_explorer was set up.      utils.py has this line  {code:java}  from lsst.qa.explorer.parquetTable import ParquetTable  {code}  that was missed to be updated when ParquetTable was moved to pipe_tasks"
Answer: 75.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 January 2020 monthly report (/)   - Audit and update [https://confluence.lsstcorp.org/display/DM/DM+PMCS+Update+Requests] (/)"
Answer: 39219.0

User story: "Change the lsstdoc.cls to:   # Use the Rubin green (#058b8c) rather than the LSST blue (four different blues!)   # Use Rubin Observatory rather than Large Synoptic Survey Telescope in all text.    I assume I will leave the LSST logo in place for now and the background picture of the telescope wire frame seems fine."
Answer: 111972.0

User story: "Puppetfile currently includes the test module andylytical/tuned.    Best practice dictates all custom modules should be pulled from the LSST-IT organization.    Work:   * Fork into LSST-IT   * Update Puppetfile   * Submit and merge PR"
Answer: 3052.0

User story: "Please provide a method on the butler object that can return the names of butler dataset types available to that butler.  This is essentially delegation to the underlying mapper class, but he method should merge dataset types for all mappers accessible by the butler."
Answer: 13245.0

User story: "Reprocess HSC RC2 dataset with  stack w_2020_07    Tasks ran with w_2020_07:  * makeSkyMap.sh  * singleFrameDriver.sh  * jointcal.sh  * skyCorrection.sh  * coaddDriver.sh  * multiBandDriver.sh  * forcedPhotCcd.sh  * visitAnalysis.sh  * compareVisitAnalysis.sh  * coaddAnalysis.sh  * colorAnalysis.sh  * compareCoaddAnalysis.sh  * matchVisits.sh  * dispatch_verify_colorAnalysis.sh  * matchedVisitMetrics.sh  * dispatch_verify_matchedVisit.sh  * validateDrp.sh    Three tasks were ran with w_2020_08:  * writeObjectTable,   * transformObjectCatalog,    * consolidateObjectTable "
Answer: 41588.0

User story: "Prepare and coordinate weekly meetings on dome control software with EIE contractor"
Answer: 18983.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."
Answer: 18982.0

User story: "Ultipro self assessment review"
Answer: 12977.0

User story: "This task is to support the summit on the CCW related activites. All I know of currently is that I am needed to move the CCW."
Answer: 8873.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "We currently get an error when trying to read parquet files from {{gcs}}.  The error is {{RuntimeError: module 'dask.bytes.core' has no attribute '_filesystems'}}}.    I have tested upgrading {{gcsfs}} from v0.2.0 to 0.6.0 and it seems to work."
Answer: 1047.0

User story: "RFC-660 deprecated LDM-472. Release a deprecated version to docushare."
Answer: 2641.0

User story: RFC-660 requires that LDM-472 be deprecated. Add an "obsolete" flag to the lsstdoc latex class to add deprecation warnings on each page.  This allows us to declare a document to be obsolete whilst also leaving the text available.
Answer: 2587.0

User story: "Create confluence page detailing how to build and deploy dm_forwarder."
Answer: 131195.0

User story: "{{/project/shared/auxTel-20200207}} was created, but not made the default repo (or, rather, it wasn't moved into place of the old one) so ingest of new images isn't working.    I suspect that the routine ingestion is now falling over somewhere, because it will be trying to ingest the new images using a new stack, but with a registry schema that is out of date, because it's still pointing at {{/project/shared/auxTel}}.    Either way, new images coming off the camera can't be used with a current stack on lsst-dev."
Answer: 35.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 a diagram of Vault to make it clearer how it's configured, and add that diagram to DMTN-112. Use the Python diagrams package as an interesting experiment."
Answer: 188.0

User story: "We're currently running 0.8.1. The current version is 0.13.1. We should upgrade, in part because it may eliminate the need to deploy cert-manager-crd separately and thus get rid of one instance of perpetual out of sync from Argo CD.    This version changes the namespace, so all cert-manager resources and annotations will need to be updated as part of this upgrade."
Answer: 4388.0

User story: "When Roundtable goes to Kubernetes 1.16, we'll need to remove all uses of the old, deprecated APIs. apps/v1beta1, apps/v1beta2, and some uses of extensions/v1beta1 are no longer supported.    https://www.ibm.com/cloud/blog/announcements/kubernetes-version-1-16-removes-deprecated-apis has some commands that will show you all the outdated resources.    https://kubernetes.io/blog/2019/07/18/api-deprecations-in-1-16/ has more information including upcoming deprecations that we should handle at the same time."
Answer: 123822.0

User story: When SFM is run, we produce and persist a "calibrated" exposure ({{calexp}}) upon which we perform measurements to compute the {{src}} catalogs. Subsequently, an "external" calibration can be run (i.e. {{jointcal}}/{{fgcmcal}}) to compute a more refined set of photometric and astrometric calibrations. Finally, a global sky correction can be performed and applied. The latter two steps are not reflected in the persisted visit-level {{src}} catalogs, yet these are the catalogs on which many "visit-level" metrics are computed and tracked. Indeed, the external photo/astrom calibrations can be applied at the catalog level, so their effects can be measured and tracked. However, there is currently no check on the photometry post global sky-correction and just pre-warping into what actually gets included in a coadd. It would be good to know if/what differences there are at these different stages, particularly in assessing the chaining of the measurement and application of these calibrations. In particular, the global sky correction is measured independently of any external photometric calibration and applied subsequently. Does this have any (negative) effects on the effective calibration of the image going onto the warp & coaddition stage?    Current plan is to make use of the new functionality added on DM-23352 which allows for forced CCD photometry to apply any combination of the above mentioned calibrations (as config options).  Forced catalogs will be created for the different permutations and combinations and the the resulting source catalogs will be compared.    Note to self: If any "issues" are uncovered, it may be worth a subsequent ticket to look into adding the ability to perform the global sky subtraction ({{pipe_drivers}}' *skyCorrection.py*) on images that have had the external photometric calibration applied.
Answer: 31876.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: "monitor01 needs an NFS mount so that we can copy logs to Systems group historical storage. E.g.:   [root@lsst-monitor01 ~]# mount -t nfs4   condo-nfs.ncsa.illinois.edu:/ on /condo type nfs4 (rw,relatime,vers=4.1,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=141.142.181.3,local_lock=none,addr=141.142.151.5)   condo-nfs.ncsa.illinois.edu:/ici on /condo/ici type nfs4 (rw,relatime,vers=4.1,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=141.142.181.3,local_lock=none,addr=141.142.151.5)    This should be Puppetized (at a minimum, we should add profile::nfsmount to the role so that, if rebuilt, the machine gets the required RPMs)."
Answer: 80755.0

User story: "NPCF:   lsst-adm01   lsst-repos01   lsst-git01   lsst-pup-npcf    NCSA 3003:   lsst-adm-ncsa   lsst-pup-ncsa"
Answer: 11731.0

User story: "Servers that are managed by pup-npcf or lsst-pup-ncsa."
Answer: 11732.0

User story: "Servers that are managed by pup-npcf or lsst-pup-ncsa."
Answer: 11734.0

User story: "We need some kind of decent UI for end-users of workflows.  If plausible, just use the Argo workflow UI, but since it doesn't know about namespaces or auth...."
Answer: 15991.0

User story: "Plot all 5 Rowe statistics involving correlation functions of PSF shape and/or size residuals."
Answer: 202959.0

User story: "Review the M2 requirement document and draft the test plan."
Answer: 3443.0

User story: "Write a script using the remote to the command Camera Hexapod in simulation mode to emulate hardware test that failed and grab data to write to a csv file."
Answer: 15827.0

User story: "After having created the mock controller framework, the commanding details need to be implemented which this story is for."
Answer: 33244.0

User story: "For the communications between the upper level DCS and lower level a mock lower level controller will be created based on the ts_ATDome code."
Answer: 16174.0

User story: "For the commanding from the upper level DCS to the lower level components a proposal needs to be made for both the communications and the command protocols. The basis for the commands will be XML files that will be used by both the Rubin Observastory and EIE. This story is for collecting the necessary commands and creating an XML file to share between both parties."
Answer: 2991.0

User story: "nginx-ingress services on Roundtable never report a green health check. After some research, this appears to be a known issue with Argo CD and some ingress controllers that we can fix."
Answer: 3769.0

User story: "ComCam forwarder would like to take advantage of the multi-threading support from cfitsio. For that to happen, cfitsio has to be compiled with `REENTRANT`. Current version of cfitsio is compiled without multithread support."
Answer: 30283.0

User story: "Add cat to lsst_distrib so it gets weekly version tags"
Answer: 210189.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "We are seeing consistent timeouts of the image pulls on nublado running at the LDF.  The timeout is 15 minutes.  That is quite a bit longer than we expect from performance we've seen from GKE.    Characterize how long things are taking and how long we think they should take."
Answer: 5615.0

User story: "In cat yml/hsc.yaml   we need to change all those {{fits:tunit: nmgy}} to nanojanskys"
Answer: 283143.0

User story: During RC2 and PDR2 processing a few issues with {{fgcmcal}} were exposed, and this ticket has consolidated these fixes into one.    First, visit level tests by [~<USER> show that the errors reported in {{fgcmcal}} {{photoCalib}} objects are much larger than for {{jointcal}}.  This is because the errors are taking into account the full calibration error, including uniformity, but this is not what the stack expects.  I do not believe these errors affect coaddition.  Instead, {{fgcmcal}} should be reporting just the "gray" error estimated locally on each ccd.  Second, there are some visits in PDR2 that have an airmass as large as 2.95 (zenith angle >70deg), which was beyond the range of the {{fgcmcal}} look-up table.  A new atmosphere table and LUT will be generated which goes to zenith angle of 75 deg which is the limit of the Subaru telescope.  Third, a couple of default {{fgcmcal}} config changes for {{obs_subaru}} including increasing the number of iterations in each fit cycle for better convergence, and fix an index error on the default {{fgcmcal}} aperture correction parameters.  Related, a bug in {{fgcm}} was fixed that did not properly persist internal aperture corrections for bands that did not have a lot of data (namely, N387).
Answer: 8106.0

User story: "Support M2 test."
Answer: 25407.0

User story: "This task will check the SAL published event and telemetry in M2 control system as the phase 2 . This is a following task of DM-23290."
Answer: 30045.0

User story: "skyCorrection for HSC-PDR2  using w_2020_05 "
Answer: 4434.0