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 images in the drop down menu of the LSP spawner are currently sorted by date. This is ok, but it makes it a bit hard to find a specific image, especially if it is ancient (i.e., the preceding major release). It would be nice to instead sort by image name. I think this would mostly have the effect of being a sort by category and then a sort by date within category (at least if the naming conventions hold). I could see arguments for major release, weekly, daily (from least populated to most) or daily, weekly, major release (from most recent to least).    This will require changes to [scanrepo.py|https://github.com/lsst-sqre/jupyterhubutils/blob/master/jupyterhubutils/scanrepo/scanrepo.py]"
Answer: 451.0

User story: "Using a bleed version of the conda environment, afw test case PhotoCalibTestCase fails with the following error:       {code:java}  # create with non-zero fluxMag0 and err   photoCalib = lsst.afw.image.makePhotoCalibFromCalibZeroPoint(fluxMag0, fluxMag0Err)   self.assertEqual(photoCalib.getInstFluxAtZeroMagnitude(), fluxMag0)   > self.assertEqual(photoCalib.getCalibrationErr(), calibrationErr)   E AssertionError: 1617423020.8062096 != 1617423020.8062098{code}"
Answer: 275.0

User story: "In order to facilitate the interactive/dashboard QA work of [~<USER>, currently, the {{pipe_analysis}} scripts have the option to write out parquet tables for the various datasets at the visit and tract level.  Currently, they only contain the information in the source catalogs plus an extra column to indicate the deemed suitability of a given source for QA analyses, and columns to indicate the ccd & visit or patch & tract per object.  It would also be of great use for the interactive plotting to have a set of columns with pre-computed values of interest for plotting (e.g. mag differences, reference catalog comparisons, etc.) These are also the per-object values from which various (aggregated) metrics will be computed.  The strategy for now will be to add a column to the parquet tables for any value that is computed and plotted in the {{pipe_analysis}} scripts."
Answer: 68001.0

User story: "Version of the submission to Pegasus allowing Operator to specify required memory and required cpus per pipeline task in a config file."
Answer: 108243.0

User story: "File a TR for attendance at the conference."
Answer: 16196.0

User story: "SQuaSH store code changes for each CI run with respect to the previous one. This information must be added to InfluxDB and displayed by Chronograf.    To display that in Chronograf, we need the ability to add links to external pages into the Chronograf table cells."
Answer: 7235.0

User story: "{{ci_id}}, {{ci_url}} and {{squash_id}} are sequential numbers. If mapped to InfluxDB tags that will   [increase InfluxDB series cardinality|https://docs.influxdata.com/influxdb/v1.7/concepts/schema_and_data_layout/#discouraged-schema-design] which is not recommended.    We should add {{ci_id}}, {{ci_url}} and {{squash_id}} as InfluxDB fields instead."
Answer: 280144.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Using multi-cast to do service discovery does not work in GKE environment, and also it requires low-level hardware configuration. DM-17601 was created to explore the alternate way to accomplish service discovery. It recommended using redis. This is the implementation ticket.          <text taken from PR>    *Objective:*  The objective is to implement an alternative to multicast cache peer discovery mechanism. Multicast is not supported in the cloud, making Firefly unable to scale horizontally.    The implemented alternative is to use a publish-subscribe messaging system for peer discovery. The flow is similar to multicast in which it relies on a periodic heartbeat message from each active peer to determine ‘liveliness’. Subscribing to the same channel determine the membership of the group.    *Implementation Details:*  A custom CachePeerProviderFactory is created to determine which discovery mechanism to use based on configuration.  Messaging is implemented using Redis server and Jedis client. The preferred deployment of Redis is via Docker. Jedis dependencies were added to Firefly.     "
Answer: 118019.0

User story: "The current version of the analysis tool (https://github.com/moeyensj/difi) supports only holistic completeness calculation and a variety of other linkage quality metrics. These should be calculated for each population of Solar System minor planets as well.    Final deliverables will be an updated analysis tool that outputs metrics per population in the Solar System and also plots useful quantities as desired by the user. The analysis tool is made to be as general as possible so that other detection linking algorithms can use it to analyze linkages, this should remain true for any metrics added in the future. "
Answer: 807903.0

User story: "We have had multiple request for the search panel drop down to be able to be resizable in certain cases such as the TAP search panel, catalog search panel and the image search panel.    Implement an option so that a search panel can be resizable based on available space.  Implement this in the TAP search panel.  You could do the Image search panel if time permits."
Answer: 5863.0

User story: "Add {{jointcal}} templates ({{jointcal_wcs}} and {{jointcal_photoCalib}}) to {{obs_lsst}} policy file so that {{jointcal}} can be run on {{imsim}} data (at least)."
Answer: 1714.0

User story: "The latest version of lsstdesc/coord (v1.1), which is repackaged in lsst/coord (currently v1.0.5), has important bug-fixes including fixing a leaking file descriptor.  So it should be upgraded.  This is only a secondary dependency, and does not require an RFC to update."
Answer: 7987.0

User story: "Schedule a demo of the proposed technology for glossaries and acronyms (when the technology is available) "
Answer: 279414.0

User story: "Test and verify SODA functionality in PDAC."
Answer: 19768.0

User story: "One key/open question is what version of SIA should DAX implement."
Answer: 394944.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 FITS files generated by the ATArchiver using the headers created by the HeaderService had to be adjusted to proper ingestion."
Answer: 9.0

User story: "SST task inherited from Mario. Some work was done,[~<USER> is collecting use cases from the science collaborations and the PST requests an overview document explaining DM plans for the treatment of crowded fields in PST-30    The goal of this ticket is to consolidate previous and current efforts and deliver a response to PST-30"
Answer: 324038.0

User story: "While we wait for a complete list of DIAObject timeseries features (https://jira.lsstcorp.org/browse/DM-11962) it will be useful to have various simple statistics to assist with exploring AP processing outputs.  The implementation is not expected to be final.    In a brown bag discussion, we suggested the following (all computed on calibrated fluxes):   * max   * min   * mean   * std   * skew   * median   * MAD   * percentiles ([5,25,50,75,95])   * Stetson J   * Linear trend   * max delta flux/delta t   * average flux error"
Answer: 18795.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 summary"
Answer: 24529.0

User story: "Sometimes, when trying to debug SAL communication,  it is useful to have the test scripts generated by salgenerator. I think it would be helpful if make_salpy_lib has an option to keep those files. "
Answer: 23335.0

User story: "Replace Vault with a productionalized instance with real certificates."
Answer: 577.0

User story: "Participate on meetings leading to the design of the plan of deliverables concerning the components of the Dome Control System software. The first phase is to get a simulator version we can utilize to exercise the TCS dome interface."
Answer: 160263.0

User story: "Reprocess the HSC RC2 dataset, as defined in DM-11345, using Stack w_2019_14. Steps include {{makeSkyMap.py}}, {{singleFrameDriver.py}}, {{mosaic.py}}, {{skyCorrection.py}}, {{coaddDriver.py}}, and {{multiBandDriver.py}}. "
Answer: 80894.0

User story: "Change template to have unique filenames in ci_hsc.  If possible save the templates to a file."
Answer: 4354.0

User story: "Determine additional details and present plan to DMLT."
Answer: 2782.0

User story: "*Reran RC2 dataset through the following 3 configurations:*   * coaddDriver/multiband lanczos5 rerun (to be used for scientific performance studies): e.g. see [~<USER>'s [https://nbviewer.jupyter.org/github/lsst-dm/modelling_research/blob/master/jupyternotebooks/psf_models_rc2.ipynb]    {{/datasets/hsc/repo/rerun/private/<USER>RC2/w_2019_06_lanczos5}}    * lanczos5 makeCoaddTempExp rerun for metadata extraction:{{/datasets/hsc/repo/rerun/private/<USER>RC2/w_2019_06_lanczos5_dir}}     * lanczos3 makeCoaddTempExp rerun for metadata extraction:   {{/datasets/hsc/repo/rerun/private/<USER>RC2/w_2019_06_lanczos3_dir}}"
Answer: 74644.0

User story: "All organizational and logistical aspects of the LSST Science Platform Final Design Review"
Answer: 61036.0

User story: "Implement RFC-577"
Answer: 127267.0

User story: "Attend Spatial Analyzer training event in Los Angeles, March 12-14, plus travel days"
Answer: 20158.0

User story: "Hook the ADAM box and our CSC up to the actual KiloArc device in the lab, and try sending commands to it. "
Answer: 409156.0

User story: "Implement detailed state on the WLS CSC. This will simply be an enumeration of the hardware states that we can receive from the KiloArc. Since we already react to an error signal from the KiloArc, this won't change CSC behavior, it is strictly about reporting more information."
Answer: 81334.0

User story: "New test cases corresponding to requirements in LDM-554 are being created in the Jira LVV project. Existing test cases that were defined in the first version of LDM-540: LSST Science Platform Test Specification have been imported into the Jira LVV system. A new version of LDM-540 will be generated based on the newly defined test cases, and will deprecate the test cases in the first version of LDM-540. "
Answer: 40277.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: "Many requirements in LDM-554 have open questions in the discussion section that reflect gaps in our understanding at the time of writing. In preparation for the LSP review, these should be again reviewed. "
Answer: 40295.0

User story: "This ticket covers the creation of test cases in Jira corresponding to the requirements in LDM-554: Data Management LSST Science Platform Requirements. "
Answer: 40303.0

User story: "Write a new set of XML for a generic camera CSC and implement it with ts_salobj.    Required items:   * Set Exposure Time   * Set ROI   ** Top, Left, Width, Height   * Set Full Frame (short cut for the set ROI command)   * Start Live View   * Stop Live View   * Event indicating live view ip / tcp port for image data   * Event indicating current exposure time   * Event indicating current ROI   * Event for camera specific properties (key / value pair basically)   * Event for camera make / model   * Telemetry for temperature"
Answer: 14455.0

User story: "Update SAL runtime and writers on hardware test cluster pLAN EFD"
Answer: 34596.0

User story: "There are currently no tests for the `get_closest_state` definition. This task is aimed to get some code coverage on it, specifically making sure that the binary schema I implemented is working correctly. I only have done some minor interpreter testing."
Answer: 755217.0

User story: "Travel to Spain for Mount FAT campaign"
Answer: 567751.0

User story: "In the electrometer (LabVIEW code) I'm sending an LFO event, the vi that does the logEvent for that topic is being executed, in parallel I'm also running the cpp logger for that event.     But sometimes I don't see that event in the cpp logger (I get almost all messages but there are cases I don't).     Andres."
Answer: 684492.0

User story: "This task is to track work on creating the design artifacts for this CSC.    Success criteria:  # Create the UML model  # Generate the XML file   # Commit the XML file to the ts_xml repo  # Run and pass all tests (Jenkins)"
Answer: 1191146.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: 134033.0

User story: "Continue SAL mentoring activities with Andrew, Tei-wei, Garry , Petr etc"
Answer: 751612.0

User story: "Old T&S Epic carried over from old JIRA project - no longer valid"
Answer: 1608965.0

User story: "Begin reviewing the EFD Writer generators. "
Answer: 292728.0

User story: "Detailed design"
Answer: 1351493.0

User story: "Work on task https://jira.lsstcorp.org/browse/TSS-3196"
Answer: 333078.0

User story: "Initial simulator support"
Answer: 1909620.0

User story: "The role of the DM Science Validation Scientist, as described in [LDM-294|http://ls.st/LDM-294] and [LDM-503|http://ls.st/LDM-503] will relocate to  LSST HQ in Tucson as a 100% role from mid 2019"
Answer: 2669.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: "Based on doing DRP processing with S3 storage."
Answer: 9852.0

User story: "Action from DMLT F2F."
Answer: 5470.0

User story: "Action from DMLT F2F."
Answer: 71675.0

User story: "Schemas are slightly misaligned between ap_association and dax_ppdb. This causes a crash in running ap_pipe on round-tripped diaObjects. This ticket will add the nessacary columns (validityStart, validityEnd, lastNonForcedSource) to the default diaObject schema in ap_association"
Answer: 2749.0

User story: "It should be possible to generate Kubernetes YAML for an arbitrary k8s cluster without requiring that gcloud (or even kubectl?) be present on the generating host--effectively, we want a way to break the templating engine out and remove its dependencies on external programs."
Answer: 1283.0

User story: "Ticket to track effort to keep the Notebook Aspect running as upstream packages change."
Answer: 126996.0

User story: "Get tests from Tony and include in SAL - or at least make them like SalObj tests"
Answer: 80935.0

User story: "{{ip_diffim}} generates lots of dipole fit fields in the DIASource catalogs.  This ticket is to investigate them and suggest a mapping to the DPPD fields."
Answer: 51538.0

User story: "Things in ctrl_iip need to be reorganized to conform to the DM standard repo style. The subtasks below this story are to be the steps in reorganizing individual code, configs, etc. properly."
Answer: 41380.0

User story: "Please propose the following items:   * the blue buttons: tap search, upload   * URLs 'tap search' for SUIT portal "
Answer: 459715.0

User story: "Both Babel and ESlint are behind and should be upgraded.   * For ESLint there are also the rules to react functional components that can be added.   * We are currently using Babel 6.26, upgrade to the most recent 7.4.   * We are currently using ESlint 4.5, upgrade to 5.1    _Babel Helpful docs:_   * [https://babeljs.io/]   * [https://babeljs.io/docs/en/v7-migration\|https://babeljs.io/docs/en/v7-migration]    _ESLint Helpful docs:_   * [https://eslint.org/]   * to add react functional component rules   ** [https://reactjs.org/docs/hooks-rules.html#eslint-plugin]   ** {{npm package: eslint-plugin-react-hooks}}    _Driving reasons:_   * We like to keep Babel up-to-date for support purposes.   * Github posted by security vulnerability alert at [https://github.com/Caltech-IPAC/firefly/network/alerts].   * Babel 7 also adds better JSX support for react fragments.    A similar ticket in IPAC Firefly team has been scheduled for July sprint.  [https://jira.ipac.caltech.edu/browse/FIREFLY-74]      [|https://jira.ipac.caltech.edu/browse/FIREFLY-74]"
Answer: 197751.0

User story: "We work through an example of a subscription to trigger a rule based replication. The subscription is measured against  data upload  & metadata assignment, leading to the creation of rules for data replication. "
Answer: 18.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "DM-17025 added the ability to validate a DatasetRef against a selected file template. Now we need the ability to be able to test that every single registered DatasetType is consistent with the corresponding file template (for datastores that support file templates).    We also need to be able to form a DatasetRef for every DatasetType and every instrument to check that instrument specializations also conform.    It should probably also check that every one of those DatasetRefs has a corresponding formatter assigned.    Chained datastores will have to forward the validation to each contained datastore noting that not all datastores have to support all datasetTypes in a chained datastore.    I am assuming this should be a command that is run on demand rather than something that occurs every time the butler is instantiated."
Answer: 12871.0

User story: "Continuing the effort to implement the build and packaging process for T&S CSCs."
Answer: 487410.0

User story: "{{ccd=9}} is now causing problems during flat construction, as it is reporting sky levels of zero. It's possible something has changed in the raw data (maybe it's being zeroed instead of recording noise?)."
Answer: 5970.0

User story: Now that the software components for the calibration system are up and running again I'll be able to run some integration tests in the lab. I'll take this opportunity to properly debug an document any SAL/ScriptQueue related issue I encounter.     Required Components:    - ATMonochromator  - FiberSpectrograph  - Electrometer  - ATSpectrograph  - ATCamera      Additional components:    - White Light Source  - Chiller     * - Additional components are those that are not required for the tests but will be added if available.     The artifacts of this task will be "at least" a script to run the Calibration system and probably one that also involves the ATCamera and ATSpectrograph, as well as confluence page with description of the issues encountered and jira tickets.    
Answer: 20335.0

User story: "This task captures the work required to write and test a script to take standard detector characterization dataset(s) for ATCamera. "
Answer: 6395.0

User story: "We need to add testing to scarlet in order to prevent breakage and ensure the stability of the code. This ticket includes adding regression tests for all of the submodules and connecting to Travis CI to run tests on every commit.         This ticket includes tests for the {{operator}}, {{constraint}}, {{resample}}, and {{transformation}} modules. Other tests will be implemented once the refactoring of scarlet is finished by [~<USER>."
Answer: 20542.0

User story: "Work on and Finish thermal initial plan."
Answer: 1763.0

User story: "Implement a basic token download interface which gives users options of scopes to issue for their token.         The code probably should be separate from jwt_authorizer, but it will likely need to share code and secrets (e.g. for a redis backend)"
Answer: 44603.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: "Work on a redis-based oauth2_proxy session store.    Once this is implemented, integrate token reissuance from the jwt_authorizer to write to that store as well.     "
Answer: 14342.0

User story: "Integrate jupyterlab with the token proxy for lsst-lsp-int.     "
Answer: 4334.0

User story: "Add a unit test suite to pytrax, so that we can then continue to develop the code without breaking it."
Answer: 219602.0

User story: "Work on planning for future M1M3 support work"
Answer: 5601.0

User story: "Sometime in the next month, I will be replacing {{Calib}} with {{PhotoCalib}} (DM-10153). We need a note in the Release Notes for v17 to prepare people (the transition is not fully backwards compatible)."
Answer: 86683.0

User story: "SAL v3.9 contains two new features   * RPM packagaing   * Combined interface modules    This task covers the effort required to update the tests for these new features.    There is also a desire to improve/increase the level of Java testing at the SAL layer.  This task also covers some time to work on this."
Answer: 19964.0

User story: "Make sure that the any and centre fake flags are being set during processing."
Answer: 145927.0

User story: "Make plots comparing input and output shapes for fake sources and add them to pipe_analysis."
Answer: 257916.0

User story: "Make magnitude based plots using the fake sources for QA purposes and add them to pipe_analysis."
Answer: 252137.0

User story: "Use fake sources to make plots of input v output posistion and add the plots to pipe_analysis."
Answer: 252175.0

User story: "Make plots showing the faintest fake sources detected for SE and coadd images."
Answer: 257966.0

User story: "Use cases and Requirements (once in Magic Draw) have to be formally reviewed in an RFC.    Create RFC."
Answer: 151719.0

User story: "Attached to [DM-16084|https://jira.lsstcorp.org/browse/DM-16084] is an Excel spreadsheet with Batch Production Services requirements.   Please ingest them into the LSST model.  The spreadsheet contains a second sheet with opening paragraphs and the list of authors if needed.    Also, please note that that in one of the requirements (row 4) we reference LSE-81 as the parent requirement."
Answer: 24300.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: "Pending approval of RFC-578, please install the Goulding S18A bright star masks on the LSST cluster.    I recommend the following strategy:  * Rename the current {{/datasets/hsc/deepCoadd/BrightObjectMasks}} --> {{/datasets/hsc/deepCoadd/ArcturusMasks}}.  * Install the Goulding S18A bright star masks in {{/datasets/hsc/deepCoadd/GouldingMasksS18A}}.  * Create a soft link: {{/datasets/hsc/deepCoadd/BrightObjectMasks}} that points to {{/datasets/hsc/deepCoadd/GouldingMasksS18A}}.    This keeps both versions available, defaulting to the new masks. Users can explicitly select the old masks by creating a link in their rerun named {{deepCoadd/BrightObjectMasks}} that points to {{/datasets/hsc/deepCoadd/ArcturusMasks}}.    I am currently downloading the Goulding S18A masks to {{/scratch/pprice/GouldingMasksS18A}}."
Answer: 40402.0

User story: "Need options for:   * row-wise plotting of fits vs data   * spectrum-wise plotting of things   * plotting of residuals    Also probably want to tweak/enhance the debug display functionality too."
Answer: 864859.0

User story: "* Fix up anything still marked with an xxx in comments.   * Fix PEP8 violations, anything else that is obviously wrong.   * Improve all docstrings. They're not currently terrible, but some still have placeholders, and many other functions and tasks will be created soon before review"
Answer: 864873.0

User story: "Given a list of gains per-amplifier, apply them as if flatfielding.    Write a function to make this into a fake flatfield, so that it can be applied as part of ISR if required."
Answer: 140274.0

User story: "Quite likely won't be implemented, but might be necessary, depending on how AuxTel operation plans go. Currently the plan is to only disperse along the vertical, and use either one or both orders depending on the seeing. However, should we decide to disperse along the paralactic angle (which has advantages wrt the dispersion relation and bending of the spectrum, but disadvantages of splitting the spectrum over many more amps) then we will need to make this extension."
Answer: 864861.0

User story: "Currently we just use the m=+1 order. This tickets will add support for the m=-1    This will probably just involve confirming the bbox calculation is correct, and flipping the spectrum so it can be treated the same."
Answer: 864862.0

User story: "Add support for using the fitted PSF to do a spectral extraction all in one go."
Answer: 864862.0

User story: "We want to be able to do a whole-spectrum fit, rather than row-wise slices, so a PSF model is required.      We should be able to support some analytical/physical model, and also doing something arbitrary as the lab-PSF is not normal (some kind of flat-topped Gaussian maybe?)"
Answer: 864862.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 already have obs_ctio0m9, but some of the data we have from that telescope is not compatible with the obs_package as it stands, as they kept changing which amps they read out, and in what configuration.    With the help of Augustin, pick a few files with the same layout, and for which there exist a few biases (and other calibs if/as required) and get them readable.    This might mean making a temporary fork of obs_ctio0m9 to get things working.    Build the calibration products, and get processStarTask running on it.    Necessary because we want to test this pipeline with absorption spectra before going on sky, and the lab will only ever provide emission spectra, not to mention it would be nice to have a more realistic PSF."
Answer: 178777.0

User story: "Move the array-like members of the SpectralExtractionTask to be a Spectrum object, which contains the dispersion so that is can be returned (and so that it all actually makes object orientated sense!). This structure was only ever temporary."
Answer: 864862.0

User story: "Sort out how/where the functions are defined, so that the can be evaluated neatly with the fitted params."
Answer: 145985.0

User story: "As part of DM-17488, I wrote a baseline script that used the linearstage and electrometer during the two weeks of Nick's visit outlined in DM-17943 and DM-17694. I made a design decision which allowed for a configurable script that would eventually allow for full functionality of script as defined in DM-17488.     This script is located in ts_externalscripts as es_coordination_laser_001.py uses the two linear stages mounted at right angles to move them in a grid pattern while the electrometer takes data. The parameters of the test outlining the position of the linear stages and the url containing the fits file of data of the electrometer is written to a txt file.     The manual parts of the test included the TunableLaser and CBP.  The TunableLaser was propagating at a set wavelength with a fiber optic cable attached that was transmitting light to the integrating sphere of the CBP which was at a fixed position."
Answer: 143.0

User story: "This will give us versioned secrets."
Answer: 4702.0

User story: "Realize the OFC interface classes (in ts_ofc) to let the MTAOS to use. Chris and I discussed and defined the interface classes in the last sprint. I plan to realize them for Chris to be able to use with the real calculations instead of interface only. This is the phase 1 of task."
Answer: 37449.0

User story: "Use the yaml format instead of txt format to do the configuration file management. The yaml is the standard in DM team for the configuration files. Since I never use the yaml before, this task will take some time for me to learn the use of yaml with Python."
Answer: 16181.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Update the ts_tcs_ofcPython to use the DM repository template. This will use the eups to do the package management and scons to build the repository. This is a preparation to put the AOS modules into the scientific pipeline (this means the user can use 'eups -k -r .' to declare the module). This task will also need to modify the code to fulfill the PEP-8 coding style."
Answer: 16186.0

User story: "Perform file transfer tests to simulate image data transfer from the Chilean data center to the {{us-central1}} bucket. Note that ingest is free so the transfers did not cost us anything.     "
Answer: 26.0

User story: "Review documentation procedures and perform installation of time server onto Summit network."
Answer: 1510.0

User story: "Relayout the TAP search panel UI according to the screen shot attach.   * Target area and table area division should be about 40/60 and resizable    * Add help the indicates one-way to ADQL query panel       |Change layout according to attached mock-up.   * TAP search panel is now resizable   * Bottom section is expand/shrink when resizing   * Column constraint toolbar is separated and placed on top for better symmetry   * Message added to Advanced ADQL panel to warn user of lost query when switching back to Basic   * Added loading mask to Select Constraints when waiting for data to be loaded|    TODOs: * All labels should be reviewed.   *    ** Submit change request as needed.    Known Issues: * Left panel of Constraints (spatial/temporal section)   *    ** Has awkward alignment when expanded   ** Horizontal scrolling will not appear when shrink   ** Minor, collapsible icon and label not aligned   * Service Provider is default to {{IRSA}}, but is not shown in input field.|            "
Answer: 7026.0

User story: "Do the following:   * Make spacial selection more narrow, work with [~<USER> on DM-18122   * Add validation to the target panel validation   * Add feedback on the disclosure bar    * remove All sky option   * Note- if column field is not defined the section is invalid or not used.   * optional: Add checkbox on disclosure bar if panel is in use.   ** needs UI discussion     "
Answer: 16116.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: "03/07/2019    Implementation details from https://github.com/Caltech-IPAC/firefly/pull/762   * Positional and temporal columns fields now behave similarly to column selection fields in charts   * Made the search for suggestions case-insensitive. (The field value is case-sensitive though, and must match column name exactly to pass validation.)   * Column constraints and selections are now independent of what is visible in column constraints table   * Cleaned column constrains selection, no field is necessary.   * TAP search requests are not cached (per Xiquin's request). New search will produce new asynchronous request.   * Added error reporting, but did not fix filter validation partially working - will move to a relevant ticket. (Filter validation is done in FilterInfo.conditionValidatorNoAutoCorrect)   * Removed unimplemented features from the UI.   * CADC TAP service should now work. (Switched to https.)         02/28/2019    Do the following:   # Update column constrains table   • which columns are _visible_ in the constraints table (i.e., the table filters) should not affect the query   • the checkboxes should control what’s in the `SELECT` clause   • rows with `principal!=0` should have their checkboxes checked when the constraints table is initially loaded   • instead of a stateful “all vs. principal” menu, we should have a _button_ that can be used to reset the checkboxes to that initial state, e.g., “Select principal columns”   # Modify UI to use column selection suggestion box.   # Constraints column validation is only partially working. It check for syntax(op vals), like in 2,3,4 but, not their content.. in this case, it would fail since it should be written in (2,3,4). Can be moved into a separate ticket."
Answer: 10387.0

User story: "{{ap_verify.py}} originally had built-in support for SQuaSH upload, but it was removed in DM-16536. The frequently used {{--silent}} command-line argument, which disables SQuaSH upload, was deprecated.    Remove the deprecated {{--silent}} argument after Science Pipeline release 18.0 but before release 19.0."
Answer: 334362.0

User story: "Do release 19.0.0 of science pipelines"
Answer: 405259.0

User story: "The final drafts of use case and requirement documents were initially reviewed by selected, internal reviewers and KT. The goal is to address issues raised by those reviewers."
Answer: 1.0

User story: "Right now, if the ADAM device is sending a voltage signal to the KiloArc, it will continue to send that signal until it receives a command to stop. The failure mode we are concerned about is, what happens if the CSC loses its connection to ADAM or crashes. Is there a way to detect that from the ADAM device, and stop sending the power signal as a result? This task is to investigate this. If there is not, then the higher level Illumination CSC will need the ability to cut power to the ADAM device, to ensure that the KiloArc can be gracefully powered down in the event of a CSC failure."
Answer: 27407.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 current behavior of the tooling (deploy, rebuild, setup) shall not be affected.   * It shall be possible to deploy a specific reference (hash, branch, tag) of scipipe_conda_env.   * It shall be possible to set up a specific deployed environment."
Answer: 204643.0

User story: "Update 17.0 release note including Gen2 deprecation"
Answer: 7084.0

User story: "This ticket is to integrate file and snippet instantiation from [https://github.com/lsst/templates] templates in templatebot (DM-17865) for Slack based handling.    Some of the objectives are:   * Manage local clones of a templates repository in templatebot   * Introspect the templates repository to get a list of file templates and drive the inital template listing from that   * Introspect the cookiecutter.json files of templates to populate the dialog boxes.   * Generate files   * Send files back to a user on Slack (following the proof-of-concept in DM-17865)    This ticket will focus on file templates, rather than projects, since they're simpler both in terms of configurations (typically) and because they don't require instantiating github repositories)."
Answer: 18785.0

User story: "Following a suggestion from R.L., estimate the residuals from gaussian process fitting of MERRA-2 time series.    l[^ctio_O3.pdf]"
Answer: 60729.0

User story: "This task covers the time to review the proposed combined SAL-generated test interfaces."
Answer: 8336.0

User story: "MultiProFit should use a linear fitter when fitting models with linear parameters, namely source/component fluxes. This is already implemented in meas_modelfit for CModel but would be useful any multi-component, single-source model, as well as multi-source fitting."
Answer: 73621.0

User story: "MultiProFit and the COSMOS fitting code (DM-15354) were designed to fit a total flux and ratios for each component in each source, partly so that one could put a prior on the total flux and also fix the total (e.g. to unity for a PSF model). However, it should also support fitting individual component fluxes, particularly to allow for linear fitters (like least squares/NNLS, see DM-18105)."
Answer: 145555.0

User story: "To develop statement of work that leads to generate purchase order for getting Linux upgrade software to be utilize in main telescope HVAC system"
Answer: 170449.0

User story: The parquet tables written from within {{pipe_analysis}} currently still use the {{Filenamer}} hack to get the filename.  As we now have a way to write parquet tables as butler datasets, we can make these tables butler datasets and properly "put" them.  Most significantly, this will enable them to be loaded with a butler.
Answer: 1708.0

User story: "While working on DM-10156, I found that it would in fact be useful to have a factory function that took the {{Calib}}-style {{fluxMag0}}/{{fluxMag0Err}} and returned a {{PhotoCalib}}. I implemented it on that ticket, but it stands alone, so I'm going to cherry-pick it here to save the poor reviewer of DM-10156 a little bit of effort."
Answer: 9933.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: "ATPtg and likely MTPtg subscribe to some SAL topics at need, rather than at startup. This results in a serious loss of reliability because the component may fail when subscribing if some remote has a mismatched SAL library. Thus the pointing component can be running just find and suddenly fail. I believe all CSCs should subscribe to all topics they use at startup, so any such error is caught as soon as possible."
Answer: 252729.0

User story: "(placeholder for steps towards running the full HSC-RC2) "
Answer: 133957.0

User story: "Create Verification Elements for LSP requirements and synchronize them to Jira."
Answer: 15719.0

User story: "Deliverable is a linearity model for each amplifier in the AuxTel sensor for its current configuration. Having some code to easily recalculate it is important, as this will surely change when they start switching/shielding cables etc    This will almost certainly involve getting the LATISS lab-folk to acquire and transfer the necessary data, and will also probably involve talking to Pierre^2 about how to take the type of nice ramp-like frames they presented at the PCWG meeting in Paris.    This will probably be interesting work as this is the first time we will have looked at this type of data.    It may also be hairer than expected, as although there is code in the stack for applying linearity correction, I don't think it has been exercised much, if at all. (A good start would be checking if every single obs_package has {{isr.doLinearize=False}} in its ISR config, and if that is the case, expect complications.)"
Answer: 596588.0

User story: "Deliverable are the gains for the AuxTel sensor in its current configuration. Just a dict of the amp names and the gain values is fine.    There is already at least one, if not two tasks in the stack which can run a basic PTC analysis. The one in {{cp_pipe}} will need slight tweaking to not fit a straight line to an obviously (at least) quadratic function, and take the linear coefficient for the gain, but that should be quite easy.    This might involve getting the LATISS lab-folk to acquire and transfer the necessary data."
Answer: 314241.0

User story: "Follow the {{obs_subaru}} pattern for having a .dat file which holds the locations of bounding boxes per-chip and turns them into fits binary tables at scons-time for retrieval by the butler, so that it works for {{isr.doDefect=True}}/"
Answer: 53036.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: "Deliverable is the crosstalk matrix for the AuxTel sensor in its currently frozen configuration, in the right format for it to be applied by ISR. Having some code/a notebook to easily recalculate it for when they change the config would be nice, but note this does not require writing this as a proper task, but some reusable code would be nice outcome.    I believe Robert has code that should be able to do this from cosmics in darks, and we have some long darks on lsst-dev (though not ingested, and lacking the headers to ingest them without a little hacking).    Could also do this from some of the spots.    Should *NOT* be done from the noise correlation - we know there is a lot of pickup, and this isn't the same thing anyway."
Answer: 600988.0

User story: "Create Alert Packets from the DIA table."
Answer: 92599.0

User story: "Understand numerical description data (size of files, required RAM and disk space)"
Answer: 92597.0

User story: "Begin working with BVan to get JWT auth working in JH."
Answer: 4381.0

User story: "- create GKE cluster for [~selles]  - load data inside GKE cluster  - study logs for qserv and dataloader"
Answer: 62016.0

User story: "{{lsst_dm_stack_demo}} uses an astrometry.net reference catalog. In order to remove a.net support from the stack, we need to convert this refcat from a.net format to HTM Indexed format. [~<USER> claimed he had some code to do such conversions in the past.    Converting the existing refcat is probably better than creating a new refcat because any changes to the refcat contents would be reflected in changes in the demo output, and we don't want to have to go and vet those changes again."
Answer: 360101.0

User story: "Three packages have an eups table dependency (Optional or Required) on {{meas_extensions_astrometryNet}}:  {{jointcal}}, {{obs_monocam}}, and {{pipe_tasks}}. As part of removing a.net support from the stack, we can start by removing those dependencies."
Answer: 528836.0

User story: "Review LDM-503, and ensure that each L2 milestone has a coherent description of what it involves.    For most of them, this will likely involve checking in with the relevant milestone ”owners” — see the list of action items from the [Nov 2018 DMLT|https://confluence.lsstcorp.org/display/DM/DM+Leadership+Team+Face-to-Face+Meeting%2C+2018-11-06+to+08]."
Answer: 425389.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: "03/12/2019 CADC TAP service was added to the list of Firefly TAP services.    [http://www.cadc-ccda.hia-iha.nrc-cnrc.gc.ca/tap/] is often unresponsive, when called from IPAC. CADC #75724 was created for this issue with the following response from Patrick Dowler at CADC:       {quote}  We have been able to reproduce this and it seems to be a strange network issue... could be some network security equipment near our end. We did also discover that https seems to resolve it and we have recently converted all our web services to use https only (in the capabilities docs - not yet propagated in IVOA registries)    I don't think we will be able to solve this for http but https appears to work so I will close the ticket. Thanks again for bringing it to our attention - I found evidence in logs that it also effected other services as well.{quote}       Firefly is now using     [https://www.cadc-ccda.hia-iha.nrc-cnrc.gc.ca/tap] end point.         02/22/2019    Please add the CADC TAP service at [http://www.cadc-ccda.hia-iha.nrc-cnrc.gc.ca/tap/] as soon as reasonably possible to the standard list of TAP services in the Firefly TAP search screen. This is a very useful service for testing, both because of content and because it's based on the same code that [~<USER> is using for the LSST TAP service.    This service has both ObsTAP (ObsCore format, table {{ivoa.ObsCore}}) and CAOM2 image metadata collections, which are a valuable resource for our development.    At this moment, something goes wrong when trying to manually access this service. The message  {quote}Failed to get schemas for [http://www.cadc-ccda.hia-iha.nrc-cnrc.gc.ca/tap/:] Error: Error from Server for command tableSearch: code: 504, text:  {quote}  appears. However, I can verify manually and/or with TOPCAT or [http://saada.unistra.fr/taphandle?url=http%3A//www.cadc-ccda.hia-iha.nrc-cnrc.gc.ca/tap/] that the {{TAP_SCHEMA.schemas}} table is available."
Answer: 26070.0

User story: "Science pipelines documentation    [https://pipelines.lsst.io/install/prereqs/debian.html]    need to be updated to ensure that a newer gcc compiler is used when compiling lsst_distrib in Ubuntu installations.     "
Answer: 8442.0

User story: "The white light source needs to continuously read four analog channels on the ADAM 6024 device, which the KiloArc device uses to signal errors and some additional information about the hardware state. My test hardware can only simulate a signal on one channel at a time, and I discovered that my assumptions about how I would read the other channels are apparently wrong. It's possible that this component could work with only one channel (the error signal) but I'd like to figure out what's amiss."
Answer: 11403.0

User story: "WLS CSC needs to implement state transitions:    -upon receiving relevant SAL commands    -upon receiving an error signal from the KiloArc hardware    -in the event of communication loss between host computer and ADAM hardware"
Answer: 98373.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: "Add a new section to https://sqr-029.lsst.io/ describing how we use Terraform and Helm to deploy the DM-EFD.  "
Answer: 17.0

User story: Using a bleed version of the conda environment, meas_modelfit test TruncatedGaussianTestCase is failing       h3. Error Message    AssertionError: True is not false : 1/4 elements differ with rtol=2.220446049250313e-16, atol=2.220446049250313e-16 2.500000000000001 != 2.5 (diff=8.881784197001252e-16/2.500000000000001=3.5527136788004996e-16)  h3. Stacktrace    {{self = <test_truncatedGaussian.TruncatedGaussianTestCase testMethod=test2d> def test2d(self): if scipy is None: return for i in range(5): x = numpy.linspace(-1, 1, 5) model = numpy.zeros((x.size, 2), dtype=float) model[:, 0] = x model[:, 1] = x**2 + x data = numpy.random.randn(x.size) + model[:, 0]*0.9 + model[:, 1]*1.1 q0 = 0.5*float(numpy.dot(data, data)) gradient = -numpy.dot(model.transpose(), data) hessian = numpy.dot(model.transpose(), model) sigma = numpy.linalg.inv(hessian) > self.assertFloatsAlmostEqual(numpy.linalg.inv(sigma), hessian) tests/test_truncatedGaussian.py:161: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ ../../stack/Linux64/utils/16.0-18-g0a50484+1/python/lsst/utils/tests.py:735: in assertFloatsAlmostEqual testCase.assertFalse(failed, msg="\n".join(errMsg)) E AssertionError: True is not false : 1/4 elements differ with rtol=2.220446049250313e-16, atol=2.220446049250313e-16 E 2.500000000000001 != 2.5 (diff=8.881784197001252e-16/2.500000000000001=3.5527136788004996e-16)}}  {{  }}  {{  }}
Answer: 7418.0

User story: "While autograd will allow us to implement a new way of calculating our models, the machinery of using FFT convolutions and Lanczos 3 for resampling can be easily implemented by updating `transformation.py` in scarlet to use FFT convolution instead of a pure convolution method in C++.  This ticket will include work to use the faster FFT convolution to improve processing time in scarlet and will include an ipython notebook demonstrating the improved performance."
Answer: 35952.0

User story: Steve Kahn asked for a "paragraph" on image security by next week.
Answer: 4345.0

User story: The docs still have an old example of how to run ap_pipe    {code}  ap_pipe.py repo --calib repo/calibs --output path/to/put/processed/data/in -c associator.level1_db.db_name=ppdb/association.db --id visit=123456 ccdnum=42 filter=g --template path/to/templates  {code}    This needs to be updated to something closer to    {code}  ap_pipe.py repo --calib repo/calibs --output path/to/put/processed/data/in -c -c ppdb.db_url="sqlite:////absolute/path/to/database" -c ppdb.isolation_level="READ_UNCOMMITTED" --id visit=123456 ccdnum=42 filter=g  {code}
Answer: 513388.0