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: Our current approach to spatial indexing on the sphere is simply to store the HTM IDs each region overlaps at a particular level, in an extra "common skypix overlap" table for every table that has a region column.  This might be an okay approach for regions of a certain size, but it's definitely not a good approach for regions of arbitrary size, and probably not close to the best approach even for its ideal region size.  Doing better would probably require using special index types built for spatial overlap queries (R trees and variants thereof).  While the databases of interest to us (SQLite, Oracle, and PostgreSQL) do not support indexing regions on the sphere natively, they all do provide ways to index 3-d bounding boxes, and the lsst.sphgeom objects we work with provide ways to get 3-d bounding boxes (for a unit sphere).  The interfaces for the three databases are quite different, however, so the big challenge is probably encapsulating that functionality behind a consistent interface for the rest of our Registry code to use.  We might be able to leverage SQLAlchemy hooks for some of this customization, but I doubt they will cover everything.  While Oracle and PostgreSQL both treat geometries as column types and spatial indexes much like normal indexes, they have different syntax for inserting, querying, and relating them.  SQLite is even more different: its R tree implementation involves creating a special table for every spatial column, in which lower and upper bounds behave like regular (but separate) columms.  Adding at least some of the abstraction to our Database class might be a lot easier, and no less usable, though at present it doesn't do much with SELECT queries (they're just passed through to SQLAlchemy directly).  And I don't think this functionality needs to be totally transparent - just database-generic.  It would be totally reasonable for Registry code that's using our Database interface to work with a spatial column to have to do things it wouldn't have to do with a normal column, like manually extracting bounding boxes from regions for inserts, calling Database methods to get SQLAlchemy expressions that represent overlaps in query join/where clauses, or doing post-query filtering in Python (as we do now).  This ticket is for adding that abstraction layer to some combination of SQLAlchemy and the Database class.  I'll create another one for actually using it in Registry (maybe after the design for this one is further along). 
Answer: 20385.0

User story: "Run M1M3 cRIO with ICL hardware simulator."
Answer: 103038.0

User story: "<USER>needs Vault secrets created for a private Docker repository, which will be used in the sandbox, NCSA teststand, summit, and base Kubernetes clusters."
Answer: 1.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "I'd certainly believe that these warnings mask a real problem, but it's already been reported upstream (https://github.com/astropy/astropy/issues/8673), and they make it extremely difficult to develop against tests in obs_packages - {{test_convert2to3.py}} in obs_subaru emits 1700 lines of these, for example.    {{warnings.catch_warnings}} + {{simplefilter}} seems to take care of the problem.     "
Answer: 1381.0

User story: "In this ticket we implement an example to demonstrate the Faust [windowing|https://faust.readthedocs.io/en/latest/userguide/tables.html] feature that can be used for aggregation of kafka streams.    The general idea is that you can use a Faust agent to process the stream of events  (messages) from a given Kafka topic and add those messages to a Faust table for persistence. The table is configured as a tumbling window. The window configuration parameters are a size and an expiration time. When the window expires a callback function is called to process the messages in that window. That's when the aggregation happens and a new Kafka topic is produced with the aggregated values.    A docker compose config is provided to start a local Kafka cluster to run the example. The instructions to start the Kafka cluster, the Faust worker and the producer are described in the README.  The docker compose also includes the Confluent Control Center which is handy to inspect the topics, their configurations and the consumer lag for the Faust consumers when running the application.    NOTE: running multiple Faust workers to distribute the application load currently crashes the application, this will be investigated in DM-24473.  "
Answer: 17080.0

User story: "It's 20MB, but I don't see anything but text files. There's probably something big in the history that should be eliminated."
Answer: 2497.0

User story: "Alternative options for sample alerts, as well as the proposal to delay the deadline for full proposals in light of COVID-19, as discussed at the DM-SST meeting 2020-04-06, should be presented to the SAC for review on 2020-04-08. "
Answer: 88969.0

User story: "Thought I had this but it needs a bit more work .."
Answer: 1027.0

User story: "[~<USER> provided us 3 tsv tables along with their schemas from the DESC simulated-LSST data and we want them ingested into Qserv.   * *ccdvisit*   Data in this table are not spatial. They will be loaded into all workers.   * *object* (dpdd_object)   * *forcedsource*   I will partition the latter two using ra & decl in each file (an object has a fixed ra & dec across the two tables), and load into Qserv."
Answer: 37348.0

User story: "The salgenerator now has the GENERATE option, that runs validate, html, cpp and idl processes in one command line option.  Write a test to validate this step."
Answer: 30385.0

User story: "The salgenerator has an IDL step that needs to be tested.  Add this in the [https://github.com/lsst-ts/robotframework_salgenerator] repo and get it running on Jenkins."
Answer: 17285.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: "Preparatory to DM-17597, we need Gaia+PS1 refcats (sub-selected from the current refcats) for each of the datasets in testdata_jointcal. This ticket is to extract the necessary shards from the refcats in {{lsst-dev:/datasets}} and put them into the relevant subdirectories in testdata_jointcal.    This ticket does not involve any reprocessing of the test data, nor does it involve changing jointcal or fgcmcal to use the new refcats (since that would change the measured metrics)."
Answer: 1279.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 this notebook we have used statistics generated from sky objects to quantify and qualify sky over-subtraction and under-subtraction within Tract 9697. We performed three custom runs of coaddDriver to re-create HSC-SSP equivalent PDR1, PDR2 and PDR3 data using the current DM stack software. We further performed three custom runs of multiBandDriver using these data, extracting unmasked circular aperture fluxes within radii of 9 pixels and 250 pixels. Sky objects are pseudo-objects placed in regions where no other detections were found, and therefore should act as a measure of sky estimation success or failure across our dataset. Much of the analysis performed here leads on directly from efforts described in DM-23641.    We find significant variations in the sky estimation outputs employed over the course of HSC-SSP processing. PDR1 and PDR3 data visually exhibit significant sky-oversubtraction around bright sources, or in the vicinity of clusters of bright sources. These are likely caused by source flux or 'flux bridges' between bright sources being inadequetly identified at the source detection step, and included in a subsequent definition of a background sky map. Sky oversubtraction surrounding bright sources in PDR1 data gave rise to the term 'divot': the negative halo of flux surrounding bright sources. The radial extent of the divot in PDR1 lies further away from any given bright source than the equivalent divots in PDR3 data.    In PDR2 data, the divot issue appears largely to have been resolved, with minimal evidence for sky oversubtraction around bright sources. However, PDR2 data exhibits a much larger variation in background sky flux in the field, evidenced by sky oversubtraction in the least densely populated areas within this tract. The cause of this remains unclear, yet is likely linked to CCD and imaging artefacts (e.g., ghosts, ghoulies) compromising sky estimation efforts.    In summary, we find that all three datasets exhibit evidence of sky over-subtraction, either in densely populated regions (PDR3), sparsely populated regions (PDR2), or both (PDR1). The varying sky estimation routines employed here and their impact upon these performance metrics should be carefully considered when generating further improvements to our sky estimation routines in the future.    The attached notebook {{skycomp.ipynb}} contains all analysis and code. A PDF version of this notebook ({{skycomp.pdf}}) is also provided. The {{scripts.tar.gz}} file contains stack processing scripts and associated configuration files. All patch postage stamps may be viewed at this link: https://lsst-web.ncsa.illinois.edu/~<USER>skycomp/plots/0009697/"
Answer: 85662.0

User story: "Planning for the April 2020 PM. Plan for PM will be linked to the maintenance story for the month  This ticket had been created automatically Primavera ID: None"
Answer: 92384.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: "There is some duplicate code in particularly the test code. Review and refactor. Also a task scheduler is needed to poll the status command on a regular basis. Add it."
Answer: 291.0

User story: "This change will update OODS to the 2.10-rc3, and CSCs to the ts_xml 5.0.0_RC1 and ts_idl 1.1.3"
Answer: 10046.0

User story: "It turns out that a lot of the overhead in running {{dataRef.datasetExists()}} is extraneous path checking when the template is a relative path.  A quick change to the logic in {{posixStorage.search}} can speed up this operation by ~60% in tests, which is useful when finding large numbers of files (especially, but not limited to, global calibration in {{fgcmcal}})."
Answer: 1986.0

User story: The Apache proxy for Firefly provided by IPAC to LSST has fallen out of date with the ACME protocol used for certificate transactions.    It must be upgraded to ACMEv2 in order to continue to function.    Please generate an updated container image on DockerHub at {{ipac/proxy}}.  To support future configuration control activities, please apply the tags "latest" and "1.1.0" to this image, and, if possible, apply the "1.0.0" tag to the previously available image.
Answer: 3.0

User story: "Will combine information on these pages:    [https://confluence.lsstcorp.org/pages/viewpage.action?pageId=120786640]    [https://confluence.lsstcorp.org/display/LSSTCOM/Commissioning+Activities+2019-04-02+Meeting+notes]    [https://ts-salobj.lsst.io/salobj_cscs.html]    Plus status of different CSCs.     "
Answer: 28639.0

User story: "Recording the conda environment hash used for a particular tag will aid in recreating that environment later for new installations.  It doesn't help for {{eups distrib install PKG VERSION}}, but that is relatively rare."
Answer: 1723.0

User story: "Run the builds for Base Dev Image, SalObj Container, and Develop-env. Familiarize with process, and address any build problems that arise. "
Answer: 8358.0

User story: "Currently WriteSource Table requires that base_LocalPhotocalib and base_LocalWcs columns are present.      Optionally add those columns from a calexp if they are not present."
Answer: 34965.0

User story: "When designing the butler command line tools it is clear that life would be much simpler if an instrument could be referred to by name rather than by instrument class. It should only be instrument registration that requires the full class name. All other operations should work by specifying the name, looking up the name in registry and retrieving the class name, using doImport on that class, and instantiating the class for downstream usage.    For this to work we need two changes:    # Add the instrument class full name text string to registry.  # Have an API ({{butler.registry.getInstrument}}?) that will return an instantiated gen3 Instrument (they don't need parameters) given the name of the instrument.    "
Answer: 1397.0

User story: "Integration testing"
Answer: 128917.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: "When using newer versions of CFITSIO (> 3380 aka 3.38), keys written by cfitsio via fits_write_record / ffprec are upper cased.    When reading from FITS files, some parts of CFITSIO will uppercase header keywords but not all cases.    afw should warn when it knows that, when writing to a file, lowercase keywords will be encountered.    afw should also uppercase all headers on read, and possibly warn users when this has happened."
Answer: 23238.0

User story: "Jim reported issues with round-tripping and comparison of timestamps in slack: https://lsstc.slack.com/archives/C2JPT1KB7/p1586273799139100  Need to understand what's causing this and to fix it."
Answer: 2020.0

User story: "DMTN-108 summarises some possible security enhancements for LSST data taffic.    Perhaps the title can be more general about data paths.    Include the   * French connection   * general topology network diagram from the ops slides   * explain the inherent lack of security through out   * add section on satellites and the possibility of some subset of the data/sky being more sensitive and potentially concentrating on that ..   * make an up front summary with a few bullets about what could be done."
Answer: 161599.0

User story: "This is the first code piece in the decorrelation afterburner rewrite.    For helping the review, the whitening concept and the whitening kernel are demonstrated in DM-24316.     "
Answer: 34158.0

User story: "AP pipeline want to have order of visit processing processing to be stable, in particular association steps for one visit needs to wait until the same step for previous visit is finished. Adding this sort of dependency for quantum graph would be difficult. It may be easier to implement special scheduling logic while executing the graph instead. I want to explore how this can be done in current pipetask and try to make it scheduling more configurable/extensible. Some refactoring (that we always wanted to do) of the internals will probably be needed."
Answer: 24719.0

User story: "Stand up an environment that has an automated way to stand itself up.  This will be useful since we can test out the disaster recovery, bringup, and latest versions of all the software as a part of CI.  Hopefully at this point we can automate more than before."
Answer: 75061.0

User story: Do a "standard" reprocessing of HiTS2015 with ap_pipe using the latest stack. I do not plan to build new templates this time.
Answer: 24466.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: "Presently ts_sal salgenerator appears to find Python.h by using {{/include/python$PYTHON_BUILD_VERSION}}. This is a bit of a problem for several reasons:  * It assumes that /include exists  * It is a bit confusing as it's not clear what PYTHON_BUILD_VERSION is being used for.    I suggest offering a new env variable PYTHON_INCLUDE (or similar) that is the full path to the directory containing Python.h. I think it would be much clearer what the env variable was used for.    You could fall back to PYTHON_BUILD_VERSION if PYTHON_INCLUDE was not defined, for backwards compatibility.    Two more small requests to consider (in an attempt to rationalize the env vars):  * Rename LSST_SDK_INSTALL to something a bit clearer. It appears to be the root directory of ts_sal, so perhaps TS_SAL_ROOT? If you do that then do you need SAL_HOME? It is a known subdirectory of ts_sal.  * Move your bin scripts (such as salgenerator) to the bin/ directory. That's what it's there for. Then we just have to get ts_sal/bin on our PATH and they can be found. The current location is surprising and deeply buried. At that point you can probably lose SAL_DIR."
Answer: 33296.0

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

User story: "Allow the connection message (GUI or DDS) in hexapod PXI code."
Answer: 50784.0

User story: "Ticket related to work done for documentation plan.         Conducted one-on-one meetings with half of software team.    Had several discussions with [~<USER> about moving forward.    Made notes about our discussions."
Answer: 9982.0

User story: "Tasks done:   * makeSkyMap   * singleFrameDriver   * jointcal   * skyCorrection   * coaddDriver   * multiBandDriver   * forcedPhotCcd   * visitAnalysis   * compareVisitAnalysis   * coaddAnalysis   * colorAnalysis   * compareCoaddAnalysis   * matchVisits   * dispatch_verify_colorAnalysis"
Answer: 50319.0

User story: "I've struggled with how best to deal with Database.sync, an important operation that needs to start and commit its own transaction in order to be safely concurrent.    -I had an idea for this while working on DM-15536 that should be explored: a sync operation could be a special context manager that could contain any number actual row syncs and other vanilla modification queries.-    Since DM-24432 added table locking, that (and another UPSERT variant that does nothing on conflict) provides a much better solution: we can just make sync work inside transactions like any other Database method."
Answer: 286183.0

User story: "We only need one reaper globally, but we should certainly Helm/Argo it."
Answer: 30190.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: When converting gen2 repositories to gen3 we currently default to using symlink mode. This means that in-place conversions can't work and also means that a user can't convert to an S3 bucket.    I think we need a couple of changes that would help a lot with the right decision being made:    # Add a new "link" option that tries a hardlink and falls back to symlink  # Add an auto mode to posix datastore that will check to see if the file is within the repository and use None if it is, else it will use "link".  # Make "auto" an alias for "copy" in S3 datastore.    With these changes the 2to3 conversion can use "auto" mode and that should do the right thing most of the time.
Answer: 4153.0

User story: "We currently have a few example efd notebooks.  These should be converted to use the modern utility classes and added to the list of CI'd notebooks.  Now that there is EFD data available from the EFD on int and visible from stable, this is now something we can do.    I would also like to promote the notebooks to the prod branch so that they show up automatically.  That may be thwarted by the fact that the correct data may not be available everywhere.    Note: We did not promote to prod on this ticket.  That will be handled in DM-24410."
Answer: 8311.0

User story: Following DM-20556, the "Plotting Demo Notebook" has a few small API changes that aren't reflected in the examples there. It also shows only DECam example plots while the plots work for HSC as well. This ticket is to update the plotting demo notebook to be an accurate and helpful set of examples for users who want to make plots from the APDB.
Answer: 14577.0

User story: "When a component is being requested from a dataset type, it is entirely possible for that particular dataset that the component will be None. At the moment we do not allow that and it is an error to return None because the python types do not match.    Change datastore such that if a component is being requested then None is an acceptable value.  Once this is supported fix the ingest test in obs_base that skips Wcs component test."
Answer: 29089.0

User story: "Something in the fakes addition code is causing deblending to have some memory issues. This is potentially because the fakes are being put into the dodgy areas of the images and then having giant footprints. Change it so fakes don't get put into these areas and then see if that fixes the problem. "
Answer: 30391.0

User story: "In DM-24285 we made reading components from exposures very efficient but inadvertently broke reading of components from raw files because the API was changed. Nothing in lsst_distrib or lsst_ci noticed and it wasn't until ci_hsc_gen2 that the breakage was discovered.    In that test we showed that reading raw.wcs does not give you the same thing as reading the raw and then calling {{getWcs}}.  This is because the previous implementation did a full read and component extraction but now components are all handled by ExposureFitsReader."
Answer: 228.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'm not sure if this is a duplicate (I could not find it in a quick search) but...    please add:  * ts_hexrotcomm  * ts_simactuators  * ts_config_*    to future T&S development Docker images. These are used by a many other packages."
Answer: 139434.0

User story: "Add a unit test for the mock controller to ts_MTMount"
Answer: 8746.0

User story: "Add quickLookExp exposure type to datasets and set template of LSST."
Answer: 18805.0

User story: "It turns out that the TCS sequence ID field is only used by the Operation Manager communicating with the PXI. It is not used by the CSC, HHD and EUI connecting to the Operation Manager. It also strips that field from replies before sending them to the CSC, HHD or EUI.    Update ts_MTMount accordingly.    Also update the mirror cover open/close commands to the sequence provided by Alberto:    To deploy the mirror covers (protect the mirror):  * Deploy mirror cover locking pins (1506 = MCL_MOVE_ALL, drive=-1, on=1)  * Deploy mirror covers (905 = MC_OPEN, drive=-1)  To retract the mirror covers (for observing):  * Retract mirror covers (906 = MC_CLOSE, drive=-1)  * Retract mirror cover locking pins (1506 = MCL_MOVE_ALL, drive=-1, on=0  "
Answer: 8669.0

User story: "This PR has been made by a GSoc student: [https://github.com/lsst/qserv-operator/pull/7]"
Answer: 8418.0

User story: Make the butler command in daf_butler able to call the register command in obs_base (at python/lsst/obs/base/instrument.py).    To do this, when obs_base is setup, it should add a colon separated list of CLI python code modules or functions. For example set it to {{lsst.obs.base.cli}}.    Then in butler command itself do something like:  {code:java}  for module in os.environ["DAF_BUTLER_PLUGINS"].split(":"):   blah = doImport(cls) {code}  and maybe have the imported class import the subcommands to click somehow   ...it may help to be explicit and have the env var contain the actual command function (so lsst.obs.base.cli.register or somesuch). 
Answer: 27178.0

User story: "Per DM-24324, we are sending calexp, rather than coadd, cutouts in our alert packets. Please use the latter. This might take some thought about how to load the data in an efficient way."
Answer: 127398.0

User story: "On DM-24234 we started creating alert packets from pipeline code, but we included Rubin-native Exposure objects, which have obscure/undocumented/hard-to-parse metadata. For portability reasons, replace them with Astropy [CCDData|https://docs.astropy.org/en/stable/api/astropy.nddata.CCDData.html#astropy.nddata.CCDData] objects instead.    (We should make sure this is approved by RFC before we actually do it.)"
Answer: 116362.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> has some code in a notebook which will format pipeline outputs as alert packets in Avro format. Incorporate that into the AP system (probably as the final step in diaPipe).    For this first version, considerations are:    - What's the appropriate interface to the pipeline?  - It's fine to spew alerts to the filesystem for now; we'll worry about hooking them up to alert distribution sometime later.  - If we don't have easy access to templates in memory, use diffim/calexp for the cutouts.  - Just use Rubin-native Exposure objects as cutouts; we'll worry about using some more portable format on another ticket."
Answer: 60431.0

User story: "Document the exact steps for bootstrapping LSP on a new cluster from scratch. The Roundtable bootstrap documentation should have a lot of these details, but not all of the apps are available in the lsp-deploy repository and we haven't tested it."
Answer: 59008.0

User story: "[~<USER> and I negotiated how the CCS image writer can trigger transfers of pixel images and metadata to other systems.  Add a write-up of the result to DMTN-143.    Also clarify DMTN-143 by highlighting the action plan rather than the reasoning behind it."
Answer: 15833.0

User story: "Provide a /logout URL that logs you out of all auth cookies and then redirects the user to the landing page."
Answer: 31506.0

User story: "The new parquet source tables should be added to the HSC repo in {{testdata_jointcal}}, which is necessary for testing this new feature in {{fgcmcal}}."
Answer: 90571.0

User story: "With new parquet source tables soon to be added to production, these should be supported in {{fgcmcal}} which should greatly speed up the i/o part of the operations.  The plan is that new methods will be written in {{fgcmBuildStarsTask}} that will make use of the source tables, meaning there will be some slight code duplication.  However, since the old method of reading source catalog fits files will be deprecated by this ticket, when the deprecation period is complete the old code can be removed much more cleanly."
Answer: 130943.0

User story: "[~<USER> points out that {{ExposureFitsReader}}, though not ideal as an internal implementation class, can be used to further optimize Gen2 Butler retrievals.  This also prepares the way for Gen3, which will have full access to the features of that class."
Answer: 2426.0

User story: "Create notebook to demonstrate the following:  * What happens to frequency spectrum in case of DFT padding?  * What does the noise whitening correction look like in pixel space?  * Demonstrate whether there is any numerical effect of low-high frequency swapping before doing the FFT/IFFT.  "
Answer: 249054.0

User story: "Christine needs to be able to trace users through the logging stream.  Figure out how to make that happen, maybe with structlog?"
Answer: 57796.0

User story: "Implementation ticket for RFC-683"
Answer: 15589.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 the great refactoring, all the image-manipulation tools switched to using a common configuration object...but the environment variables they set don't reflect that."
Answer: 1596.0

User story: "This is to apply updates to latiss_cwfs_align based on verification work. Also provide example notebooks on how to perform CWFS analysis."
Answer: 54758.0

User story: "JavaScript sites will generate multiple login redirects that will not succeed, which can cause excessive upstream requests. It can also break CSRF handling by replacing the CSRF token in the session before the actual login attempt succeeds.    Fix both of these by reusing a state attribute if it hasn't expired and rate-limiting login redirects. (Or possibly detect JavaScript calls and don't redirect those?)"
Answer: 37436.0

User story: "When planning PipelineTask conversion of FGCM, we recognized a Gen3-converted testdata_jointcal repo as a useful prerequisite (presumably the same is also true for a PipelineTask conversion of jointcal).    I'm not familiar enough with the structure of that package to have a plan in mind for how to organize things (or whether to try to convert the HSC data separately and before trying to convert the DECam data - I assume we'll defer the CFHT regardless).  Given that there is data from multiple instruments here it could also be an interesting test of making multi-instrument Gen3 repos, but we shouldn't let that block getting something usable for PipelineTask testing.  I'm hoping [~<USER> (who now knows both about this data and gen2to3) might have some thoughts on those points.    [~<USER>, if we can get this scheduled to be done by someone more familiar with the conversion code this month, that will open up [~<USER> to work on the actual FGCM conversion next month.  I don't _think_ it should be a lot of work, but again, I'm less knowledgeable about this package than others."
Answer: 110158.0

User story: "Fitsfile created by CCForwarder has wrong pixel data."
Answer: 67553.0

User story: "The purpose of this ticket is to start work on the front-end for the reboot of [www.lsst.io|http://www.lsst.io/] by initializing a React/Gatsby.js app. We believe that Gatsby is the most appropriate front-end framework because it renders static pages that will deploy well on LSST the Docs. Gatsby will also let us create curated documentation features by using GitHub as a CMS/collaboration platform. React works well with the Algolia Instantsearch UI framework (Algolia is the software-as-a-service that the Ook app, see DM-24241, is populating with searchable records). Specific goals for this ticket are:   * Startup the Gatsby project   * Add code linting and formatting hooks   * Set up CSS build pipeline (global styles + styled-components?)   * Set up GitHub Actions-based CI.   * Create a demo page that integrates with Instantsearch.js"
Answer: 28203.0

User story: "CCArchiver is now creating FITS files from pixels read from the DAQ. The integrity of the pixels and the headers needs to be assessed. "
Answer: 8127.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "With guidance from [~<USER>, extract satellite trails from 4 g-band DECam visits (one including DARKSAT) and measure brightness to better understand how they will affect LSST.    Processing this data was done as described in DM-17538."
Answer: 89327.0

User story: "Review the configuration manager by MOOG. This is a LabVIEW project."
Answer: 8180.0

User story: "After some discussion we have decided that it might be better for datastore to be in charge of assembly/disassembly of datasets. Currently registry creates 7 rows per raw with almost none of those components being relevant. We did it this way to allow pipelines to specify components directly. We very rarely want to do this though and it would be more efficient in database storage to have a single row for a dataset in registry and move [dis]assembly to the datastore layer. Then we can instead write a single row if we do not disassemble and multiple rows if we do disassemble (and no row at all for components that were not present).  This is similar to the original implementation of datastore.    This ticket is to check that the approach is feasible and also whether it can be implemented independently of registry to allow us to experiment with both approaches in parallel."
Answer: 41604.0

User story: "Scheduled a separate zoom meeting with Rucio folks and others to discuss various Rucio topics and Data Backbone needs.  "
Answer: 3.0

User story: "Considering that Network verification elements are already included in LDM-732, we need to find the right granularity to have easy to manage documents."
Answer: 180446.0

User story: "There's existing code in the stack to apply proper motions and parallaxes from the reference catalog. Find it, dust it off, and get it going in Jointcal. It may require some modification. If it requires substantial overhauls (e.g. rewriting completely because it's too slow), let's make a new ticket to capture that.    For now, we will correct the reference catalog to the mean epoch of the loaded data."
Answer: 138122.0

User story: "Perhaps include the usage table from [PSTN-003.lsst.io|http://pstn-003.lsst.io/]  perhaps one of the sizing cost tables - With a ref to DMTN-135 ..     We could also add the Check LIst for iDacs .. discussed in CEC meeting.."
Answer: 7201.0

User story: "I need to read and understand more in depth thermal papers send by Neil."
Answer: 8705.0

User story: "SALSubsystems.xml lists the FiberSpectrograph instances as MTBlue, MTRed and ATBroad. [~<USER> would like the prefixes removed, to avoid misleading people, as the spectrographs may be moved around at need."
Answer: 1103.0

User story: "The test assumes it will be run in a particular way (with certain specific functions invoked).  This is subject to change, and apparently it does change with newer versions of pytest.  Remove the tester-specific lines."
Answer: 607.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: "Eric's concept for the alert stream in a box is something like:    - A Docker container  - Which can be pointed to an external directory of alerts on disk  - Which it will read in, then send out over a Kafka stream to some recipients, at a realistic rate and cadence (ie, 10,000 alerts every ~37 seconds).    Write a design document which describes what this will actually consist of. That should probably be formatted as a DMTN (but you can also use Confluence if you find that easier/more convenient)."
Answer: 11807.0

User story: "Repurpose this ticket for something else as there was already one created DM-24358"
Answer: 54577.0

User story: "As proposed in DMTN-082 the LSP users are generally interested in telemetry data at a frequency closer to the cadence of the observations.     The original proposal is that “all telemetry topics sampled with a frequency higher than 1Hz are (1) downsampled at 1Hz and (2) aggregated to 1Hz using general statistics like min, max, mean, median stdev”.     Commands and event topics should not be aggregated as they are typically low-frequency and can be read directly from the raw EFD data sources.    Another aspect of the aggregation is to resample the telemetry topics in a regular time grid to make it easier to correlate them.    The aggregator will produce a new set of aggregated telemetry topics in Kafka that can be consumed by a connector and stored in a specific format. In another ticket we'll use the parquet data format to store the aggregated topics.     In this ticket, we'll investigate and evaluate [Faust|https://faust.readthedocs.io/en/latest/], a Python asyncio stream processing library. Faust supports Avro serialization and multiple instances of a Faust worker can be started independently to distribute stream processing across nodes or CPU cores.    "
Answer: 93812.0

User story: "Work with Tiago to create (or flush out) the repo and development structures for developing notebooks, observing utilities, and scripts etc."
Answer: 21850.0

User story: "Add an HSC Gen 3 dataset to the {{scipipe/ap_verify}} Jenkins job. The job should already be designed to let us plug in more datasets, so the main work would be specifying a Gen 3 run (requires adding an internal flag to the Jenkins job?) and working with Groovy."
Answer: 204454.0

User story: "Produce a Gen3 version of existing {{ap_verify}} datasets, including the dataset compiled in DM-24259."
Answer: 62289.0

User story: "Create a “stub” dataset for testing HSC Gen2 processing in CI. The contents of this do not have to be (indeed, are not expected to be) scientifically meaningful: we are aiming for a smoke test to make sure nothing throws an exception, rather than outputs for further analysis.    Please check with [~<USER>, who might already have compiled some useful data for testing."
Answer: 39086.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: "Continue update of software interface documentation, to make consistent with the new partition of development of control software by Rubin Observatory and EIE contractor, as we continue to settle on details. This is continuation of DM-23906"
Answer: 18616.0

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

User story: "As DM-23430, but for all other bands."
Answer: 155923.0

User story: "As DM-23429, but for all bands (not just G)."
Answer: 24451.0

User story: "The recent large runs of {{fgcmcal}} on HSC data have shown that (a) in certain use cases the startup time is a factor of a few slower than it could/should be, and (b) certain files can be checkpointed to allow faster restart in case of transient file system failures, out of memory issues, etc.  I have a branch {{/u/<USER>fasterstart}} that implements these changes and will be cleaned up."
Answer: 15243.0

User story: "Bug as determined on DM-23944."
Answer: 20116.0

User story: "Plug in electrometer and test it with reviewed CSC."
Answer: 34090.0

User story: "[~<USER> ran the butler config validation on the ci_hsc_gen3 output repo and got the following report:  {code}  Template failure with key 'default': Template '{run:/}/{datasetType}.{component:?}/{tract:?}/{patch:?}/{label:?}/{abstract_filter:?}/{subfilter:?}/{physical_filter:?}/{visit:?}/{datasetType}_{component:?}_{tract:?}_{patch:?}_{label:?}_{abstract_filter:?}_{physical_filter:?}_{calibration_label:?}_{visit:?}_{exposure:?}_{detector:?}_{instrument:?}_{skymap:?}_{skypix:?}_{run}' is inconsistent with DatasetType(ps1_pv3_3pi_20170110, {htm7}, SimpleCatalog): {'exposure', 'patch', 'skypix', 'abstract_filter', 'tract', 'label', 'physical_filter', 'detector', 'instrument', 'calibration_label', 'skymap', 'subfilter', 'visit'} is not a superset of {'htm7'}.  {code}    Fix the template."
Answer: 192571.0

User story: "Get the science monkey configurable to run on int and deploy with kubernetes"
Answer: 122590.0

User story: "write a command line tool using the Click package for the scripts in daf_butler:   dumpButlerConfig.py    makeButlerRepo.py    validateButlerConfiguration.py   following Jim's API wishes in his document at [https://paper.dropbox.com/doc/Gen3-Middleware-Command-Line-Tools-NBYZOpQqz50D0v1nqfJrI]         before this is closed, fix any problems with the replaced scripts in ci_hsc_gen2 and ci_hsc_gen3.     When it is closed, write a CLO post about the removed scripts and how to do those things in the new CLI tool.     "
Answer: 31837.0

User story: "Argo Workflows >=2.5 is very different from earlier versions, and our inability to move yet is making a lot of things increasingly fragile as the Python support classes move on without us."
Answer: 122400.0

User story: "The purpose of this ticket is to add the capability to reduce technote documents (both reStructuredText and LaTeX [Lander-deployed]) and index those records into Algolia."
Answer: 66162.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: "M1M3 controller lack (almost any?) parameter checking. At least running M1M3 start_commander without proper Default (configuration name) will throw an error on m1m3 support. That needs to be rectified, verified and sensible messages returned."
Answer: 60626.0

User story: "Review the porposed solution (Tekniker) to replace the use of NI Softmotion Axis  calls with substitute/direct calls to OpenPLC equivalents. Assist engineers in  establishing a local TMA controller simulation environment with PXI capable PCs'"
Answer: 22855.0

User story: "Assist the EAS contractor with building and testing the software against latest  SAL and DDS versions, rpi firmware upgrades, XML definition"
Answer: 11554.0

User story: "Assist SAL 4.1 release CI process with any required tweaks anf fixes revealed during CI  testing "
Answer: 20169.0

User story: "Review the draft of LTS-162 v5:    [https://www.dropbox.com/s/zgoq9zmcqtogyyz/LTS-162_v5.docx?dl=0]"
Answer: 1584.0

User story: "Deploy more than one instance of DBB buffer managers on single, non-production machine but using separate buffers to verify if they can operate simultaneously without any interference.  "
Answer: 4014.0

User story: "This is the ticket to actually perform the switch to the conda environments based on the conda-forge channel as well as the conda compilers.    This involves a few changes across a few repos to fully implement. Those changes are equivalent to adding a new compiler and a new conda environment, since that is what we are doing.    * A rebase of all branches in DM-23835, a new conda test tag  * Small changes to ci-scripts (specifically ccutils for conda compiler)  * A final verification with ci jobs and stack demo  * Verification the tarballs work  * Updates to jenkins-dm-jobs (specifically the YAML configuration, and some jobs)  * A publishing of a new daily release with the new conda environment (including tarballs)    This change implicitly also means updating the versions of several third party packages, such as cfitsio."
Answer: 73628.0

User story: "Deploy DBB buffer managers for 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: 14369.0

User story: "Deploy DBB buffer managers for Auxtel on NCSA test stand and verify they are working. This includes writing deployment-specific documentation for those in charge of operating the service.  "
Answer: 2596.0

User story: "get electronics working, create a repo for ts_pressureSensor, start work on CSC"
Answer: 79.0

User story: "Task to cover the work to release the next version of XML."
Answer: 12954.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 per DM-23044, ptc.py from cp_pipe is now able to persist different types of linearizers. One of them is LookupTable (see linearizer.py in ip_isr), with, for an LSSTCam-type device, will have a shape of (#nAmps, #DN) --->(16, 2**18).  This table, along with necessary metadata, is saved as a yaml file.  However, reading this file (~38Mb for the file in the example below) again takes a very long time (~ 3 mins), which is not ideal:     {code:python}  import yaml  import timeit   file = "/project/shared/auxTel/rerun/<USER>PTC-auxTel2020MAR25-doLinearize-true/calibrations/linearizers/linearize-lut-det000_2020-03-27.yaml"    def read_yaml ():      with open(file, 'r') as f:          dataLU = yaml.load(f, Loader=yaml.Loader)      return   {code}  {code}  %%timeit -n2 -r3  read_yaml ()    3min 18s ± 4.11 s per loop (mean ± std. dev. of 3 runs, 2 loops each)  {code}      
Answer: 4616.0

User story: "With the evolution of the classes we use in ts_standardscript, it became clear that they would need a place of their own, instead of cohabitating with the scripts itself. This task is to move those classes out of ts_standardscripts into a new ts_observatory_control repository.      "
Answer: 32943.0

User story: "The CBP CI is broken. Figure out why it is broken and fix it."
Answer: 177668.0

User story: "The electrometer CSC needs a dockerfile for deployment. This story covers that work."
Answer: 13182.0

User story: "The LinearStage's substates should be NotMoving and Moving instead of having the Summary states repeat and a Moving substate."
Answer: 238048.0

User story: "Adapt AP testing methodology to work within Gen3 Butler.  This ticket had been created automatically Primavera ID: None"
Answer: 107692.0

User story: "Produce test set and scripting necssary to perform AP pipeline testing at scales of roughly 500 CCD/images.  This ticket had been created automatically Primavera ID: None"
Answer: 107690.0

User story: "Work to maintain, alter/expand configuration and deployed infrastructure for testing AP with the NCSA Test Stand.  This ticket had been created automatically Primavera ID: None"
Answer: 107688.0

User story: "Document build and deployment of HeaderService  This ticket had been created automatically Primavera ID: None"
Answer: 141492.0

User story: "Implement changes as required by updates warranted by behavior changes to other CSCs that the HeaderService relies on  This ticket had been created automatically Primavera ID: None"
Answer: 123188.0

User story: "Implement changes as required by updates of the Telescope & Site CSCs  This ticket had been created automatically Primavera ID: None"
Answer: 123181.0

User story: "Implement changes as required by updates to the CCamera's XML definition  This ticket had been created automatically Primavera ID: None"
Answer: 64726.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: "Redis is running as service on the native host. Create a new docker container that hosts this service, either by using an existing Redis container, or creating one.  This ticket had been created automatically Primavera ID: None"
Answer: 258413.0

User story: "RabbitMQ is running as service on the native host.  Create a new docker container that hosts this service, either by using an existing RabbitMQ container, or creating one.  This should include all necessary L1 queue and user definitions.  This ticket had been created automatically Primavera ID: None"
Answer: 258414.0

User story: "Obtain quotes for spare switches, and submit for purchase  This ticket had been created automatically Primavera ID: None"
Answer: 284512.0

User story: "To ensure the viability and stable operational capacity of the LSST DM infrastructure at NCSA,   This ticket had been created automatically Primavera ID: None"
Answer: 111537.0

User story: "Determine which ESXi licenses need renewed and obtain quotes for these renewals.  This ticket had been created automatically Primavera ID: None"
Answer: 287221.0

User story: "Write a recommendation document on how to best streamline services  This ticket had been created automatically Primavera ID: None"
Answer: 284513.0

User story: "Obtain quotes for hard drive spares needed for Dell and Lenovo nodes, and submit for purchase  This ticket had been created automatically Primavera ID: None"
Answer: 111537.0

User story: "Review and approval of plan from NCSA LSST Program Office, prior to hardware and license order  This ticket had been created automatically Primavera ID: None"
Answer: 284514.0

User story: "VMs offer additional reliability over bare metal where it can be arranged, this story is to generate the list and plan which machines can move to VM; method of migration; and downtime requirements  This ticket had been created automatically Primavera ID: None"
Answer: 284514.0

User story: "Prototype system capable of monitoring AuxTel data transfer and ingestion (DR is a stretch goal).  This ticket had been created automatically Primavera ID: None"
Answer: 264511.0

User story: "Produce a plan for file transfer monitor system  This ticket had been created automatically Primavera ID: None"
Answer: 264512.0

User story: "In order to set up file-transfer monitor system, need to understand the source(s) of truth available at the Observatory/Camera level, within the DBB, and DR.  Check into whether there are hooks in OCS/CCS that make this redundant (or need feedback from such a sysem).  This ticket had been created automatically Primavera ID: None"
Answer: 264512.0

User story: "Install RabbitMQ container on Summit  This ticket had been created automatically Primavera ID: None"
Answer: 141374.0

User story: "Install Redis container on Summit  This ticket had been created automatically Primavera ID: None"
Answer: 141374.0

User story: "Install CCForwarder on summit  This ticket had been created automatically Primavera ID: None"
Answer: 101634.0