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: Currently, we track bugs and issues through JIRA, which is only accessible to project members.    We also have a per-repository issue tracker on GitHub. These are open to the public. According to [DMTN-020|https://dmtn-020.lsst.io/#receiving-bug-reports] (NB still not formally approved at time of this writing), T/CAMs will monitor the GitHub trackers and transfer information back and forth between them as necessary.    Currently, the rate of tickets being filed on GitHub is very low. Since the threshold to reporting issues on GitHub is minimal, though, it seems reasonable to expect that this will increase in future. We might also expect that, as community interest in the LSST stack grows, and increasing number of less technical users will attempt to get our code working, run into problems, and file GitHub tickets that do not represent "real" bugs, but rather misunderstandings or user errors.    We also have the [LSST Community|https://community.lsst.org] forum. Currently, queries there are handled by interested readers on a best-efforts basis. Occasionally, they uncover issues which can be fed into JIRA. As our science community expands, the total number of support queries seems likely to quickly balloon beyond what the residents experts can handle informally. This is a problem in at least two ways: it will be hard to be responsive to the community, and we risk having our expert developers distracted into providing user support rather than working on core development. Further, sorting the important bugs from the mass of general support requests may become untenable.    Please define policies and resourcing for providing appropriate end-user facing support while ensuring that key bug reports are handled appropriately.
Answer: 1088306.0

User story: "Now that there is a working astrometrySourceSelector (just merged in meas_algorithms from DM-5933), we should get matchOptimisticB working with it. This would entail replacing matchOptimisticB.SourceInfo with AstrometrySourceSelectorTask and tweaking the latter to do whatever matchOptimisticB needs, and removing SourceInfo."
Answer: 292281.0

User story: "SQR-012 provides details of how the new unittests should be written, but it only gives an example of the old testing boilerplate in the introduction. It would be very helpful to have the first thing a reader sees be the new, correct, boilerplate, so they can immediately drop it into a new testing file."
Answer: 67406.0

User story: "Required by 2016-07-12."
Answer: 31331.0

User story: "While working on DM-4202 it became apparent that the aperture corrections calculated and applied by CModel were too large. This ticket is intended to trace down where the failure is occurring and correct it."
Answer: 12958.0

User story: "Perform a quality analysis on the LSST processing of the RC dataset (DM-6816) in the same way as would be performed before an HSC data release."
Answer: 228962.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Using the script enhanced in DM-6588, compare HSC and LSST (DM-6816) processing of the RC dataset."
Answer: 222899.0

User story: Process the "RC" dataset used to verify HSC data releases through the LSST stack using the configuration specified by DM-6815.
Answer: 210381.0

User story: In preparation for running an end-to-end comparison of large scale processing with the HSC and LSST stacks, we need to update the configuration to reflect currently understood best practice.    In general, we expect the default HSC configuration to be better understood and "battle-tested" given that it has been used for science-grade data releases.    Audit the default configuration of the full LSST stack (from ProcessCcdTask through multiband coadd processing). Where LSST defaults differ from HSC, update the LSST configuration to match the HSC equivalent unless there's a clear reason why LSST's default should be different. When it's not appropriate to update the LSST configuration, add an override to obs_subaru.    In some cases, the LSST and HSC stacks have diverged so that a direct transfer of configuration options isn't possible. Where an equivalent can be found, take advantage of it. Otherwise, stick with existing LSST defaults.
Answer: 112250.0

User story: "The scan schedulers are vulnerable to slow queries in that all queries on a scheduler can be held up by a single slow query. There needs to be a method of detecting slow tasks so they can be removed from a scheduler (allowing the scheduler to continue) as well as move an entire user query to the snail scheduler if it contains too many slow tasks. "
Answer: 120999.0

User story: "Review data to migrate and map out plan."
Answer: 170041.0

User story: "Design disaster recovery plan for science datasets."
Answer: 223294.0

User story: "meas_extensions_ngmix has no useful documentation, not even a {{doc}} directory. Add some.    This should include at least an overview of the package contents, a description of its capabilities, and instructions on enabling it within the meas_base framework. The package should have a README."
Answer: 43624.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: "Our code is built using scons, with our own set of extensions in the form of the sconsUtils package. sconsUtils is not well documented and requires ongoing maintenance (see, e.g., DM-6721). It was originally written by Science Pipelines (and, indeed, still carries a README directing queries to Science Pipelines developers), but the pipelines groups are not scoped to assume continuing responsibility for it. Most work recently has been performed by Architecture and SQuaRE, but this largely consists of relatively minor fixes: it's not clear that anybody assumes responsibility for the high-level structure and direction of this package.    The above text focuses on scons & sconsUtils, but it's possible that more dramatic evolution of the build system will be necessary during construction: this also includes investigating and leading the adoption of other tools if & when necessary.    Worth noting that this relates to, but is not the same as, the work on EUPS described in DM-6335."
Answer: 142864.0

User story: "Currently afwMath.convolve does not have an in-place operation option, thus always requires at least double the memory. Apparently SDSS had an in-place version, and we should include that capability for LSST processing."
Answer: 1883740.0

User story: "The deblender sometimes gets into trouble with cluster galaxies, and the deblended fluxes aren't accurate.  In that case it helps to have measurements on the image without any deblending having been performed.  This is a feature used in HSC's mid-2016 production run afterburner, ticket [HSC-1400|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1400].  This feature should be ported for use in LSST."
Answer: 140849.0

User story: "HSC has a new measurement extension: meas_extensions_convolved.  This performs aperture photometry with the PSF degraded to nominated seeings (similar to how galaxy photometry is commonly done these days).    Relevant HSC tickets are [HSC-1395|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1395] and [HSC-1408|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1408]."
Answer: 141117.0

User story: "DM-6302 adds support for custom exception translators to pybind11. However exceptions mapped do not inherit from Python {{BaseException}} or higher. This prevents exceptions from being raised and caught with {{except Exception as e}} in Python. This behaviour also occurs with Boost Python and Swig (we hack around it with a pure Python wrapper).    This ticket aims to solve the problem by adding support for inheritance from Python exception types to pybind11."
Answer: 24456.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: "Looking up keys by string,  {code}src['somefield']{code}  is about 60x slower than pre-computing the key and using that,   {code}  key=src.schema.asKey()  src.get(key)  {code}  We should be able to cache those keywords in a dict to normalize that access speed and so that users don't have to deal with pre-defining and carrying around a bunch of keys.    I'll attach a simple ipython file that demonstrates the speed difference. The output of one run of it is shown below:    {code}  $ ipython field_key_timing.py  Small schema, string lookup  1 loops, best of 3: 214 ms per loop  Small schema, asKey() lookup  100 loops, best of 3: 3.35 ms per loop    Large schema, string lookup  1 loops, best of 3: 201 ms per loop  Large schema, asKey() lookup  100 loops, best of 3: 3.18 ms per loop  {code}"
Answer: 2068139.0

User story: "The sizeMagnitudeStarSelector is still in meas_algorithms, but it is unused and likely no longer works. We should either remove it, or update it to be fully supported.    The same holds true for any other C++-based star selectors we still have lying around."
Answer: 135151.0

User story: "Write up list of concerns, including new requirements, clarifications, pipeline staging requirements (both pre and post execution), and any inconsistencies to better inform requirements for batch production services."
Answer: 93707.0

User story: "Consolidated and wrote up typos and comments."
Answer: 93707.0

User story: "Go through document to seek out all references to workflow and orchestration to find any additional requirements, or things to be clarified.  "
Answer: 93708.0

User story: "Go through document to seek out all references to all inputs/outputs listed for each pipeline."
Answer: 93708.0

User story: "Examine LDM-151 (and its updates), LSE-141, LSE-68 for information regarding orchestration, workflow, and pipeline inputs/outputs."
Answer: 93710.0

User story: " Dividing F16 Service Management  ~ monthly."
Answer: 92329.0

User story: " Dividing F16 Service Management  ~ monthly.  "
Answer: 45981.0

User story: "Dividing F16 Service Management  ~ monthly."
Answer: 4546.0

User story: "Based on project-level and DM-level goals of batch production services, break down goals and work to achieve those goals at each service layer, integrated in a phased deployment plan for Batch Production Services."
Answer: 226298.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: "Convert a {{CmdLineTask}} into {{SuperTask}} so it can be run under an Activator.      ----    This ticket adds three tasks that can be run with the CmdLineActivator. They are the three subtasks of {{ProcessCcdTask}}. To run them with the {{obs_test}} data:     {code:java}  cmdLineActivator superIsrTask --extras $OBS_TEST_DIR/data/input/ --config doDark=False --output testOutputDir --id  cmdLineActivator superCharacterizeImageTask --extras testOutputDir --output testOutputDir --id  cmdLineActivator superCalibrateTask --extras testOutputDir --output testOutputDir --id  {code}    This ticket is only meant to provide a real-life example for future SuperTask+workflow work, and not meant to be any recommended way to run ProcessCcd at this moment, as the scientific details are not verified here, and implementation+API will change in the future as the design matures.  Also processing codes here are duplicated from pipe_tasks and will rot very quickly until the team commits to keep the SuperTask version up to date with other developments.    "
Answer: 111277.0

User story: "Select an existing CmdLineTask to be converted to the current SuperTask framework as a workflow example "
Answer: 89313.0

User story: "Examine existing process_ccd pipeline and record inputs and outputs. Document how we want to store inputs/outputs so that it can be implemented."
Answer: 226249.0

User story: "Attend camera workshop, Meeting did not fully address the need.  Travel to SLAC."
Answer: 3.0

User story: "These are the changes to support defalt chart and single chart type (as for IRSA release)  - Remove chart selection from chart area  - Use dropdown for chart selection (can be omitted if single chart type is used)  - Populate current values in chart options  - Support Clear and Reset in chart options  - For tables, connected to charts, if no default parameters are specified, default chart is an XY plot with CATALOG_COORD_COLS (used to produce an overlay) for catalogs or two first numeric columns for other tables.  - Label, matching column expression, and unit, matching table model, are default parameters for both app and api now.  "
Answer: 1545.0

User story: "As of DM-6127, we've clarified the licensing position of ngmix. Please ensure that we're actually carrying a version of ngmix which has a license attached in our repository."
Answer: 2720.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "In the meas_base framework, we independently define an enumeration of available flags [(e.g.)|https://github.com/lsst/meas_extensions_photometryKron/blob/cba01575dab0cd609c7e2a3f3d08632b94f97f58/include/lsst/meas/extensions/photometryKron.h#L82] and a set of table fields for storing flags [(e.g.)|https://github.com/lsst/meas_extensions_photometryKron/blob/cba01575dab0cd609c7e2a3f3d08632b94f97f58/src/KronPhotometry.cc#L422]. We implicitly assume that these are declared in the same order, but do not, in general, enforce this.    In DM-6561, these were found *not* to be in the same order in meas_extensions_photometryKron. Setting a flag based on a bad result would therefore set the wrong flag in the output table.    In the DM-6561 solution, we introduced a test for this which is specific to the photometryKron codebase. However, the basic structure of the test would be easily extended to cover all meas_base plugins to ensure this error can never occur. Do so."
Answer: 315619.0

User story: Our Python coding standard informs us that ["{{is}} and {{is not}} SHOULD be used when comparing to {{None}}"|https://developer.lsst.io/coding/python_style_guide.html#is-and-is-not-should-be-used-when-comparing-to-none]. A couple of lines later, however, it tells us that ["{{if x}} SHOULD NOT be used when you mean if {{x != None}}"|https://developer.lsst.io/coding/python_style_guide.html#if-x-should-not-be-used-when-you-mean-if-x-none].    Since I am following the first rule, I *never* mean {{if x != None}}.
Answer: 91389.0

User story: "As summary. Necessary to run meas_extensions_ngmix through Jenkins."
Answer: 175.0

User story: "I would very much like to see a report on the outcomes and discussion from the LSST in Europe meeting.  I think [~<USER> is probably the right person to delegate this."
Answer: 322761.0

User story: "To test out processing at modest scales (~ 100 -- 1000 cores)  utilizing Shifter+HTCondor on machines like BW, organize processing (processCcd of obs_sdss) of stripe82 data similar to that used in the lsst_dm_stack_demo (run=4192 field=300)."
Answer: 225875.0

User story: "Work on preliminary specific additions to the camera interaction ConOps took place this month during attendance at the Camera Workshop"
Answer: 1657.0

User story: "Proper acknowledgements began being added to the messaging system this month."
Answer: 1649.0

User story: "Message types for system bookkeeping acknowledgements as well as report messages were added to the existing dictionary and the means for acting upon these message types are being added to component prototype code.  In addition, needed changes were made to the existing dictionary so all reporting entities write more complete details to their report message queues."
Answer: 60947.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 story addresses the need to separate the processes that connect to the DAQ and retrieve the image data from the processes that forward the image data to NCSA. Requirements for this component and the component that formats the image data into a file which includes associated metadata were discussed at length during the Camera Workshop this month. Prototypes for these component processes are underway."
Answer: 60955.0

User story: "Identify startup processes to be monitored for health and to provide notification for startup failure."
Answer: 60973.0

User story: "At the Camera Workshop in Mid-June, OCS Team members suggested that DM pull down their Service Abstraction Layer software and gain familiarity with it. The User manual is being studied before compiling the software and running it with DM software as a means of simulating planned Telescope & Site processes and how DM will interact with them.  Most of the work for this epic will be conducted in August. This story captures our prep work."
Answer: 142814.0

User story: "Respond to RFC comments and update RFC as needed."
Answer: 95539.0

User story: "Write up and submit RFC."
Answer: 95541.0

User story: "Discuss elements of workflow RFC (technical details, scope, requirements)."
Answer: 95543.0

User story: "Based on use cases/requirements gathered in DM-6270 and evaluation reports completed in DM-6276, select workflow system."
Answer: 95544.0

User story: "While working the unit test for Projection in java and javascript, I feel that ImageHeader.java may need some work to refactor it.  It will be better it is more resemble the Header in FITS library.  The ImageHeader has many public instance variables.  However, it does not have any utilities method such as get/set etc.       Two methods were added for running unit tests.  In the long run, if we have time, it is good to refactor it since it is public now."
Answer: 136178.0

User story: "Respond to SuperTask RFC based on requirements"
Answer: 231646.0

User story: "Specify requirements for SuperTask extensions according to the use cases and architecture."
Answer: 231647.0

User story: "Discuss elements of RFC (technical details and scope)."
Answer: 66119.0

User story: "Based on articulated design, revise WBS to incorporate phase."
Answer: 250144.0

User story: "Articulate the design created in (DM-6697) into the format needed for planning."
Answer: 250154.0

User story: "Produce functional design breakdown from the revised conops (DM-6696)."
Answer: 250163.0

User story: "Revise the Level 1 conops to incorporate the minimal required functionality of Level 1 Services: minimal data archiving of camera data and minimal transport via data backbone to NCSA."
Answer: 100451.0

User story: "Based on the batch services conops, develop a list of engineering considerations for making a BOE for the batch services planning package."
Answer: 100488.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "When the batch production services conops is in a solid state, convert the Google doc to reStructuredText and deliver to DM design document repository in github."
Answer: 60368.0

User story: "Review raw draft of concept of operations for the batch processing services to work through underdeveloped areas, clear up uncertainties, and make readable."
Answer: 60380.0

User story: "Write a raw draft of the concept of operations for batch processing services. In this iteration the document is developed in Google docs following the ConOps template."
Answer: 8401.0

User story: "Based on the L3 Hosting services conops, develop a list of engineering considerations for making a BOE for the L3 Hosting planning package."
Answer: 100494.0

User story: "Submit the document for TCT change control. Process is TBD.    If it is not accepted by TCT, further work is not in the scope of this epic, and would need to be planned in the EV system."
Answer: 100499.0

User story: "Factor Level 1-specific information into Level 1 uber-conops, and consider documentation structure."
Answer: 100860.0

User story: "Review first draft of Service Monitoring conops within Data Processing Architecture working group, bringing in relevant experts.    Input from review is incorporated into a second draft.  "
Answer: 100676.0

User story: "Provide high-level context for service-level monitoring with respect to components and business needs. Create diagram. Provide one worked out case of high-level requirements in the context of the Level 1 system."
Answer: 100484.0

User story: "Write a raw draft of the concept of operations for service monitoring. In this iteration the document is developed in Google docs following the ConOps template."
Answer: 100483.0

User story: "  "
Answer: 100501.0

User story: "Submit the document for Systems Engineering change control.    If it is not accepted by SE, further work is not in the scope of this epic, and would need to be planned in the EV system."
Answer: 89003.0

User story: "When the AA services conops is in a solid state, convert the Google doc to reStructuredText following DM's documentation versioning process."
Answer: 28493.0

User story: "Review first draft of AA services conops within Data Processing Architecture working group, bringing in relevant experts.    Input from review is incorporated into a second draft.  "
Answer: 28494.0

User story: "Review raw draft of concept of operations for the AA services to work through underdeveloped areas, clear up uncertainties, and make readable."
Answer: 7.0

User story: "Write a raw draft of the concept of operations for authentication and authorization services. In this iteration the document is developed in Google docs following the ConOps template."
Answer: 4.0

User story: "Submit the document for TCT change control. Process is TBD.     If it is not accepted by TCT, further work is not in the scope of this epic, and would need to be planned in the EV system."
Answer: 100536.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "We are going to have a PDAC set up at NCSA at the end of F16. Current plan is to give access to everyone in LSST project. We would also like to have some outside users to have access to the system to give us feedback.     Who should have the access to PDAC?"
Answer: 322558.0

User story: "While working on DM-6438 (set up unit test for projection in JavaScript), we realized we should have a parallel unit test system set up for Java code, to keep the two systems in sync. "
Answer: 136939.0

User story: "in 2015 iPlant was rebranded to CyVerse  (http://www.cyverse.org/) with a revised mandate to serve all life sciences.  CyVerse's  Data Store is based on technology iRODS (http://irods.org/).   CYVerse's Atmosphere provides a managing portal for users's VM instances and data spaces called volume. The instance and volume is tied under a project.     There are other tools and UIs under CyVerse. Data Store and Atmosphere are very close to what we wanted  for LSST workspace.  It provides many VM instance images preconfigured for life sciences domain-specific tasks. We could definitely learn from this if LSST provides the VM for its users.  LSST could supply instance images with specific astronomical tools preconfigured.      Deciding if the CyVerse could be used as LSST workspace implementation will need much more study and discussion with other teams involved in workspace design and implementation.     The direction we are going with Jupyter Notebook and JupyterHub most likely preclude us from using CyVerse directly.   "
Answer: 188426.0

User story: Per the [February 2016 JTM|https://confluence.lsstcorp.org/pages/viewpage.action?pageId=44138708], provide the Data Access group with a specification for "in Butler catalogue joins".
Answer: 1940419.0

User story: "* default  symbol size, shape,and color setting is different from that of original version.  * no XY Plot Options pop-out windows  *  the plot displays non-ascii characters on the panel (for example:  Fit  )  * miss Filter Dialog on the plot panel comparing with the original version.  *  does not accept default column names for the plot."
Answer: 122135.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: "*-for external image viewer, the default RangeValues causes problem, i.e. other defaults not set-. (FIXED)  *-global default does not always apply to external image viewer-(FIXED DM-7016)  The Gator implementation related to coverage map   (1) default symbol size, shape, color setting is different from that of original map   (2) cannot specify the shape, size, and color through API;   (3) cannot specify the shape, size, and color of a search center through API;   (4) -does not display any image and source when the table has only one ra,dec values, for example:  one table with one position value or one table with many records but has the same ra,dec values.- MOVED to [DM-7001]   (5) -the sources on coverage map are not clickable. However, on table and plot are clickable and work fine.- (FIXED)  more issues:    Other issue    - -It's possible to select distance tool and then area selection. First drag would define area selection, all the following line. A click would be defining a 0 length line, even if point selection is enabled.- _Can't repeat, i think this is fixed._"
Answer: 121010.0

User story: "There is no test for imageDifference.py. Create one."
Answer: 2.0

User story: "When a dialog such as catalog search is displayed, it should be able to pick up the active target or the coordinates from a highlighted row in a table. Please, implement the mechanism that will automatically pick up those coordinates and pre-fill the search form for you."
Answer: 341676.0

User story: DM-5988 introduced a hack in reading the raw files: we use a database to cache metadata from the shutter files and update the camera files at read time.  The camera files have now been "sanitised" (updated with the appropriate metadata), and it's time to remove the hack.    [~<USER> writes:  {quote}  Data is on lsst-dev in:    /nfs/lsst2/photocalData/data/monocam/sanitised9/1m3/1m3    Raw calibs are in:    /nfs/lsst2/photocalData/data/monocam/sanitised9/1m3/calibs    Regarding what I want: everything to be the same, but with a normal ingest, i.e. no splicing, just taking everything that is needed from one set of files. Some points to note:    * should be able to ingest all the raws and calibs files, and register their OBJECT types to allow processing with these as ids (inc. pipe_drivers scripts)  * pipe_drivers master calib scripts should still run (and their outputs still be ingestable)  * processCcd should run  {quote}
Answer: 187085.0

User story: "Reviewed https://github.com/lsst/LDM-PMT/blob/integration/index.rst and https://dmtn-020.lsst.io/v/DM-6447/    Made extensive markup of LDM-PMT,  delivered to <USER>  Assessed DM-6447,  which show promise of an actual workable manual, though not complete."
Answer: 11673.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-2674 involves getting HSC's {{meas_mosaic}} working with the LSST stack.  This issue consists of adapting the analysis.py script of DM-4393 & DM-4730 to (optionally) apply the astrometric and photometric solutions derived running {{meas_mosaic}} to the individual visits before comparison.  This is useful in general and is specifically useful in comparing the {{meas_mosaic}} results between the HSC and LSST stacks."
Answer: 160335.0

User story: "Review CloudSlang against criteria defined in the epic.   http://cloudslang-docs.readthedocs.io/en/v0.9.60/index.html"
Answer: 62130.0

User story: "Review [pinball|https://github.com/pinterest/pinball] workflow management system."
Answer: 62133.0

User story: "Review Makeflow against criteria defined in the epic.   http://ccl.cse.nd.edu/software/makeflow/"
Answer: 11519.0

User story: "Review [RADICAL-Pilot|http://radicalpilot.readthedocs.io/en/latest/index.html] against criteria defined in the epic."
Answer: 11547.0

User story: "Create a detailed checklist for developing the planning packages for the replan and WBS restructuring."
Answer: 1841.0

User story: "Using the {{assertXxNearlyEqual}} methods for exact comparisons is a bit confusing, even if it works (if you set {{atol=0 and rtol=0}}).  On this ticket I'll add simple variants whose names don't imply an approximate comparison and just delegate to the {{NearlyEqual}} variants with zero tolerances.    Doing this now so I can use it on DM-6631.  "
Answer: 1560.0

User story: "IsrTask is a command-line task, but its run method does not take a dataRef (it instead has a {{runDataRef}} method.  This is inconsistent with other {{CmdLineTasks}} and more importantly breaks {{parseAndRun}}.    I'm committing a small workaround on DM-6631 to get {{parseAndRun}} working, but the ultimately method names should be made consistent across CmdLineTasks.  That will require an API change and hence an RFC."
Answer: 1185281.0

User story: "Had a bug where {{utils.auto_slugify_edition}} did not replace underscores with a dash, and therefore failed {{utils.validate_path_slug}}. This created a silent breaked where a branch like {{u/<USER>r12_patch1}} did not get an edition created for it.    This ticket adds this replacement code and adds a test for such a case."
Answer: 48.0

User story: "This ticket contains no work, but is blocked by all tickets which should be addressed before DMTN-020 fully reflects the work of the PMP-WG."
Answer: 226209.0

User story: "Expand https://dmtn-020.lsst.io/v/DM-6447/#jira-maintenance to describe best practices for T/CAMs working with JIRA. Include:    * Appropriate labels;  * Teams;  * ... other things?"
Answer: 1829854.0

User story: "Support a means of ingesting index reference catalogs from FITS tables (e.g. SDSS catalogs)."
Answer: 9726.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: "{{validate_drp}} computes metrics and generates JSON that, through the [post-qa|https://github.com/lsst/post-qa] tool, is submitted to the SQuaSH REST API for persistence and display in a web app.    A previous ticket, DM-6086, we bolted on a JSON serialization scheme compatible with SQuaSH. However, this approach was not well integrated with {{validate_drp}}. We want a framework/API where serialization is handled consistently and integrally with metric computations. This includes the semantic serialization of computational parameters and reduced datasets.    This API can be applied beyond {{validate_drp}} as a means for metrics and integration tests to be submitted to SQuaSH as well."
Answer: 56045.0

User story: "Reimplement the image decorrelation as a subtask rather than a direct call to a function."
Answer: 11398.0

User story: CcdImage.cc currently has hard-coded a bunch of {{getSchema().find("base_blah").key}} things. These should either be replaced with "slot_*", config.blahName, or dealt with at a higher level (e.g. not loading all those values directly inside of ccdImage::LoadCatalog).    Once this is done, we should delete the comments at the top of the file.
Answer: 62008.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: jointcal currently fails several of the tests that get run as part of lsst.utils.tests.MemoryTestCase. For example:    {code}  File open: /Users/parejkoj/lsst/lsstsw/stack/DarwinX86/obs_lsstSim/12.0.rc1-2-g80ec5c9/description/defects/defectRegistry.sqlite3  File open: /Users/parejkoj/lsst/simastrom/validation_data_jointcal/twinkles1/registry.sqlite3  F  204295 Objects leaked:  ...  47: 0x114f5aeb0 lsst::afw::table::BaseRecord  46: 0x114f5b410 lsst::afw::table::BaseRecord  45: 0x114f5b370 lsst::afw::table::BaseRecord  44: 0x114f5b2d0 lsst::afw::table::BaseRecord  43: 0x114f5b230 lsst::afw::table::BaseRecord  42: 0x114f5b190 lsst::afw::table::BaseRecord  41: 0x114f5b0f0 lsst::afw::table::BaseRecord  40: 0x114f5b050 lsst::afw::table::BaseRecord  39: 0x114f5afb0 lsst::afw::table::BaseRecord  38: 0x114f5ae10 lsst::afw::table::BaseRecord  37: 0x114f5ad70 lsst::afw::table::BaseRecord  36: 0x114f5acd0 lsst::afw::table::BaseRecord  35: 0x114f5ac70 lsst::afw::table::BaseRecord  34: 0x114f5ab50 lsst::afw::table::BaseRecord  33: 0x114f5aab0 lsst::afw::table::BaseRecord  32: 0x114f5a9d0 lsst::afw::table::BaseRecord  31: 0x114f5a910 lsst::afw::table::BaseRecord  30: 0x114f5a830 lsst::afw::table::BaseRecord  29: 0x114f058f0 lsst::afw::table::BaseTable  28: 0x114f04f28 lsst::afw::table::detail::SchemaImpl  F  ======================================================================  FAIL: testFileDescriptorLeaks (__main__.MyMemoryTestCase)  ----------------------------------------------------------------------  Traceback (most recent call last):    File "/Users/parejkoj/lsst/lsstsw/stack/DarwinX86/utils/12.0.rc1-2-gbf6fe2f/python/lsst/utils/tests.py", line 134, in testFileDescriptorLeaks      self.fail("Failed to close %d file%s" % (len(diff), "s" if len(diff) != 1 else ""))  AssertionError: Failed to close 2 files    ======================================================================  FAIL: testLeaks (__main__.MyMemoryTestCase)  !Check for memory leaks in the preceding tests  ----------------------------------------------------------------------  Traceback (most recent call last):    File "/Users/parejkoj/lsst/lsstsw/stack/DarwinX86/utils/12.0.rc1-2-gbf6fe2f/python/lsst/utils/tests.py", line 118, in testLeaks      self.fail("Leaked %d block%s" % (nleak, plural))  AssertionError: Leaked 204295 blocks    ----------------------------------------------------------------------  {code}    We should track down why these tests are failing, and fix them. I have commented out MemoryTestCase for now, so that CI will run cleanly.
Answer: 456738.0

User story: "We need an integration/validation test for jointcal on lsstSim data, to show that jointcal can run safely on lsstSim data processed through the stack."
Answer: 222083.0

User story: "We need an integration/validation test for jointcal on DECam data, to show that jointcal can run safely on DECam data processed through the stack."
Answer: 234015.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 an integration/validation test for jointcal on cfht data, to show that jointcal can run safely on cfht data processed through the stack."
Answer: 62144.0

User story: "We need an integration/validation test for jointcal on hsc data, to show that jointcal can run safely on hsc data processed through the stack."
Answer: 60647.0

User story: jointcal.py current does things like:    {code}  for dataRef in dataRefs:      if dataRef.dataId["visit"] == int(visit) and dataRef.dataId["ccd"] == int(ccd):          ...  {code}    This is not survey generic, and is probably not the best way to identify data blocks anyway. This, and other non-generic things in jointcal.py should be cleaned up so they work across surveys.
Answer: 234021.0

User story: One should be able to create a LoadAstrometryNetObjectsTask without passing a Config object, if one only wants the default configuration. Currently it raises TypeError:    {code}  Traceback (most recent call last):    File "testJointcal.py", line 79, in setUp      refLoader = LoadAstrometryNetObjectsTask()  TypeError: __init__() takes at least 2 arguments (1 given)  {code}    If the config object really is a kwarg, it should default None and create a default config, so that one doesn't have to do, e.g.:    {code}  LoadAstrometryNetObjectsTask(LoadAstrometryNetObjectsConfig())  {code}
Answer: 200.0

User story: "In the v12_0 release, release notes and a release announcement for the entire DM system (`lsst_apps`, qserv, dax, firefly and doc projects) got lumped into the documentation site for `lsst_apps` (pipelines.lsst.io).    This ticket is a reminder to re-assess this situation, figure out the business needs that motivated it, and to drive a re-factoring of documentation and release notes to the appropriate places so that we have a solid architecture for documentation in the future.    cc. [~<USER>"
Answer: 2219623.0

User story: "[~<USER> wrote an excellent tutorial on command line data processing with HSC data. This is the type of content that’s sorely needed to get new users up to speed with LSST processing.    Naturally this content belongs in the {{lsst_apps}} documentation project, whose URL is currently https://pipelines.lsst.io. I think this tutorial can serve as a nucleus for a set fo ‘First Steps’ tutorials that serve as primers for {{lsst_apps}} before a user dives deeper into the tutorials and API references associated with each package.    With that, this ticket will    1. Migrate DMTN-023’s content to the https://github.com/lsst/pipelines_docs repo and deprecate DMTN-023 (with a link to follow-up)  2. Create a new section in https://pipelines.lsst.io for introductory tutorials  3. Migrate the content  4. Improve the tutorial’s content and presentation were possible."
Answer: 488232.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: "from pull request DM-6500:  https://github.com/Caltech-IPAC/firefly/pull/102  * 2MASS All-Sky 'Read Me!' link in Catalog Search panel points to http://localhost:8080/irsaviewer/Q'http://hades.ipac.caltech.edu/applications/Gator/GatorAid/irsa/scan.html'E * -If you search m31 2MASS scan info catalog (4th catalog in the list), then bring back catalog panel, the first catalog is highlighted, but if you search, you'll notice that you are still searching 2MASS scan info.-"
Answer: 213306.0

User story: "I don't think that we're distributing the Kron code; please add it.  "
Answer: 221.0

User story: The Kron code doesn't set the algorithm metadata.  E.g.  {code}  algMetadata.set("ext_photometryKron_KronFlux_nRadiusForFlux",                  config.plugins["ext_photometryKron_KronFlux"].nRadiusForFlux)  {code}  
Answer: 59606.0

User story: "obs_subaru enables bright object masks by default, as that's desirable for HSC production runs.      However, when HSC data is processed without bright object masks available (as will happen in most GO observations and development use), multiBandDriver.py will fail because the BRIGHT_OBJECT mask plane is not present but the base_PixelFlags algorithm is configured to make use of it. This is confusing, and it also requires the definition of a configuration file to fix the problem because base_PixelFlags cannot be configured directly on the command-line.    Some possibilities for fixing this:   - Add the BRIGHT_OBJECT mask plane in AssembleCoadd if doMaskBrightObjects is True but the external catalog is not found.  This will make the PixelFlags operation a silent no-op.   - Allow configuration options to allow PixelFlags algorithm to silently skip some flags if the appropriate masks are not available.    I am sure there are other options as well.  "
Answer: 71032.0

User story: "There is much more information in the document, but the pipelines sections need to be refined.  We also need to give the software primitives a go over."
Answer: 34349.0

User story: "Add the release announcement and finalize other documentation details in pipelines.lsst.io for the v12 release."
Answer: 996.0

User story: "On several occasions, sims has desired to add python packages to the standard build env which are not DM approved 3rd party packages.  The result has either been to block sims development or undocumented deps creeping into DM packages.    This may be avoidable by adding a sims specific installation flag to {{lsstsw}} along with a sims env specifc jenkins job."
Answer: 382928.0

User story: "read and critique Jacek's  LPM document and the more manual oriented work from <USER>  Phone con with Kevin w.r.t. reporting channel for equipment expenses in Jira (as opposed to the now clear separate distinct financial channel).  Worked out checklist and principals for revised WBS. "
Answer: 2.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: "From [HSC-1409|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1409]:  {quote}  Due to an operational reason (to meet the requirement of Subaru FITS dictionary), the definition of EXP-ID is soon to be changed in the data acquisition side.  In the new definition, EXP-ID is set to 'HSCE%08d' where the letter 'E' is fixed as requested in the dictionary, and the number part corresponds to exactly the same number as our familiar 'visit'.  obs_subaru:ingest.py needs to be updated to include this rule.  The data taken with this change so far are:  HSCA07441200--HSCA07441757  HSCA90925200--HSCA90929557  {quote}    The change made as part of HSC-1409 introduces a new code path for the updated data, while old data continue to be supported with the old code path."
Answer: 43384.0

User story: "Write the presentation for the SPIE conference. Date of presentation: 26th June."
Answer: 14228.0

User story: "This will be done as DMTN-023 so the results are preserved for posterity.    This may be somewhat redundant with the work Mandeep Gill is doing in translating HSC docs, but I need it now; we can merge later."
Answer: 2261.0

User story: "* firefly_loader.js mistakenly uses relative path to load dependencies when it should resolve it via location of the loading script.  * TablePanel should render html content as html by default.  * paging bar style does not show correctly in irsa html  * row height does not resize to the icon size, the old api did. and the default row selectable is set to false in the old api.  * the help button needs to be added on top of the table panel.  * the expand button does not function as expected (open a full table panel)."
Answer: 5740.0

User story: "We want to have a subMenu component in the Firefly so we could group some of the actions together by putting them into subMenu.         Added submenu capability to drop down menu. Submenu can be nested to multiple levels.  Also, implemented ticket DM-14515 to place project footprints into submenu.  You can test this by loading any image, then select {{Overlay Markers}} to see drop down with submenu."
Answer: 1123213.0

User story: "Pybind11 does not currently support translation of custom exceptions. This ticket tracks work done on upstream pybind11 (internal fork https://github.com/lsst-dm/pybind11-1) to implement this functionality. It should support functionality equivalent to (but not necessarily with the same API) as Boost Python exception translators (http://www.boost.org/doc/libs/1_61_0/libs/python/doc/html/reference/high_level_components/boost_python_exception_translato.html)."
Answer: 34590.0

User story: "1. In the color stretch dialog:  (in chrome Version 50.0.2661.102 (64-bit) on my Mac OSX 10.9.5)      * the asinh beta and powerLaw Gamma input field do not  look like part of the input fields group. Too much white space in between.      * When clicked on the Z scale option when the asinh and powerLaw types selected, the min and max values overlapped with the option choice. "
Answer: 210530.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 analysis script was adapted for single visit processing comparisons in DM-4393 and DM-4730.  Do the same here for coadd processing comparisons."
Answer: 246525.0

User story: {{obs_decam}} uses {{ccdnum}} as the CCD dataId key, while most other obs packages use {{ccd}} and there are a number of places in the stack that the key name "ccd" is assumed (e.g. PropagateVisitFlags DM-5326; afw/cameraGeom/utils ButlerImage).  This has caused many troubles for using {{obs_decam}}.      {{ccd}} used to mean something different in {{obs_decam}} because there were no designated numbers for the sensors and side+ccd were used when the package was first put together.  Since the merge of this commit https://github.com/lsst/obs_decam/commit/1c4db0457cc4ff6e3bbb76b468f5da10de7a0c37 (DM-3591), side+ccd are no longer used in obs_decam. To ease maintenance need and reduce confusion, this ticket will remove the deprecated usage of the dataId "side" and "ccd".   Afterwards "'ccd" can be made to mean "ccdnum" for specific dataset types.     This provides a workaround for obs_decam for DM-5326, and CBP/CPP work.  
Answer: 91476.0

User story: "Work associated with making manual weeklies, mid-cycle releases etc. Closes when the mid-cycle release is done. "
Answer: 239467.0

User story: "This ticket involves the research and design of a metadata system for describing LSST code and documentation repositories. Such metadata would be leveraged by DocHub and LSST the Docs (see [SQR-011|https://sqr-011.lsst.io]) and would reside as a YAML/JSON file in a resource’s GitHub repository.    [JSON-LD|http://json-ld.org] is of particular interest. I’m also consulting with GitHub, ADS, Zenodo, and CfA Library on making a sustainable system."
Answer: 240407.0

User story: "The dipoleFitTask was spitting out too many warnings. Change many of those to debug statements and remove the `lmfit` UserWarnings."
Answer: 1035.0

User story: "Understand how the variance plane should be adjusted in the decorrelation (ZOGY) correction, and ensure it is being done correctly."
Answer: 56230.0

User story: "We start with initial tests of Shifter, with the first goal to  submit PBS jobs on the Blue Waters test system utilizing Shifter that start HTCondor master/startd daemons on compute nodes.  These daemons will communicate to a remote HTCondor central manager (e.g., running on the Nebula OpenStack) and glide-in to join a working pool.  The setup will then be tested with simple payload jobs (these  submitted from a Nebula instance running the schedd)  that verify access to the LSST stack within the UDI (User Defined Image)."
Answer: 21736.0

User story: "Make Known Issues and Metric Report both top-level pages. Link to installation issues from installation page.    See https://pipelines.lsst.io/v/DM-6575/index.html"
Answer: 1358.0