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: h1. Goals  This effort is similar to [DM-23086] and [DM-23962] efforts, except the catalog will be ingested into the "small" Qserv cluster explained in [DM-25949].     h1. Implementation details  Files supporting the ingest installed on the GPFS filesystem at:  {code}  /datasets/<USER>gaia_dr2_02/  {code}  Many files are inherited (via symbolic links or copied and modified) from the previous effort:  {code}  /datasets/<USER>gaia_dr2_01/  {code}    The partitioning and chunk/table contributions phase will be run inside the latest version of the Docker container {{qserv/replica:tools-DM-25986}} (see [DM-25986}] which included the latest improvements and fixes to the Replication & Ingest system.    The ingest orchestration will be done from the master machine {{qserv-master03}}. This will include interactions with the Replication System's REST API, launching containers at workers.    There will be one container per worker. Each container will be used for partitioning input files into the worker's work folder, and launching many ingest streams, The number of streams per worker would be *16* which is equal to the number of the CPU cores per node. This allows to fully utilize CPU resources available to each worker.    There will be a dedicated _super-transaction_ started for each such stream.    Scripts and configurations used during this ingest are found in the dedicated Git package: https://github.com/lsst-dm/qserv-ncsa-gaia  
Answer: 18748.0

User story: "[~<USER> observed:    --butler-config now requires a .yaml file, and not a repository URI. This is confusing, since AFAIK most users think of Butler repositories as a location, not a config file.    [~<USER> responded:    That definitely has to be fixed since it has to be the case that any repository URI you give to the Butler() constructor must be acceptable here. S3 et al URIs must work.         I suspect this is just a restriction imposed by the option's type being set to MWPath, need to verify that and/or correct whatever the issue is."
Answer: 8542.0

User story: "This ticket updates the main telescope CSC page in obs-controls.lsst.io ([https://obs-controls.lsst.io/System-Architecture/CSC-Overview/Main-Telescope-CSCs/index.html#csc-overview-main-telescope-cscs])         It also reformats the user-guide section of ts-observatory-control, and adds some content.               "
Answer: 13023.0

User story: "Currently ctrl_bps has the initialization (--init-only) for each PipelineTask as separate compute jobs in the DAG to allow running of some jobs if --init-only fails for some jobs.  It has been recommended to move all of the --init-only into a single compute job (which means any --init-only fails halts running prior to any PipelineTask execution)."
Answer: 77916.0

User story: "Deploy DBB handoff buffer managers using {{bbcp}} for Auxtel and Comcam on NCSA test stand and verify they are working. This includes writing deployment-specific documentation for those in charge of operating the service.    "
Answer: 13574.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: Still using sqlite for the APDB and the Jan 2020 coadd HiTS2014 templates for this "make sure everything is still functioning" ap_pipe HiTS2015 rerun.    The results will be in {{/project/<USER>hits2015/rerun/cw_2020_08}}. The slurm job is 254561 and full logs (one per visit+ccd combo) are in {{/project/<USER>hits2015/slurm/ap_pipe254561-*.out}}.
Answer: 14157.0

User story: Now that WebDAV has been merged into datastore we have some code duplication with S3 that needs to be cleaned up. The more code we reuse the better chance we are of keeping WebDAV functioning without an explicit datastore test.    Also should clean up the remaining "if S3 do x elif WebDAV do Y" instances.    I propose to have a RemoteFileDatastore parent class.
Answer: 2599.0

User story: Got this error when building test plan and report for LVV-P67:         File "/Users/GComoretto/.local/lib/python3.7/site-packages/requests/models.py", line 940, in raise_for_status      raise HTTPError(http_error_msg, response=self)  requests.exceptions.HTTPError: 401 Client Error:  for url:   [https://confluence.lsstcorp.org/s/en_GB/7502/ac22fa19040b80942f38f572cb0ccfe31fa6e23d/_/images/icons/emoticons/help_16.png|https://slack-redir.net/link?url=https%3A%2F%2Fconfluence.lsstcorp.org%2Fs%2Fen_GB%2F7502%2Fac22fa19040b80942f38f572cb0ccfe31fa6e23d%2F_%2Fimages%2Ficons%2Femoticons%2Fhelp_16.png]     
Answer: 10177.0

User story: "Add sphinx-click-generated documentation to neophile.lsst.io and improve the README and documentation index."
Answer: 388.0

User story: "Make sure that the Dome CSC sends events whenever a command gets executed and in all other situations."
Answer: 54765.0

User story: "The quantum graph object that we have is still largely in the same form as it was when initially created. After having learned more about how the object will be used in various contexts it needs to be rewritten.    This ticket will  * explore what what apis the new Quantum graph object should have  * implement these apis  * adapt existing code to use the new object."
Answer: 59413.0

User story: "Submit an abstract for a poster covering the linkage analysis tool as a possible QA tool for small body linking algorithms. "
Answer: 1.0

User story: "Test the Jenkins with LabVIEW on my desktop to see it can do the unit test, generate the Junit xml reports, and publish or not. I think it might be easier to use the virtual box to do this test (install the Jenkins in the virtual box)."
Answer: 15589.0

User story: "MultiProFit currently only supports fitting within the bounding box containing a source's footprint (or the spanset therein). This ticket will add a configurable dilation distance to expand the bounding box, with the hope that this will reduce the number and severity of cases of fits with runaway size growth."
Answer: 63140.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: "Using the linkage analysis tool, run a 'perfect' linking algorithm on the newly simulated Solar System catalog and create a series of MPC submission files to test with during our multi-day working session with the folks at the MPC."
Answer: 93702.0

User story: "This ticket is to update the packaging and CI for LTD Keeper to bring it more in line with how we package Safir apps for long-term maintainability:   * pinned requirements.txt via pip-tools   * GitHub Actions   * pre-commit hooks, including black"
Answer: 15811.0

User story: "Attend a subset of PCW sessions that are relevant or interesting, including plenaries, External Synergies for Rubin Science, Commissioning & Validation, Survey Strategies, and the breakout session recap"
Answer: 136.0

User story: "In DM-26138 we ended up with a filter name that includes {{1.4}}.  This breaks butler ingest because gen2 puts the 1.4 in the file names and ButlerURI assumes that 4 is part of a file extension.  Fix ButlerURI.getExtension so that it only returns a single extension unless there is a special case of .gz, .bz2, .xz, and .fz (in which case it returns two).  This should fix ingest for filters with a dot in them and allow us to use the filter name we want for imsim."
Answer: 1343.0

User story: "There are some issues with the LTD version dashboard builds for qserv-ingest and other docs:   * qserv-ingest dashboard is not updating   * Truncation in the GitHub repository name"
Answer: 237.0

User story: "Currently, there is a park command that takes a value to park or unpark. There should be two separate commands to make it more clear to the user what is happening. Also fuse azimuth and elevation commands into one move command."
Answer: 54687.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: daf.butler.registry.queries is getting creaky and hard to work with; usage patterns and needs have slowly diverged from what it was originally designed to do, and it's accumulated a lot of bad encapsulation, tight coupling, weird and hard-to-document method preconditions.  This has gotten bad enough that it's very hard to include support for querying CALIBRATION collections on DM-24432 without major changes.    We also have a number of related changes on the horizon that we should at least consider in any cleanup or refactoring we do now:  * We need to make additive changes to the dimensions system (adding new dimensions, adding new metadata columns) less disruptive in terms of schema versioning.  * We have discussed replacing the commonSkyPix/HTM-based spatial joins with a system where the user explicitly declares up front the combinations of skymap, instrument, and skypix systems they want to use together, and then we just instantiate those relationship tables up-front.  That should make for faster queries, simpler query code (no trimming of query rows in postprocessing) and perhaps more configurable flexibility in the future for the kinds of relationships that can exist.  * We need to be able to give users more control over which variants of at least some spatial relationships are used in a query.  The use case we have is "give me all visit+detector data IDs for which the visit overlaps the tract, even if the visit+detector doesn't, and all HTM IDs at some level that overlap that visit+detector even if they don't overlap the tract", but I'd like to frame that problem in a more abstract sense before trying to solve it.      This ticket is only for design/prototype work, not actually implementing all of the above changes on master.
Answer: 32129.0

User story: "Build a 64bit CentOS 7 (aarch) container and test it with hardware setup  (temp sensors and POE hat)"
Answer: 10047.0

User story: "Make a branch of ts_salobj with volatile telemetry topics, for testing.    Branch from version v5.17.0, to simplify comparison with the version we are currently running on the test stand, as per request by [~<USER>."
Answer: 6521.0

User story: "Make a branch of ts_sal with volatile telemetry topics, for testing.    I suggest this be branched from version v4.1.4, to simplify comparison with the version we are currently running on the test stand. But this is up to [~<USER> and [~<USER>"
Answer: 17352.0

User story: "I might be missing something but it looks like the DECam WCS uses the flipX parameter in gen2 for raw data but it doesn't in gen3. I'm not entirely sure how that can be true.    Regardless LATISS will need flipping (DM-24592) so I need to add a class property to raw formatter base to indicate whether flipX should be applied. Should be quick."
Answer: 5786.0

User story: "Attend and contribute to PCS sessions."
Answer: 14038.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: "Whenever we re-export a registry the resulting yaml is generated with a random order of datasets. This really messes up git diffs by making it look like there are extensive changes when in reality the order changed but not much else.    Investigate whether we can improve matters. Options are to try to optionally add sorting to the SQL results or doing sorting of the python data structure directly (maybe forming a sort key from all the values in the dict within the lists)."
Answer: 96453.0

User story: "This ticket is to track the time spent on attenbding the PCW."
Answer: 6.0

User story: Add a new generic "heartbeat" telemetry topic. The long term plan is to transition to that and eliminate the event. During the transition the Watcher and LOVE should listen to both topics (if present) -- data on either is a heartbeat.
Answer: 25.0

User story: "In new base_slew Script. "
Answer: 19526.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: "DM-26310 is breaking Jenkins because www.lsst.org is not visible from Jenkins servers. We are using responses package so this shouldn't be an issue but it seems that we are failing to mock the {{requests.options}} call.  "
Answer: 46.0

User story: "It takes half a second for getCamera to read the HSC camera in HyperSuprimeCam instrument class every time we call it. This adds up really quickly when we are looping over exposures and calling {{loadCamera}}.    Add a simple lru_cache as was done for YAMLCamera in DM-25923"
Answer: 1274.0

User story: "Support the update of sensitivity matrix. Bo updated the sensitivity matrix and bending mode in the following two PRs:   1. [https://github.com/lsst-ts/phosim_syseng4/pull/3]   2. [https://github.com/lsst-ts/ts_ofc/pull/26]    Because this update will break the unit tests in *ts_ofc*, I will support the fix of them. In addition, the scientific pipeline uses the *gcc/g++ 7.3*. The [phosim_syseng4|https://github.com/lsst-ts/phosim_syseng4] has the problem of compilation. This task will try to upgrade it and do the related test.    The update of M2 force file in *ts_phosim* should break the unit tests as well. Need to fix them."
Answer: 2402.0

User story: The Firefly extension also relies on PageConfig (as did our savequit extension).  This is not compatible with JL 2.x, and I don't know what the support is going to look like in 3.x (it is being reintroduced in some form, though).    So I figured this would be a good time to namespace our extensions under "rubin.something", break the helper _functions_ that both jupyterlabutils and jupyterhubutils need into their own package, and then, once I have a settings-interrogation-endpoint mechanism, rebuild savequit, the query templater, and the firefly extensions to use it.
Answer: 12210.0

User story: "Add WebDAV support to ButlerURI and add a webdav datastore."
Answer: 1447.0

User story: "Create TunableLaser documentation and general code cleanup."
Answer: 62142.0

User story: "Matt Long has done the legwork to allow direct mounts of filesystems without NFS.  Switch over."
Answer: 1775.0

User story: "Try to clarify the documentation for data types in salobj topic classes, and what the callback function receives."
Answer: 1066.0

User story: "PexConfigFormatter is anomalous in that it's defined in daf_butler but can't be used by daf_butler, shouldn't be used by daf_butler and can't be tested in daf_butler.    It should move to obs_base where the other lsst-specific formatters exist. It can then be tested properly in obs_base."
Answer: 13332.0

User story: "Sometimes when mobu is creating a lab, it gets stuck.  This happens because mobu has to keep polling the spawn URL until it gets a redirect (to the lab).  This is the only way to know when the hub is finished spawning.    So in mobu, we keep retrying until we get a redirect.  But we shouldn't retry forever!  We need a timeout of the number of retries, so we can make progress and try again (and alert on the expiration of the number of retries)"
Answer: 73.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: "At the moment, DBB handoff manager does not collect any metrics regarding files it transfers. The goal is to make it persist information allowing one to answer questions including, but not limited to:  * When was a file created?  * When was the file transferred to the endpoint site?  * What was the transfer rate?"
Answer: 23191.0

User story: "Currently DBB handoff manager uses internally {{scp}} to transfer files between the handoff and endpoint sites. However, some _ad hoc_ tests indicate that {{scp}} does not fully utilize the available network bandwidth.    The goal is to modify the handoff manager to allow a user to specify a transfer tool (and its options) in manager's configuration which should make switching to other, more efficient transfer tools (e.g. {{bbcp}}) rather straightforward. "
Answer: 10881.0

User story: "Current Python based M1M3 uses pyqtgraph for graphs needs. PySide2 includes PyCharts (which weren't available in the first Qt 5.x releases) and pyqtgraph needs native install to setup the graphing. Using PyCharts will be much simpler than awkward install of pyqtgraph and PySide2 combo."
Answer: 11393.0

User story: "Doc is available here:  https://sdk.operatorframework.io/docs/building-operators/golang/project_migration_guide/"
Answer: 63201.0

User story: "PR is here: https://github.com/lsst/qserv-operator/pull/13"
Answer: 10093.0

User story: "Provide an interface so that qserv-operator user can enable Qserv to create and store core files."
Answer: 24657.0

User story: "The document series pages on [www.lsst.io|http://www.lsst.io/] are creating infinite redirects based on the search state cached in the URL. The advanced search page had a similar issue and we fixed that in  DM-24955."
Answer: 9907.0

User story: "The lsst-texmf build process hasn't been updated in several years, and it's now worth making several updates to improve the stability and performance of both CI and the Docker image product going forwards:   * Switch to GitHub Actions for better performance   * Target Python 3.7 for both the test environment and the Docker image   * Use a multi-stage docker build and intermediate image caching to create a compact docker image that no longer relies on https://github.com/lsst-sqre/lsst-texlive"
Answer: 10107.0

User story: "This ticket is to bring documenteer into line with the latest development infrastructure used by other SQuaRE PyPI packages:   * GitHub Actions for testing and PyPI deployment   * Black formatting   * pre-commit   * mypy type checking    This will make it easier to further develop and maintain documenteer."
Answer: 53436.0

User story: "Tasks:    singleFrameDriver    makeSkyMap    coaddDriver    multiBandDriver"
Answer: 14629.0

User story: "Provide more Doxygen docs for Context, Model and related (now singletons). Publish build Doxygen doc on https://ts-m1m3support.lsst.io"
Answer: 24764.0

User story: "Determine a suitable model for Hexapod compensation, with coefficients."
Answer: 5754.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 distributed data generator currently calls DataGenerator through a subprocess.run call on datagen.py. This is unnecessary and it would also be useful to track how much time is being spent on various aspects of data generation and ingestion, which is difficult to transfer with the subprocess.run. So, DataGenerator should be called directly, moving command line arguments to configuration files and changing DataGenConnection to transmit the new configuration information and timing data. "
Answer: 38741.0

User story: "Organize developer guide repo structure."
Answer: 14376.0

User story: "A simple notebook showing how to access the EFD Parquet files from S3.     Note that for this example the S3 Sink connector was configured to partition the data on an hourly basis.     [~<USER> we can plan on extending the EFD client to access the Parquet files. It would be handy if the EFD client could handle the S3 credentials and help to figure out which S3 bucket to read for a given EFD instance and which files to download from the S3 bucket given the time span.         "
Answer: 4679.0

User story: "The hash suffix is based on the sha1, but not the version, of dependencies. As a result, the hash does not change for top level products when dependencies have changes."
Answer: 148.0

User story: "Using this opportunity to update to reflect recent changes in the lsst-dm/milestone package."
Answer: 8.0

User story: "This is not a conversion of a gen2 RC2 run.  This is actually running RC2 using gen3 (BPS).  This first time limiting to only one tract.    Stack version:  w_2020_31    Gen3 repo:  /project/hsc/gen3repo/rc2w30_ssw31  (Use Gen2 converted repo per dm-middleware discussion)    Tract: 9615  (want smallest, change if wrong tract)"
Answer: 17315.0

User story: "Support the new enum syntax in IDL file: (1) shared enum such as the *SummaryState*, and (2) assign the enum value in <Enumeration> of xml. Use the *Test* subsystem as an example, the structure of summary state looks like this:    {color:#4c9aff}struct logevent_summaryState \{{color}  {color:#4c9aff}    long summaryState;{color}  {color:#4c9aff}    long priority;{color}  {color:#4c9aff} };{color}    There is no information to say summaryState is a enum (e.g. *// enum :*).    In addition, the following part in *Test* xml does not reflect to IDL file:  {color:#4c9aff}<Enumeration>Int0ValueEnum_Zero=0, Int0ValueEnum_Two=2, Int0ValueEnum_Four=04, Int0ValueEnum_Five=0x05</Enumeration>{color}"
Answer: 27379.0

User story: "Release 0.2.0 add the following features:    * Add first and third quartiles (q1 and q3) to the list of summary statistics computed by the aggregator.  * Ability to configure the list of summary statistics to be computed.  * Pinned top-level requeriments.  * Add Kafka Connect to the docker-compose setup.  * Use only one Schema Registry by default to simplify local execution.  * First release to PyPI.    Python package is now on PyPI too https://pypi.org/project/kafka-aggregator/"
Answer: 11870.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: "Attend 2020 RubenObs PCW."
Answer: 11801.0

User story: "qhttp ajax unit test sometimes fails in Jenkins.  Troubleshoot and fix."
Answer: 47.0

User story: "[~<USER> & [~<USER> have prepared notes on how the changes made in release 20.0.0 impact on the data products which will be consumed by end users. Please ensure these notes are included on the pipelines.lsst.io site."
Answer: 5926.0

User story: Make some improvement to ts_observatory_control:        * Add {{inspect_settings}} method in {{RemoteGroup}} to return all available settings for CSCs in a group.    * Add {{rot_sky}} strategy on slew methods, this will cause the rotator to remain fixed.   * In {{Usages}} make a "generics" session and a CSC section for topics   * Fix {{rot_angle}} strategy in MTCS slew.   * Add {{auto_sky_angle}} mode where it will check if it is possible to slew to the user provided sky angle or go to the +/- 180 degrees
Answer: 36956.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: Working on the new pipeline_check package I realized that the 33MB dark and bias files can trivially be compressed using fpack to be 5MB each.    Compressing these single data array FITS files (GZIP_1 or GZIP_2) then breaks ExposureFitsReader with a SEGV when trying to read the mask that does not exist:    {code}  afw.image.MaskedImageFitsReader WARN: Mask unreadable (FitsReader not initialized; desired HDU is probably missing.); using default  Process 58746 stopped  * thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x8)      frame #0: 0x0000000110ee02fd libafw.dylib`lsst::afw::image::MaskedImage<float, int, float> lsst::afw::image::MaskedImageFitsReader::read<float, int, float>(this=0x00007ffeefbf1628, bbox=0x0000000121f54770, origin=PARENT, conformMasks=false, needAllHdus=false, allowUnsafe=false) at MaskedImageFitsReader.cc:216:43     213              }     214              LOGL_WARN(_log, "Mask unreadable (%s); using default", e.what());     215              // By resetting the status we are able to read the next HDU (the variance).  -> 216              _maskReader._fitsFile->status = 0;     217          }     218          try {     219              variance = std::make_shared<Image<VariancePixelT>>(  {code}    The compression confuses the reader because compression creates an extra hdu binary table. MaskedImageFitsReader does not look at the EXTTYPE header and so tries to read the next extension as if it's a mask.    I'm not entirely sure why we write FITS files with EXTTYPE headers but then don't use them when we read.    The most important issue here is the SEGV.    To reproduce run {{fpack -g2}} on the {{CALIB/DARK/2013-11-03/NONE/DARK-2013-11-03-010.fits}} from {{testdata_ci_hsc}}.  Then try to read the .fits.fz file with ExposureFitsReader:    {code:python}  from lsst.afw.image import ExposureFitsReader  reader = ExposureFitsReader("dark.fits.fz")  e = reader.read()  {code}    [~<USER> points out that we probably should be reading these as Image and not Exposure but that might require invasive changes to pipelines.    A more generic solution would be for MaskedImageFitsReader to query for EXTTYPE and if there are no MASK and VARIANCE extensions, skip trying to read them regardless of the number of extensions found.    
Answer: 1334.0

User story: "Having compiled “requirements” and use cases in DM-26069, produce a design sketch for a new system for representing filters. This should address the requirements identified on DM-26069, but need not make reference to or be based upon the RFC-624 design (except insofar as you regard that as useful).    This design will ultimately need to be accepted by an RFC, but this ticket can be closed once the design document is ready, without the RFC having been adopted (or even filed)."
Answer: 72118.0

User story: "A test failed in the nightly (again) which is the same problem but in a different test. This time I will run the tests locally in a similar directory."
Answer: 57.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: "HS need to be deployed using version 2.3.2"
Answer: 8.0

User story: "This task is to cover the time spent investigation the LabVIEW deployment solutions that are being used. "
Answer: 17277.0

User story: "Once the HVAC CSC has been created, the conda recipe can be created as well."
Answer: 33209.0

User story: "Create the CSC for HVAC that at least publishes the HVAC telemetry based on what it receives via MQTT."
Answer: 31229.0

User story: "Once the EAS GitHub repo, code and unit tests have been modernized, the conda recipe can be created as well."
Answer: 30368.0

User story: "Once the MTECC GitHub repo, code and unit tests have been modernized, the conda recipe can be created as well."
Answer: 30368.0

User story: "The EAS GitHub repo is very much outdated and needs to be modernized. This also is true for the code and unit tests. Please fix this all."
Answer: 27389.0

User story: "The MTEEC GitHub repo is very much outdated and needs to be modernized. This also is true for the code and unit tests. Please fix this all."
Answer: 23049.0

User story: "Update ctrl_bps to meet LSST coding standards such as making sure very file has license at top, everything that needs a docstring has one, run black to reformat code, etc.  Do not do code rewrites or reorgs in this ticket."
Answer: 2686.0

User story: "Since we switched to use lock files for the environment definition, the env diff is not useful."
Answer: 2549.0

User story: "Due to the sweeping changes to the {{pipe_analysis}} scripts of DM-22255, there have been some inevitable bugs introduced that are being caught via more detailed scrutiny of the plots as well as some non-standard (i.e. non-default) run modes. This ticket collects and fixes three such bugs:   * fixing the plotting and logic of ccd outlines to use the correct WCS   * moving setting of newly added {{plotInfoDict}} so that it is available when using non-default configs (e.g. {{plotMatchesOnly=True}}, etc.)   * add missing {{plotList.append}} for the sky object plots in {{visitAnalysis.py}} so that the plots get persisted (I noticed they were missing in recent RC2 processing runs)"
Answer: 34759.0

User story: "As summary.    The lack of a P6 API means we can't actually pull this information directly from there, but we can get it from the {{lsst-dm/milestones}} repository."
Answer: 70602.0

User story: This ticket is to track the time spent participating in the Operations Rehearsal #2 which ran from Mon, July 27, 2020 through Thurs, July 30, 2020.  In particular, I was asked to provide "QA" support.    See [the confluence page|https://confluence.lsstcorp.org/pages/viewpage.action?pageId=120786067] for details of the rehearsal and its execution.
Answer: 1234.0

User story: "Convert RC2 w_2020_30 to gen3 repo"
Answer: 4043.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Support activities to develop a dome environment conditioning contract, to control the temperature during daytime. The activities include reviewing proposals, provide technical information to potential contractors, meetings with Rubin Observatory reviewers and contractors."
Answer: 18471.0

User story: "Prepare and coordinate weekly meetings on dome control software with EIE contractor."
Answer: 18472.0

User story: "Some of the metrics (e.g., AM1-3, AD1-3, AF1-3) are calculated using stars/objects at large separations, so that calculating measurements at a patch scale won't work. Some metrics will thus need to be calculated at the tract scale (or larger). Implement the ability to use different spatial scales for different metrics."
Answer: 50700.0

User story: "Now that the basic all-sky CSC and driver are done, they need to be commanded as well. In order to test that functionality, create an additional python script and command the CSC with that."
Answer: 18277.0

User story: "Now that the basic ESS CSC is done, it needs to be commanded as well. In order to test that functionality, create an additional python script and command the CSC with that."
Answer: 22068.0

User story: In the nightly release build https://ci.lsst.codes/blue/organizations/jenkins/release%2Ftarball/detail/tarball/6041/tests one of the ingest symlink tests failed:    {code}  self.assertTrue(not uri.scheme or uri.scheme == "file", f"Check {uri.scheme}")  > self.assertTrue(os.path.islink(uri.path))  E AssertionError: False is not true  {code}    Normal Jenkins is passing and the job worked the previous night.    Only two tickets were merged yesterday: DM-26119 and DM-25985; and neither look like they should affect ingest.  
Answer: 324.0

User story: "Create CBP documentation based on csc doc template."
Answer: 33063.0

User story: "Whenever bin/deploy is ran, it will attempt to reinstall a conda environment even if that exact conda environment is already deployed. On jenkins workers for linux, this is really slow because the transactions are very slow over networked file systems due to the large amount of small files.         Some kind of fast path could probably be created - particularly when we are using lock files. Simply verifying an existing environment has the same {{conda list --explicit}} output that the environment we are asking to install should be enough to bypass the extra step."
Answer: 3081.0

User story: "Tasks ran:    jointcal    processCcdWithFakesDriver    coaddDriver    multiBandDriver    visitAnalysis     "
Answer: 30203.0

User story: "The ESS code has been adjusted to support a single USB device. Integrate that code into the CSC."
Answer: 332.0

User story: "Time spent coordinating, creating agenda, followups, reporting and lastly holding the weekly TMA Software Integration Meeting"
Answer: 19587.0

User story: "This task is to begin working on the RBF for the Deployable Platform.     - Install LabVIEW   - Install Visual Studo   - Install RBF intellesense addon  - Download the repository"
Answer: 59765.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "This task is to cover the first effort into integration the virtual PXI's into the current virtual environment. I am unsure how long this task will take so I have broken it into two parts to prevent another major under-estimate like with the recent HMI.     About this task I do know the following;    - There are specific IP addresses that need to point to the PXI's the same IP's that need to be changed when integrating the software into the actual telescope.     - I think? that a new network card needs to be configured to be part of this environement. That's because the PXI's talk on an ether-cat line. "
Answer: 35567.0

User story: "This task is to cover the first effort into integration the virtual PXI's into the current virtual environment. I am unsure how long this task will take so I have broken it into two parts to prevent another major under-estimate like with the recent HMI.     About this task I do know the following;    - There are specific IP addresses that need to point to the PXI's the same IP's that need to be changed when integrating the software into the actual telescope.     - I think? that a new network card needs to be configured to be part of this environement. That's because the PXI's talk on an ether-cat line. "
Answer: 35575.0

User story: "Generate a list of essential components of ts_sal that are required  in order for Jenkins to be able to create the CSC runtime assets  and run the tests"
Answer: 12873.0

User story: "Attend the virtual PCW meetings"
Answer: 17234.0

User story: "Attend the 2020 Project & Community Workshop 8/10-8/14"
Answer: 15872.0

User story: "Please update the version of Python in lsstts/robot:latest so we can use features in Python 3.7.    Another option to consider is running ts_xml Jenkins with lsstts/salobj instead, if that would work."
Answer: 13069.0

User story: "[~<USER> points out that the saturation levels in the yaml files are ignored in favour of the CCD-type defaults.  Please fix this.     "
Answer: 1937.0

User story: "The data generation system needs methods from sphgeom::Chunker to identify chunk boundaries and determine neighboring chunks. These methods need to be accessible from python. "
Answer: 25921.0

User story: "Attend the Vera Rubin project and community workshop"
Answer: 19797.0

User story: "The ATHexapod is not setting its internal state to be FAULT when the start command fails. It does issue the proper summaryState info to SAL, but then its internal state is inconsistent with what is presented by the EFD."
Answer: 23966.0

User story: "Support activities to develop a dome environment conditioning contract, to control the temperature during daytime. The activities include reviewing proposals, provide technical information to potential contractors, meetings with Rubin Observatory reviewers and contractors."
Answer: 63.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "As discussed on DM-26195 it would be useful to skip instrument dimensions on import if the instrument has already been registered.    One quick work around is to allow the user to specify a list of dimensions to skip and use them in the {{Backend.load()}} method.    It looks like this is a trivial fix as such and it does work."
Answer: 496.0

User story: "When time permits rewrite the Hexapod and Rotator CSC commanders to use the standard salobjlCscCommander and delete the hexrotcomm.CscCommander.    I wrote the hexrotcomm version first, and the salobj version based on that. The salobj version is now much better."
Answer: 15911.0

User story: "When using butler export to save datasets to YAML, we tend to include relevant instrument dimensions such as instrument, physical_filter, and detector.    In many cases where you want to import into an existing repository we have already run {{butler register-instrument}} and these dimensions have already been defined. Import therefore fails. Currently we have to edit the YAML file. It would be nice if it was possible for either these instrument dimensions to be skipped (optionally) on export or else have the dimension duplication be ignored on import.    It's possible that skipping on import would be more robust.    I believe that currently skipping named dimensions on export is quite involved.    "
Answer: 68129.0

User story: "Install the TMA simulation components (PXI VM's, docker container, EUI)  on my local machine to support <USER>and Teknikers upcoming development efforts"
Answer: 24354.0

User story: "Improve the doc string for CscCommander.amain to document the parameters and clarify that index is a required argument."
Answer: 5856.0

User story: "As SAL and XML are released, the build scripts need to be updated accordingly.  Normally, there are specific events that I use to create these tasks (a release, for example).  However, this sprint had no such event, but there was significant work to be done on the scripts.  Namely, activating the SALSubsystems.xml unit tests and writing the Jira tickets for outstanding work on that file."
Answer: 48.0

User story: "This task covers the time necessary to prepare for and then lead the hackathon to create the various CSC Conda Jenkins builds."
Answer: 218.0

User story: "To {{sourceDeblendTask.py}} and {{scarletDeblendTask.py}} respectively, thereby implementing RFC-717. "
Answer: 1779.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 DM-26119 I learned that when pipetask uses multiprocessing we never instantiate an {{Instrument}} and therefore we never define the filters for that instrument in the global singleton.    In single process mode it's fine because at some point an Instrument is created.    Modify pipetask multiprocessing such that the dataIds are scanned for the "instrument" dimension and we call {{Instrument.fromName(dataId["instrument"], registry)}}.  Currently we only expect one instrument.    When the singleton is removed it's likely that some related initialization will be needed to register the filters but we assume that would allow the same initialization for multiple instruments.    CC/ [~<USER>, [~<USER> in case they have come across this problem before.
Answer: 1524.0

User story: "In order to replace {{validate_drp}} in CI, we need to have the data in a gen3 repository.  I believe the steps are to:  1) create a gen3 repository  2) export calibration products from the gen2 git lfs repository to a gen3 repository  3) run the processCcd version of the gen3 pipeline on the resulting repository"
Answer: 77763.0

User story: "Write the test framework of SAL LabVIEW API. This task begins to construct a framework to test the LabVIEW API for each new SAL update. In the past, we used the component CSC in LabVIEW to test this. Now, we need a framework to test this automatically. The SAL LabVIEW APIs rely on the shared memory, which is not needed for the C++ and JAVA APIs. Therefore, this kind of automatic test framework should be helpful for the maintenance of CSC in LabVIEW. This task is in the phase 1."
Answer: 60144.0

User story: "In order to support running the Hexapod simulator on k8s, the ATHexapod needs to be able to configure the supporting IP address via an envvar. The variable will be called (to be checked) HEXAPOD_SIM_SERVICE_HOST."
Answer: 48817.0

User story: "Optimize the tool that generates the SAL LabVIEW APIs. The [ts_SALLabVIEW|https://github.com/lsst-ts/ts_SALLabVIEW] is used now to transform the data type from SAL IDL. The execution speed is slow now. This task will try to optimize the performance.    * I noticed some type definition do not work as expected. This task will try to fix this as well."
Answer: 18593.0

User story: "The validity ranges in the calibration database are currently set as days with no time included, which means that they implicitly round down.   In consequence, a calibration that should be valid on the last day of a validity range can never be looked up.    The simplest fix is to make validEnd equal to validStart for the next interval.  There is a problem for calibs taken exactly at the roll-over, but this window is only 1ms wide, and providing we don't take calibs at midnight we will be OK.  For gen2, I think this is OK, but we should handle it properly in gen3 (especially as people like to take calibrations on dark and stormy nights)    [~<USER> points out that the place to fix the code is in the {{fixSubsetValidity}} method in ingestCalibs.py"
Answer: 1258.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 TVS crowded field working group is working on testing scarlet on DECam images of the globular cluster NGC-6569. One of the issues is detecting all of the sources in the field, since the high stellar density and wide PSF in redder bands makes detection more ambiguous.    This ticket is to test out the wavelet detection algorithm of Remy Joseph. The idea is that because the field is dominated by point sources, we should be able to use wavelets to create a high pass filter for the image and only allow the highest frequency coefficents to pass through, removing the wings of PSFs and lowering the detection threshold."
Answer: 1007.0

User story: "Account for EFD maintenance work on the week of July 13 to July 17.    - Base EFD: Recovered Kafka after Control Center license expired. The root cause for that is configuration control. I personally need better control of which app is running in which environment. I should be able to discovery these problems before it happens.    - Tucson Test Stand EFD: was updated early this week. Tiago needed to used that environment while the NCSA Test Stand was under maintenance.    It was useful during the week but today we had errors due to disk space which reached 95% on that machine. We need a plan to expand the k8s cluster there and move the EFD from k3s.    - NCSA Test Stand EFD: there was an intervention during the week. Everything that was on the NTS k8s cluster local storage under /data was wiped out. We recovered the Chronograf database which was local (by mistake) and moved it back to NFS using the nfs-storage class. Recreated the Kafka PVs that are local and we are making sure the system is healthy again.  "
Answer: 1.0

User story: "This task is to setup the needed software environment (by virtual box) on my MacBook Pro to update the M2 software. The original linux laptop and desktop are in Chile and Tucson office individually. Therefore, I need to setup the environment on my personal laptop to do the development of M2 software."
Answer: 7555.0

User story: Following DM-24475 the obs_base build failed because there is a "+" in the build path and somewhere a double URI encoding is happening so that the + is encoded and then the resulting % is encoded.
Answer: 681.0

User story: "There has been for some time an intermittent crasher that occurs sometimes during teardown of the boost::unit unit test for qhttp (testqhttp).    <USER>recently obtained a repeatable failure and extracted a core; investigation of this indicated the problem is occurs as a bad object dereference in a race between the asio service teardown in one thread and a socket accept handler executing on the service handler thread."
Answer: 1008.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 support running DDS in shared memory mode, we require the following changes to the nublado build and deployment.    * Use the licensed version of the OpenSplice RPM for building. This requires access to the nexus private yum repository. A yum repo file is attached to the ticket for the access, but note that it requires authentication. T&S software will provide the credentials for that authentication via an agreed upon method.  * There are some changes on T&S package build steps for the licensed version of OpenSplice. Telescope and Site can provide the necessary changes to the sal-sciplat-lab repo via PR.  * The consequence of using the licensed OpenSplice RPM is the resulting build images can no longer be stored in a publicly accessible repository. The project maintains as private Docker repo within the nexus server. The nexus repo URL is [https://ts-dockerhub.lsst.org|https://ts-dockerhub.lsst.org/]. T&S software will provide the credentials via an agreed upon method. Since SQuaRE has access to the VaultSecret storage, the credentials could be retrieved that way (see below).   * A new OpenSplice configuration file needs to be used to support the shared memory configuration. The one to use is attached to the ticket. Recall that the net1 replacement still needs to occur.  * Since the image is now in a private Docker repo, the deployment needs imagePullSecrets in the pod spec. VaultSecrets for this are already available on all sites. Please see the following for the paths: [https://github.com/lsst-ts/argocd-csc/blob/master/apps/cluster-config/templates/vault-secret.yaml]  * In order for the shared memory configuration to work, the deployment needs a “hostPath” volume for the pod spec. This path needs to be site configurable as it will not be the same from site to site. While the name is an implementation detail, we have labelled ours osplshmem. On the NTS, the system path is /scratch.local/ospl. We do not have a location for base or summit yet.  * The “hostPath” volume from above needs a volumeMount for the container spec. The mountPath must be /tmp  * Another consequence of the shared memory configuration is that the hostIPC and hostPID attributes in the pod spec must be used and set to true."
Answer: 94058.0

User story: "Ensure that locking works adequately on Amazon EKS + FSx"
Answer: 2073.0

User story: "Get our extensions running in 2.x"
Answer: 3364.0

User story: "In the current baseline, version 5.0, on page 6:  {quote}  A list of existing distributor/brokers as of the writing of this document is shown in Error! Reference source not found..  {quote}  and on page 11:  {quote}  as well as the historical data in Error! eference source not found. suggest that this is achievable.  {quote}    "
Answer: 130.0

User story: "add the options block that disables concurrent builds and sets some discard options for old builds"
Answer: 17.0

User story: "Add new packages to the scipipe_conda_env environmnent."
Answer: 12935.0