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: "The way that [~<USER> split the two config/ingest.py retargeted *then* loaded the ts8 common configs.  This meant that the ingest thought it was dealing with ts8 not e.g. ts8e2v  "
Answer: 10.0

User story: "The DRP team has developed a system for converting pipeline outputs to something resembling the LSST Science Data Model (hence, “SDMization”).    Can we adopt the same system in AP?    - Look at the work that's been done on DRP;  - If necessary, have a chat with [~<USER> and/or [~<USER> (maybe include [~<USER> and/or [~<USER> in that conversation too);  - Come up with a recommendation — is this something we should spend time on? What's the suggested approach"
Answer: 30502.0

User story: "After the new matcher (Pessimistic B) became default on DM-14857, the astrometric metrics recorded on SQuaSH regressed (for both HSC and CFHT). Reproduce this locally and understand what happened. Fix if this is a matcher problem; if it's a validate_drp problem, ticket that for future work."
Answer: 20477.0

User story: "As developed in DM-17549."
Answer: 10392.0

User story: "Each alert packet should record the version of the schema which was used to generate it.    Also include some instructions for backwards compatibility."
Answer: 141885.0

User story: "Current HSC donut fits leave residuals that are coherent from donut to donut (see [donutGoodnessOfFit-0069030-046.png|https://dmtn-064.lsst.io/_static/donutGoodnessOfFit-0069030-046.png] and [donutStampResid-0069030.png|https://dmtn-064.lsst.io/_static/donutStampResid-0069030.png] for example).  I'd like to try and greatly increase the number of fit parameters in order to reduce the residuals to being consistent with noise and see how different the inferred in-focus optical PSFs are.  This is probably only feasible for a small number of donuts, but that should still be interesting.  Probably choosing a few intra/extra-focal donut pairs around the FoV would be best.         I think probably the best way to attack this would be to implement the Fienup hybrid input-output algorithm, which is an iterative procedure yielding an image of the wavefront, rather than a forward model fit."
Answer: 199079.0

User story: "There is useful documentation in README files in obs_lsst that needs to be integrated into the sphinx documentation."
Answer: 2918.0

User story: "Converting to pipeline tasks introduced a bug in runDataRef in MeasureCoaddSourcesTask, fix the bug."
Answer: 897.0

User story: "This a timeboxed ticket, on the assumption that making calibration products is “easy”.    When we get beyond about 2 days of work, we should file more tickets to describe the issues that are being encountered and what we're doing to resolve them"
Answer: 747782.0

User story: "If restrict lab/restrict dask are true, further filter node list in prepuller."
Answer: 132.0

User story: "As part of DM-16406 [~<USER> identified systematic correlations between the lightcurves of various HiTS sources.  This ticket is to investigate the cause of that correlation."
Answer: 93514.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  {{confluent-kafka}} chart needs some custom config that:    1) increases the broker's disk to 15G and configures a retention policy for the topic offsets and the kafka logs of 24h in {{cp-kafka}}. That will avoid filling up the disks as seen during the SAL Mock experiment    2) uses a specific docker image for {{cp-kafka-connect}} which adds the Landoop InfluxDB Sink connector and overrides the {{plugin.path}} configuration.  Our implementation uses the Landoop InfluxDB Sink Connector to connect kafka and InfluxDB, see SQR-029 for details.    3) sync our cp-helm-chart fork with recent changes in the [upstream repo|https://github.com/confluentinc/cp-helm-charts/commits/master/values.yaml]. That is required for 2.  "
Answer: 23446.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: "Qserv czar is missing a length check at message table insertion; a too long error message can cause message insertion failure.  This may result in an empty message table, leading the czar to conclude that the query succeeded and subsequently attempt to access a non-existent result table."
Answer: 78.0

User story: Use the simulations generated in DM-17527 to build a {{DcrModel}}. If cuts are made to exclude observations with poor seeing, that should be recorded. Use the {{DcrModel}} to generate templates for a second "year" of simulated observations. Since these are simulations with only static sources, a good metric will be to compare plots of the number of detections in the image differences, since any detection is a false detection. It will be useful to also build a coadd for the "year 1" data using {{CompareWarpAssembleCoadd}} as a refernce.    The result of this ticket will be a set of plots comparing the number of false detections under different conditions, and using the current version of {{DcrAssembleCoaddTask}} or {{CompareWarpAssembleCoaddTask}}. A more detailed tech note will follow on a later ticket.
Answer: 86242.0

User story: "Generate two test data sets of simulated data using {{StarFast}}: one with constant seeing but using a range of observing conditions (airmass etc..) taken from OpSim, a second using the OpSim observing conditions including variable seeing.   * Simulate ~1 year of observations   * g-band for now   * Assume 16-20 observations of the same field for g-band in the first year"
Answer: 45789.0

User story: "Need to develop tests that fully exercise the WLS CSC through SAL, where we send it a message or command through SAL, and then look for an event on SAL as a result. "
Answer: 45928.0

User story: "There are issues with Large cookies being handled by nginx. nginx is currently omitting one of the {{Set-Cookie}} headers, which is corrupting a cookie which is split for size reasons at 4kB.         This ticket is for implementing server-side cookie storage and issuing small cookies to the client in oauth2_proxy"
Answer: 46030.0

User story: "Take what you learned on DM-16409 and turn it into a set of notes on the ip_diffim codebase — what are the key options? How is the code structured?    This shouldn't attempt to be comprehensive, user focused documentation: use it to draw out the key themes and options that you think we should schedule time to investigate over the next several months, and record what you wish you'd known when you were getting started a few months ago."
Answer: 117077.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: "Review of Besalco contract documents..."
Answer: 1002.0

User story: "We use the terraform-provider-influxdb to create the database and the retention policy for the EFD database in InfluxDB.      "
Answer: 23197.0

User story: "Attempt to reduce Python env complexity in JL build."
Answer: 1421.0

User story: "The ATMCS simulator has some issues that need addressing:    * Updated XML, including M3 telemetry  * Motors should be enabled by standby->disabled and vice versa (the current logic is more complicated). That said, we are discussing whether there is some way to only enable a rotator if it is needed, in order to reduce heat load.  * Update limits based on current knowledge  * Output azimuth raw encoder counts in range [0, 360]*resolution and offset encoders by appropriate amounts when there are multiple encoders per axis  * Do not output m3InPosition and probably not m3PortSelected ([~<USER>?) until the setInstrumentPort command is received.  * Enable tests that were accidentally left disabled"
Answer: 30263.0

User story: "Work out details of CAP-9"
Answer: 70702.0

User story: "Spot check some epics marked done and make sure I can find deliverables."
Answer: 11496.0

User story: "Go through risks assign to CAMS and also do review ahead of board .."
Answer: 9861.0

User story: "The geometric approach for producing PSFs from obscuration+wavefront is significantly faster than using Fourier optics, but is more approximate.  I think that approximation should actually be pretty good though for out-of-focus donuts.  This issue would be to run the donut fitting code over a few dozen donuts (maybe with differing degrees of obscuration) and compare the results to see if we can switch to the faster approximate code, and maybe use that increased speed to justify investigating higher order Zernike coefficients."
Answer: 93784.0

User story: "Use batoid to predict the fully-aligned HSC wavefront model and compare that to the wavefront model obtained from donut data."
Answer: 93800.0

User story: "I suspect that the dominant contributors to wavefront distortion coming from tilts and decenters are constant coma (i.e., constant over the field-of-view) and linear astigmatism.  See if this is the case for simple alignment problems like tilts and decenters using batoid.    Note, even if these are indeed the only significant contributions to wavefront perturbations above, there may be additional types of optical perturbations in real data; e.g., mirror pinching.  So while still interesting, I wouldn't necessarily be prepared to advocate limiting the full wavefront model to only constant coma and linear astigmatism."
Answer: 93805.0

User story: "I suspect from playing with LSST numbers that only differences in Z4 with focal plane height variations (chip gaps) are actually significant for HSC.  Check using batoid that this is the case.  If true, then we shouldn't model Z5+ chip-level dependencies in the full wavefront model."
Answer: 93810.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: "Populate topics and schemas needed for to transform MTM1M3 topics from the SAL into the DM-EFD demo.    Also deploy the transformer app needed for the MTM1M3 transformations."
Answer: 109.0

User story: "We've just encountered a problem [~<USER> and I discussed back in the SuperTask WG but haven't yet implemented a solution for: it's totally normal for {{MakeWarpTask}} to not write some of its expected outputs because there didn't turn out to be an overlap between an input visit and the requested patch.  That of course makes the as-executed QuantumGraph differ from the predicted one, and that breaks things.    While we don't yet need a solution that results in an empty/sentinal file being written, we should try to find one that could at least be expanded to do that in the future as that may be useful/necessary for addressing this problem in a Pegasus-based executor."
Answer: 369176.0

User story: "[~<USER> reports that trying to build a single QuantumGraph for all of the PipelineTasks in ci_hsc runs into SQLite's hard-coded maximum of 64 joins a single query.  I can think of several ways to avoid this, many involving temporary tables (I know those work differently in Oracle; I think my ideas are compatible with that).    For the demo we'll plan on just running the pipelines in three stages, for which QuantumGraph generation works fine.  If everything else is going extremely well early in the week I may take a stab at resolving this, too."
Answer: 12060.0

User story: "Running PipelineTasks with ctrl_mpexec with -j can lead to SQLite errors about the database being locked.  It's unclear whether it's just not blocking long enough or not blocking at all, and also unclear whether we need to fix this by adding our own blocking or somehow informing SQLAlchemy or SQLite to do it.    (It's also possible we do have a genuine deadlock bug, but I doubt it.)"
Answer: 4351.0

User story: "[~<USER> reports that some modifications to the dimensions used by DatasetTypes in MakeWarpTask were necessary to get full QuantumGraph generation working, in that some dimensions that should have automatically been included as dependencies (e.g. Instrument) needed to be added explicitly.    While the conventions on whether to specify dimensions minimally or maximally are TBD, it should be impossible to get incorrect behavior, if we expand those dimensions as soon as a Registry is available."
Answer: 222292.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 Gen3 formatter class for HSC raw data doesn't call {{setFilter}} on the returned {{Exposure}}, which is a problem for downstream processing.  To fix that, we need to:   * add a {{makeFilter}} to {{FitsRawExposureFormatterBase}} in daf_butler, similar to the existing {{makeWcs}} and {{makeVisitInfo}} (including using it in the base class {{readInfoComponent}}.   * implement {{makeFilter}} in obs_subaru appropriately.    We'll probably have to call the {{afw.image.Filter}} constructor with {{force=True}} to try to avoid mucking with the global variables (and hope no one else does); a better solution will have to wait for RFC-541."
Answer: 1475.0

User story: "Running PipelineTasks end to end revealed some issues that were not found which each task was run individually against a gen3 repo created from a ci_hsc run. This ticket will fix all those issues."
Answer: 3964.0

User story: "Implement Registry.dissociate as well as a way to remove all Datasets from one or more Collections."
Answer: 18741.0

User story: "The goal of this ticket is to take a first pass at identifying defects identified on TS8 & AuxTel data.    Specifically, working on the LSST Science Platform (nb.lsst.io):    * Make sure you have access to flats & darks from TS8 and AuxTel;  * Check that the cosmic rays have been removed;  * Experiment with detection code to identify n-sigma defects (both positive and negative) (this is DM-19334).  * Critically examine the results of that detection code. File blocking tickets on this one to investigate anything which looks suspicious (the first one of these is DM-19335).  * Work through blocking tickets, until all the suspicions are explained.  * Job done!    Success criteria here are just to be able to identify visually-convincing defects in a notebook; worrying about appropriate formats to persist this information is out of scope for now."
Answer: 360193.0

User story: "DM-16467 added some Python and bash scripts that add brighter-fatter kernel and defect datasets to a Gen3 repo.  These use direct SQL calls instead of the Registry API, and have been broken by changes on DM-16227.  This ticket will move that work into the {{daf.butler.Instrument}} class and its obs_* package specializations, allowing it to be done automatically by the {{gen2convert}} tool (in addition to fixing the breakage, of course).    Coming up with a new, consistent-across-obs-packages way to manage human-curated source for these datasets is definitely out of scope right now, but this might provide an example of how the Butler side of that might look to those who do design that."
Answer: 4370.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: "Write an external script utilizing the scriptqueue BaseScript class that utilizes two linear stages which are at right angles. The TunableLaser will propagate at a wavelength or wavelength ranges. The linear stages will then move in step increments as the laser is propagating. The electrometer will then be read from as each increments occurs. The data from each CSC will then be put into a data file. Then a plot(not part of script) will be generated from the resulting data.    The idea is to use test-driven development to ensure that a. unit tests are written and b. that code logic is good. Unit tests using CSCs have been written using a Harness which wraps certain calls in mocks to ensure that only consistent software logic is being used.    The task ultimately became a part of Nick's visit as outlined by dm-17694 and dm-17943. Because of some issues with SAL and the private network along with some weird CSC. This task produced an early version of the script without the laser but is configurable to run in such a manner with or without the laser as part of the script."
Answer: 155452.0

User story: "Write the self-evaluation in Ultipro for the 2018 performance evaluation."
Answer: 14191.0

User story: "Write the self-evaluation in Ultipro for the 2018 performance evaluation."
Answer: 14028.0

User story: "Write the self-evaluation in Ultipro for the 2018 performance evaluation."
Answer: 6995.0

User story: "Write the self-evaluation in Ultipro for the 2018 performance evaluation."
Answer: 14029.0

User story: "Write the self-evaluation in Ultipro for the 2018 performance evaluation."
Answer: 14015.0

User story: "Write the self-evaluation in Ultipro for the 2018 performance evaluation."
Answer: 9898.0

User story: "Write the self-evaluation in Ultipro for the 2018 performance evaluation."
Answer: 14043.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: "Reporting lines and responsibilities fro Frossie as LSP CAM need to be properly outlined and agreed."
Answer: 9813.0

User story: "From the query monkey it seems like there is some kind of problem where the TAP service connection pool to qserv can get stuck:         [2] errors in a row. Running [SELECT 'monkey', ra, decl FROM wise_00.allwise_p3as_mep WHERE CONTAINS(POINT('ICRS', ra, decl), BOX('ICRS', 295.0426569335857, 79.31794246418082, 0.09614271869047619, 0.9002164336445476)) = 1] threw [PoolExhaustedException: [http-nio-8080-exec-431] Timeout: Pool empty. Unable to fetch a connection in 20 seconds, none available[size:10; busy:10; idle:0; lastwait:20000].]         I've saved the log from the TAP service and restarted it to get things going again.  This might be some kind of misconfiguration of the tomcat jdbc pool."
Answer: 8638.0

User story: "Continuation from meeting on 1/16/19 (DM-17229).     See minutes in the comments                   "
Answer: 36.0

User story: "DM-17228 changed the visit numbering.  Therefore all repos in {{/datasets/ts8/}} need to be refreshed. New sqlite registries need to be made. "
Answer: 7263.0

User story: Add to https://sqr-029.lsst.io:   * Write 2.1 The Confluent Platform   * Add a new section between "Deploying Confluent Kafka and InfluxData" and "Connecting Kafka and InfluxDB" that talks about Avro schemas and the Python transformer.
Answer: 6033.0

User story: "Once RFC-569 is adopted and obs_lsst is added to lsst_distrib, the sphinx build in pipelines.lsst.io has to be modified to include obs_lsst."
Answer: 17632.0

User story: "Modify MultiProFit's COSMOS galaxy fitting code to do simultaneous fitting of HSC images in multiple bands (gri to start), verify that it works and compare (roughly) the runtime cost vs single-band fits"
Answer: 50740.0

User story: "Currently the parser+Intermediate representation unit tests depend on the old (antlr2) parser to generate IR that gets compared with the IR generated by the new (antlr4) parser.    We need to stop using the antlr2-generated IR in unit tests, and instead have a concise, readable, way to generate a specific IR tree to be used as the 'expected' value for comparison with the (new) parser-generated IR tree.    The reason for this is we have reached a point where we want the IR generated by the 2 parsers for the same query to diverge (for example so we can use a plugin to put the where clause into disjunctive normal form instead of relying on the parser to build it that way). This allows the parser-generated IR to reflect the query in as natural & accurate a way as possible, and any needed transformations can be applied (selectively, even) later on."
Answer: 7271.0

User story: "Collect, record, and verify financial data for the LSST Data Facility. Deliverable consists of a monthly financial report delivered to the Project Controls Specialist."
Answer: 105200.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: "Collect, record, and verify financial data for the LSST Data Facility. Deliverable consists of a monthly financial report delivered to the Project Controls Specialist."
Answer: 54735.0

User story: "Collect, record, and verify financial data for the LSST Data Facility. Deliverable consists of a monthly financial report delivered to the Project Controls Specialist."
Answer: 8915.0

User story: "Implement new command group in {{kafkaefd}} to create the connector configuration and upload to the {{cp-kafka-connect}} REST API.    See  [https://docs.confluent.io/3.2.0/connect/managing.html]    Then create a k8s deployment that executes the {{kafkaefd}} command."
Answer: 44904.0

User story: "PV/PVC need to be renamed on qserv-cluster because of new czar-0 pod."
Answer: 44150.0

User story: "Implements part of RFC-557."
Answer: 11165.0

User story: "@chb Would it be possible to deploy the historical DAX services lsst-lsp-stable? Loi and Brian are working on authentication issues at lsst-lsp-int, and suit there might not be available for some time. We have deployed suit at lsst-lsp-stable, but it seems that the DAX services are not there."
Answer: 1347.0

User story: "`https://lsst-lspdev.ncsa.illinois.edu/tap/availability` returns a note `DataSource is not usable: jdbc/tapuser, cause: java.sql.SQLSyntaxErrorException: Table 'TAP_SCHEMA.SCHEMAS11' doesn't exist`"
Answer: 9910.0

User story: "PhotoCalTask passes a config object as the first argument to the DirectMatchTask constructor, however DirectMatchTask defines butler as its first argument, not config. This causes the config object to be assigned to the butler argument. If the referenceObjectLoader is passed to DirectMatchTask's constructor then this has no impact. However if the referenceObjectLoader is None this will cause the task to fail.    See:  https://github.com/lsst/pipe_tasks/blob/master/python/lsst/pipe/tasks/photoCal.py#L256  and:  https://github.com/lsst/meas_astrom/blob/master/python/lsst/meas/astrom/directMatch.py#L42"
Answer: 1134.0

User story: LDM-148 is referring to "Prompt Processing Ingest" in section 5.1.3.    This product is not included in the product tree proposed in LDM-294 and in approval with the RFC-561.    Considering that, the product tree is not showing the sub-services in which "Prompt Processing" is divided, LDM-148 should be make consistent.    I suggest to rename 5.1.3 heading as:   * "Prompt Processing (at Base)"    and 6.1.1 heading as:   * "Prompt Processing (at NCSA)"
Answer: 230708.0

User story: "DM-17395 changed ci_hsc to write outputs for CharacterizeImageTask, but missed updating the SConsript for generating the pre-sfm run. This ticket fixes that."
Answer: 33.0

User story: "Write a simulator for the ATPneumatics CSC."
Answer: 7247.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "We need to do some optimization over the MySQL Cluster configuration to make it work according to our needs.    To do this, we will need to have a better idea of how much data and schema of the EFD.    Some links that may be helpful to do this are:   * [https://dev.mysql.com/doc/refman/5.5/en/mysql-cluster-programs-ndb-size-pl.html]   * [^mysql_wp_cluster_performance.pdf]    This task is meant to be on the backlog until there is a good idea of the amount of data the EFD will have."
Answer: 342985.0

User story: "Review laser tracker protocol interface docs, update text and diagrams to include new terminology (Laser Tracker CSC instead of Laser Tracker Controller, remove references to labview, etc). Our vendor, New River Kinematics, is proposing an API for communication between our CSC and their part of the code. Review this API and prepare feedback for meeting next week"
Answer: 15730.0

User story: Improve the ATDome CSC as follows:  - Make it the real CSC, not just a simulator  - Update for XML changes in DM-17610  - Add a command for homing  - Reject attempts to move in azimuth or home while already homing  - Make the engineering commands that move individual doors safer (the usual commands that open or close both doors are always safe; they have internal sequencing) and add unit tests for them:  -- Reject attempts to move the main door unless the dropout door is fully open or fully closed  -- Reject attempts to move the dropout door unless the main door is fully open  - Rename the bin script to remove the "_simulator" suffix and add a unit test for it  - Take a first pass at supporting configuration. The real code will have to wait until we have a standard for this.
Answer: 17727.0

User story: "In [obs_lsst #43|https://github.com/lsst/obs_lsst/pull/43] [~<USER> has added support for the UC Davis camera to obs_lsst.    We need to shepherd this through adoption into the DM codebase.   "
Answer: 9978.0

User story: "Implement RFC-557."
Answer: 10276.0

User story: "Collect, record, and verify technical progress data and narratives for the LSST Data Facility. Deliverable consists of updated JIRA issues and a Technical Progress Report."
Answer: 71936.0

User story: "Collect, record, and verify technical progress data and narratives for the LSST Data Facility. Deliverable consists of updated JIRA issues and a Technical Progress Report."
Answer: 33058.0

User story: "Remove the {{Coadd}} class, any supporting code, and the {{makeBitMask}} function."
Answer: 30033.0

User story: "Drop the dependency from pipe_tasks on coadd_chisquared.    Move the coadd_chisquared repository to lsst-dm/legacy-coadd_chisquared.    Update repos.yaml appropriately."
Answer: 1270.0

User story: "Peak culling was introduced to remove false detections around bright stars. Now it's been observed (with better sky subtraction and deeper images) that real sources are being culled. Ikeda-san is trying different parameter combinations."
Answer: 114789.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "It has been observed that the PSF as measured on the coadd is narrower than the PSF model says it should be. This has found to be true on the warps as well, so we believe it's an artifact of warping. [~<USER> is experimenting with higher-order Lanczos kernels."
Answer: 145037.0

User story: "The HSC survey data are obtained using a position angle whereby the saturation trails are east-west. When we use a skymap that has east-west along rows, the interpolation does not cleanly remove the saturation trails. This can be addressed by rotating the image the image before interpolation, and then rotating back."
Answer: 53005.0

User story: "Andy Goulding (Princeton) has delivered some improved bright star masks. These need to be installed and tested."
Answer: 60537.0

User story: "The current full-visit sky subtraction is not perfect; in particular, there are some negative residuals around the edge of the field of view. [~<USER> is investigating potential improvements, including the use of PCA."
Answer: 108588.0

User story: "Make documentation current again."
Answer: 3187.0

User story: "Consulting with DESC and [~<USER>, choose a tract or two of ImSim DC2 data from the subset [~<USER> already copied to /datasets/ to reprocess as part of the new monthly DRP reprocessing, that meet DRP's QA needs.     End product of this tickets is tract number(s) and visits listed in the comments.   "
Answer: 538064.0

User story: "travissync job is both broken and no longer useful."
Answer: 18.0

User story: I'm taking the last piece of DM-16227 - using SQLite's  "ON CONFLICT DO NOTHING" variation of INSERT - out of that ticket because it doesn't work with 3.24 (it does with 3.26), and I'm not totally certain the behavior I'm depending on is guaranteed going forward.    On this ticket, try to answer that question by pestering the SQLite mailing list (etc).  A Stack Overflow question ([https://stackoverflow.com/questions/54261493/sqlite-unique-conflict-resolution-ordering)] has thus far generated no responses.    An alternative to the current approach would be to instead set the conflict resolution policy at schema definition time.  This works with both SQLite 3.24 and 3.26, but unfortunately is also not clearly documented to do what we want in this case.  If this approach is taken, DM-17154 should be considered a blocker.
Answer: 376304.0

User story: The shim calls this parameter "origin", but the actual Gen2 butler calls it "imageOrigin".
Answer: 9104.0

User story: "Run jointcal with HSC-RC2 and w_2019_06"
Answer: 28922.0

User story: "Run pipe_analysis scripts   # visitAnalysis   # coaddAnalysis   # colorAnalysis   # compareVisitAnalysis   # compareCoaddAnalysis    and validate_drp   # matchedVisitMetrics.py   # validateDrp.py   # reportPerformance.py    Upload the validate_drp metrics (json files) to SQuaSH:   # dispatch_verify.py    with the w_2019_06 RC2 outputs from DM-17400"
Answer: 34395.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: "Reprocess the HSC RC2 dataset, as defined in DM-11345, using Stack w_2019_06. Steps include {{makeSkyMap.py}}, {{singleFrameDriver.py}}, {{mosaic.py}}, {{skyCorrection.py}}, {{coaddDriver.py}}, and {{multiBandDriver.py}}. "
Answer: 34377.0

User story: "Michelle discovered an interesting issue while trying to run {{pipetask}} on a single Qunatum (extracted from a full graph). Graph {{traverse()}} method tries to determine prerequisites for a quantum execution by looking at quanta inputs and determining which other quanta produced those inputs. It works OK on a full graph but when single quantum is removed from a graph its prerequisites are not in the same graph anymore and {{traverse()}} currently does not like this (it crashes).      "
Answer: 338.0

User story: "In order to ensure a consistent environment reference with the weekly lsst_distrib build, the git package scipipe_conda_env should be tagged github at the same time that all lsst_distrib packages are tagged.         Release procedure shall be updated also."
Answer: 215052.0

User story: "By default ProcessCcdTask does not write out all the outputs generated by CharacterizeImageTask. This ticket will set configs such that all outputs are written out when ci_hsc is run. This will aid in comparison checks and migration to gen3 middleware. This will not increase the run-time of ci_hsc, and will only minimally impact storage."
Answer: 2944.0

User story: With the new ISR order implemented in obs_decam (DM-15862), it is necessary to rerun processCcd when making new coadds from hits2014 "template" images to be self-consistent with the processCcd that happens on the hits2015 "science" images in ap_pipe. This ticket is to do all that to make new DCR coadds (DM-16864) and a corresponding new ap_pipe rerun.
Answer: 14374.0

User story: "Verify Firefly can access WebDAV workspace for datasets (/lsst/datasets) as a user.    Initial work on user workspaces."
Answer: 18771.0

User story: "Work on integrating Firefly authentication in with the lsst-lsp-int domain (in the `lsst-pdac` kubernetes namespace).          This may need a few changes to the authorizer, and some code changes in to firefly to be maximally useful"
Answer: 8915.0

User story: "Convert CalibrateTask into a Pipeline task"
Answer: 4706.0

User story: "goal setting for FY 18"
Answer: 299.0

User story: "With the implementation of RFC-554, pipe_supertask is now obsolete.    Following actions are required:   * rename pipe_supertask to legacy-pipe_supertask   * move legacy-pipe_supertask to lddt-dm   * update repos.yaml"
Answer: 31.0

User story: "Thereby including it as part of the lsst_distrib metapackage."
Answer: 20465.0

User story: "Write the self-evaluation in Ultipro for the 2018 performance evaluation."
Answer: 6727.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: "https://developer.lsst.io/team/onboarding.html#data-facility-resources states (or, at least, heavily implies) that everybody being onboarded to DM automatically gets issued with an account which provides access to Nebula.    Apparently, that's not actually the case: Nebula accounts are only available following the procedures at https://developer.lsst.io/services/nebula/index.html and are not issued automatically.    Please update the Dev Guide to make this clear."
Answer: 187394.0

User story: "We need something that will run queries all the time through the TAP service, to keep exercising TAP and qserv all the time.  This is because a fair number of times, something seems to get stuck, and while all the hosts are up, things aren't working.  This will also be a good way of simulating users from the notebooks and portals and give us at least some query load.  Right now in the PDAC our query load is very low, and issues may languish without being detected for some time."
Answer: 8501.0

User story: "Deploy InfluxDB from its helm chart      {noformat}  helm install stable/influxdb -f influxdb-values.yaml --name influxdb    {noformat}    InfluxDB uses [this configuration|https://github.com/lsst-sqre/ick-deployment/blob/master/influxdb-values.yaml]     which:     1) creates a persistent volume of 128G for the database  2) enable the nginx ingress controller and set  {{hostname: influxdb.lsst.codes}}  3) override the InfluxDB configuration parameter  {{max_row_limit: 0}} to avoid data truncation when using the HTTP API.         "
Answer: 10214.0

User story: "Splitting the {{_camera}} work from DM-17291 as it's separate (and more complex) than the {{_lsstCamMapper}} work."
Answer: 17080.0

User story: "astro_metadata_translator has by default been using GPLv3. In order to encourage contributions from the astropy community in this ticket we will change the license to BSD 3-clause."
Answer: 10203.0

User story: "This task is to review the following ATHexapod tasks.    https://jira.lsstcorp.org/browse/DM-17161    https://jira.lsstcorp.org/browse/DM-17162    Since this review is expected to be rather involved, it deserves a task of its own."
Answer: 120.0

User story: "The task is to meet with Tiago (and <USER> and provide Tiago with the information he needs to take over management of the pointing component contract."
Answer: 132.0

User story: "An action item out of the ATDome meeting relating to [https://confluence.lsstcorp.org/display/LTS/ATDome+Control+Issues] was to look at the vendor-supplied SmartDome software, identify what desired features are missing or already present somehow or how they could be met, and summarize options for making modifications.    The deliverable will be a report that addresses these topics."
Answer: 5789.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 covers the effort to learn how to use Docker and how it integrates with Jenkins.  The TSSW Jenkins environment was updated to be more DM like and therefore, requires using Jenkins to run jobs via Docker containers.  I need to time to learn and implement the testing in this new paradigm."
Answer: 47.0

User story: "Update the ts_tcs_ofcPython, ts_tcs_wep, and ts_tcs_wep_phosim to use the scientific pipeline with the tag of w_2019_02. This is to adapt the update of obs_lsst."
Answer: 24533.0

User story: "obs_lsst needs to have the documentation build enabled. It still mostly uses doxygen strings (presumably as a hold over from the early days)."
Answer: 10050.0

User story: "This task covers the re-training on M1M3 control in support of Mirror Lab testing."
Answer: 56.0

User story: "Get the Pointing Component tests created and running.  Get the Docker image from Andrés that has the PtgComp installed.  -Figure out how to run the vendor supplied Robot-Framework tests.-  "
Answer: 24444.0

User story: "The ATDomeTrajectory CSC needs to know where in azimuth the dome is headed, in order to work properly. It would be really nice to get this as an event instead of having to follow a telemetry stream, because the one value we care about only changes occasionally.    I am requesting a new event that outputs the commanded state. For this to be useful the dome would have to output the event when it starts up, presumably listing the current state of the dome as the commanded state."
Answer: 158034.0

User story: "The ts_SALLabVIEW VI currently requires user interaction to provide the    location of the .idl and .so files. We need to be able to have this information   be provided externally (eg at command line) so that the entire process can be   run automatically with no user interaction required.   e.g.    updateSALLVcontrols ATMonochromator [optional location]    the default location would be $SAL_WORK_DIR/subsystem-name/labview/lib    Below are notes to myself to finish this task. "
Answer: 751983.0

User story: "This task covers   * time to research and learn about Docker.   * create a Docker image configured for testing.   ** miniconda or scl/ius for Python3 support   ** Robot-Framework   ** XML parser   ** dependencies"
Answer: 24452.0

User story: "salgenerator should now be producing the C++ telemetry, commands, and event tests into a single file so that during automated testing the tests can be completed much faster than having to fire up a sal manager every time. Which currently is all we have.  This task is to do the same for Java. The reason there is part 1 to the task is I am not quite sure how it works. Once I identify what I need to know I can better estimate the length that this task will take me."
Answer: 95088.0

User story: "* Implement setMaximumSpeeds in the ATHexapod, this will be used from the configuration files.   * Update target position from the controller directly instead of following at a higher level "
Answer: 10350.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Currently only the commands in c++ are being tested from a single file. This task is to complete tcl scripts to produce the telemetry tests into a single file as well."
Answer: 47802.0

User story: "Add kafka high data rate writers to the end machine in the mirror lab.  Run on a separate machine as well. Verify binary log backups"
Answer: 49105.0

User story: "Currently only the commands in c++ are being generated into a single file. This task is to complete tcl scripts to produce the telemetry tests into a single file as well."
Answer: 44765.0

User story: "Currently only the commands in c++ are being done. This task is to complete tcl scripts to produce the events into a single file."
Answer: 24630.0

User story: "Add simulation mode to CBP CSC. Commands should return sensible values.    Add settings and configuration to CBP CSC."
Answer: 217863.0

User story: "# Test SAL java interface with aux tel camera CSC in simulation mode on the test hardware cluster.   # Have [~<USER> test with his latest auxtel camera code and the physical camera system."
Answer: 44907.0

User story: "Perform some initial evaluation of release:    'ts_pointing_common'  tagged it as v0.1."
Answer: 197150.0

User story: "For the most part I have the changes I have made here complete TSS-3276, this task is to go over with Dave on my computer and make sure indeed that this is the behavior that is desired. I also have questions.     Primarily which files are involved with the Python wrapping. I will also include these relevant files with the visuals I am creating to help understand the salgenerator pipeline. "
Answer: 56435.0

User story: "Create a standalone program that can run on multiple machines. "
Answer: 44913.0

User story: "This task captures the time spent learning pybind 11. I have a standalone program that I have been working on as well which I used as a sandbox. Doing this helped with the learning curve jumping onto the templates used for ts_sal. "
Answer: 44925.0

User story: "Revamp LinearStage hardware api."
Answer: 452159.0

User story: "Add moving state substate to LinearStage xml and CSC. Involves adding Enum subclass and finishing detailed_state getter and setter.    Tested with localhost vm and embedded pc using chesterfield as remote. Linear Stages are now on separate USB ports and are capable of moving at the same time. They will not accept a moving command while moving. Script code has been modified accordingly. XML was adjusted for index-ability.    [Github Pull Request|https://github.com/lsst-ts/ts_LinearStage/pull/7]"
Answer: 21493.0

User story: "Many of the EAS sensors have a requirement for SAL support on an embedded system  (Raspberry Pi). Create a reference implementation and consult with the developers to deinfe the appropriate generic EAS XML for the various sensor types"
Answer: 34500.0

User story: "Continue SAL mentoring, advise in building single task command/event test programs for faster Jenkins testing"
Answer: 17121.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: "Modify the EFD writer generators to produce code that bundles multiple available updates into single transactions to increase efficiency when the message rate it high"
Answer: 62084.0

User story: "Make the mirror lab EFD instance accessible via a VPN connection using the second ethernet port"
Answer: 62086.0

User story: "Change writers to implement transactions which batch sets of inserts for increased effciency"
Answer: 30270.0

User story: "Add settings & configuration reader to TunableLaser api that is in accordance with the yaml specification. It will use pyyaml to parse and update settings. Currently blocked due to in-progress design of salobj configurable CSC."
Answer: 168774.0

User story: "As part of the new simulation mode for CSC, design and implement a simulation mode for the hardware. Mock serial port and return sensible values for registers.    Read only registers will set static value and writable registers will set whatever acceptable values are sent.    [Github pull request|https://github.com/lsst-ts/ts_TunableLaser/pull/9]"
Answer: 25588.0

User story: "Update the EUPS version of sqlalchemy following RFC-564."
Answer: 1131.0

User story: "The LinearStage has logic that is tied to the now deprecated ts_statemachine and salpytools. The hardware api shall be cleaned up of this logic. The statemachine api will be removed because salobj inherently handles state functionality. The project structure will also change to a more traditional pythonic structure. The zaber library will be upgraded to the latest one released.         [Github Pull Request|https://github.com/lsst-ts/ts_LinearStage/pull/6]"
Answer: 1514.0

User story: "Add some more colour to the LSST Catalog Tutorial to show how to use the new ADQL spatial functions using pyvo."
Answer: 9992.0

User story: "Create the tcl script that will produce a makefile for the cpp generated file. "
Answer: 1524.0

User story: "development of error code reporting and responding to bugs found during testing"
Answer: 20274.0

User story: "execute tests which involve manual voltage setting on the test hardware"
Answer: 1530.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: "Technically the code is there, but has not been functionally tested. In order to be complete, it must be tested and working. This allows the TunableLaser to start emitting the light beam and stop emitting through SAL state transitions. The component API already implements this functionality. Had <USER>look over the current implementation and he had some suggestions. I will be making those changes as part of this task.    The CSC now demonstrates basic state transitions including substates for propagating the laser. It demonstrates both local host functionality and network functionality with the chesterfield script machine. It can start propagating when in the enabled state. It can also stop propagating and be in the enabled state or if disabled will also stop propagating. Revamped the hardware wrapper api based on better understanding of hardware itself, updated the firmware to gain access to several error registers. Revamped unit tests to a slight degree. There is also a very simple settings api. Added all temperature sensors to telemetry in preparation for some stability(plus the fact that we don't know which ones are important). Added changedWavelength event to indicate that the wavelength has changed(may be redundant if wavelength is published as telemetry).          [Github Pull Request|https://github.com/lsst-ts/ts_TunableLaser/pull/8]"
Answer: 66298.0

User story: "Currently, in the running of fgcmcal the output plots must be inspected after every fit cycle to determine the optimal cuts for removing non-photometric exposures from the model fit.  However, while inspection will still be recommended for large-scale runs to ensure the best performance, I have enough experience now to compute default cuts."
Answer: 12152.0

User story: "This task will consist in making sure ATPointing and ATAOS run with the same version of SAL, write an OCS-Script to drive the test and run the test locally.     Final integration will happen when both systems can be deployed on the Test environment using our deployment strategy.     Artifacts:   * Docker container with ATPointing component   * Docker container with ATAOS component   * OCS-Script to drive the test    Required CSC:   * ATPointing   * ATAOS   * ScriptQueue          "
Answer: 21894.0

User story: "Initial version can probably just continue with the Gen2 of pretending these are FITS (they have readFits and writeFits for that reason).    Longer term (not this ticket), we should give them their own StorageClass and/or Formatter and maybe think about sharding them on SkyPix."
Answer: 2.0

User story: "During the process of working on pipelinetasks/middleware, functionality has been added. This ticket will make DetectCoaddSources (the first task converted) use that new functionality."
Answer: 7485.0

User story: "assembleCoadd wants to apply the bright object masks. They are inputs available to ci_hsc. gen2convert should convert them so they're available to the gen3 version when processing on ci_hsc"
Answer: 17748.0