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: When running jointcal's tests with a recent stack, I'm seeing a lot of warnings like the below (roughly one per test?), which are obscuring real errors:    {code}    /home/parejkoj/lsst/lsstsw/stack/Linux64/python_future/0.16.0+1/lib/python/future-0.16.0-py3.6.egg/past/builtins/misc.py:79: DeprecationWarning: 'U' mode is deprecated      with open(filename, "rbU") as fin:    source:447: DeprecationWarning: invalid escape sequence \   {code}
Answer: 253276.0

User story: "Replace the {{nginx-ssl-proxy}} currently being used for LTD Keeper with Kubernetes's native [Ingress|https://kubernetes.io/docs/concepts/services-networking/ingress/] resource. This should simplify the deployment, and since it is managed by Google Cloud Platform, should have better security.    Tutorial: https://cloud.google.com/kubernetes-engine/docs/tutorials/http-balancer"
Answer: 11408.0

User story: "The DCR technote DMTN-037 needs to be rewritten for publication in a journal. This bucket ticket represents the amount of effort that will be spent on that revision in the current sprint."
Answer: 424541.0

User story: "The current implementation of the {{Butler}} prototype hardcodes the the path hint for storage.  Fix this by implementing {{makePath}}."
Answer: 20673.0

User story: "To construct a {{Butler}}, a user should only have to supply a path to a ({{YAML}}) configuration file (or group of files). This should then lead to the instantiation of a specific {{Registry}} and {{Datastore}}.    Implement this as a first prototype version."
Answer: 13452.0

User story: "[~<USER> added work in {{u/fix_outliers}} to better manage photometry errors and outlier rejection. This ticket is to review that work and see if it fixes the problems with HSC processing on the constrained model."
Answer: 23083.0

User story: "It looks like the to push to s3 or not to push to s3 logic got mangled as part of refactoring on DM-10367."
Answer: 110.0

User story: "Reduce technical debt in how we create Docker releases and versions for LSST the Docs applications.    # Use {{setuptools_scm}} to create semantic versions for the LTD Keeper and Dasher applications based on the repo's Git tag state.  # Convert Keeper and Dasher to setuptools projects to use {{setuptools_scm}}.  # Create a Makefile to create a Docker image that automatically inserts the version information.  # Create a Travis CD pipeline that uploads to Docker Hub when a new tag or branch is available.  # Create an API route that exposes the Keeper API version."
Answer: 13176.0

User story: "Everyone will attend the 4 day LSP workshop, held at IPAC, from Dec. 4 to Dec. 8, 2017"
Answer: 14466.0

User story: "The {{_48}} release failed attempting to make git tags.  It seems that the {{w_2018_48.list}} tag file was pushed to s3 but has not yet (as of a few minutes ago) appeared on {{eups.lsst.codes}}."
Answer: 2805.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 Firefly we are using IRSA OASIS service to get 2MASS (allsky) images.   2MASS is in IBE since a long time but there is now a new IBE2 api which expose all ATLAS, WISE, PTF and 2MASS images which includes all 6 2MASS datasets (mosaic included).     It would require to change Firefly code to get 2mass images from ATLAS api type instead of OASIS."
Answer: 146599.0

User story: "Building on {{validate_drp/reportPerformance.py}}, we need some code to take the JSON output of validate_drp on all of the tracts+filter combinations and produce some kind of summary table to compare the 115 tract+filter combinations across the three runs (singleFrame/jointcal/meas_mosaic) in photometry and astrometry. There's already some pretty-printing code in validate_drp that we can probably steal."
Answer: 175681.0

User story: "There's an SCL I missed."
Answer: 75.0

User story: Perform the "basic data completeness and integrity checks" following the procedues in  DM-12605's LDM-534 test case DRP-00-05 (sect. 4.2.8.3)
Answer: 1.0

User story: "Diagram the architectural overview of monitoring for all physical ocations."
Answer: 1.0

User story: "As we think of more things to pass down to the spawned Lab container, and more knobs that need to be added to the deployment (for instance, selecting between CILogon and GitHub), then our deployment tool needs to be modified to accommodate these additional settings and generate configuration and deployment instructions for them.    Same goes for bug fixes in the deployment tool as we find corner cases where it doesn't currently work but should."
Answer: 131233.0

User story: "There are a number of places that unit testing would be desirable."
Answer: 399.0

User story: "As is imageREST_v0 API (URL pattern/style) is already supported on top of v1 code base.    Once we transition over to imageREST_v1, which can be seen as v0++ from functionality standpoint,  there is really no need for the old v0 code (isolated to a few files) to remain in the code base.    "
Answer: 128427.0

User story: "I imagine that it would be useful to navigate QA sky plots by perhaps starting off with a multi-tract sky plot, then clicking on a tract and showing just that tract (and then perhaps loading tract-specific information or showing tract-specific scatter plots), and then to have the same ability to see specific patches.  And then similarly it could be useful to look at a visit plot and be able to auto-zoom to individual CCD regions.  All of this is of course slightly redundant with the pan-zoom features that come automatically with Bokeh, but the ability to attach different callbacks to clicks and to automatically load up information on demand for the discrete processing units that the pipeline knows about could be useful.    This is related to DM-12252, but broader because of the regional-click callbacks and hierarchical plotting structure I'm imaging this will require."
Answer: 543585.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: "{{ProcessingFW}} is one of the packages DESDM framework consist of. The goal is to port it to Python 3."
Answer: 18.0

User story: "{{IntegrationUtils}} is one of the packages DESDM framework consist of. The goal is to port it to Python 3."
Answer: 12.0

User story: "{{FileMgmt}} is one of the packages DESDM framework consist of. The goal is to port it to Python 3."
Answer: 12.0

User story: "{{DatabaseApps}} is one of the packages DESDM framework consist of. The goal is to port it to Python 3."
Answer: 7.0

User story: "{{QCFramework}} is one of the packages DESDM framework consist of. The goal is to port it to Python 3."
Answer: 12.0

User story: "See https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1426  "
Answer: 746.0

User story: "Review synpipe instructions set provided by [~<USER>.  This is the first step in the project to put fake objects into the biweekly HSC continuous integration. "
Answer: 58713.0

User story: [~ksuberlak] is trying to use the {{text2fits.py}} utility provided by the Stack's astrometry_net package. Unfortunately, it doesn't work with Python 3:    {code}  Reading file starfast_ref_obs_s5n6170.txt  Column names: ['id', 'ra', 'dec', 'u', 'g', 'r', 'i', 'z', 'y']  Traceback (most recent call last):  File "/Users/chris/lsst_stack2/stack/miniconda3-4.3.21-10a4fa6/DarwinX86/astrometry_net/0.67.123ff3e.lsst1+4/bin/text2fits.py", line 50, in <module>  intvalmap=inulls)  File "/Users/chris/lsst_stack2/stack/miniconda3-4.3.21-10a4fa6/DarwinX86/astrometry_net/0.67.123ff3e.lsst1+4/lib/python/astrometry/util/fits.py", line 813, in streaming_text_table  for i,line in zip(xrange(Nchunk), f):  NameError: name 'xrange' is not defined  {code}    Please fix it.
Answer: 1175458.0

User story: "Evaluate current star/galaxy separation in the stack using the HST cosmos catalogs. For example: plot completeness, purity, and develop metrics for testing classification algorithms.   This can serve as the training set for future work. "
Answer: 96490.0

User story: "Research existing star/galaxy separation approaches past and present in the project including:  * Jose Garmilla's thesis/code  * Ongoing work with Scott  * Ongoing work with Colin"
Answer: 96493.0

User story: "Regenerate plots evaluating the effect of lossy compression on galaxy shape parameters (ellipticity residuals etc..)."
Answer: 48968.0

User story: "The Butler Working Group developed requirements in a Google spreadsheet. They need to be migrated to the MagicDraw SysML document and then placed into LDM-556 on DocuShare for review."
Answer: 17390.0

User story: "In support of the LDM-534 QA milestone, run {{coaddAnalysis.py}}, {{colorAnalysis.py}} and {{visitAnalysis.py}} on all coadds and visits from the weekly 46 RC processing run (/datasets/hsc/repo/rerun/RC/w_2017_46/DM-12545/).  "
Answer: 47338.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 redesign of the {{ap_*}} framework should be motivated by the expected capabilities of Butler v3, SuperTask, and (to a much lesser extent) the new {{obs}} framework. We should learn of any design constraints imposed by these frameworks before reviewing {{ap_verify}} and {{ap_pipe}}."
Answer: 28471.0

User story: "Represent Alert Production in the Lossy Compression Working Group. Ensure AP's needs have test coverage as algorithm comparisons start ramping up."
Answer: 27114.0

User story: "For catalog search, in case the searched catalog is with no position information, what should be rendered on the triview in addition to the table containing no position columns?     The content of the coverage will be blank. However, the chart content is various based on the table content,   a default chart of the first two numeric columns? a blank chart with no numeric columns? a chart with only one numeric column?      The triview layout needs some update in case a catalog with no position information is searched and displayed.     ----------  TG 02/01/18  - If the table with no positional info is the first rendered in firefly, no coverage or chart area will show.  - If other tables are added, the coverage and chart areas will not disappear, when changing the active table. This is intentional behavior to avoid confusing layout changes.    An example of a table with no position info WISE -> AllWISE Inventory Table    Other bugs fixed:    - non-returning search  - removed chart hanging in the store  - empty result area with no drop down, when all tables are deleted  - missing layout updates (on table update or removed chart)  - no axis labels in the default histogram chart"
Answer: 92268.0

User story: "With DM-12356 I found it hard to fully deploy the LTD Keeper app in a staging namespace from scratch, indicating that some technical debt has crept into the deployment process. This ticket is to systematically go through the deployment and resolve documentation and deployment processes."
Answer: 19947.0

User story: "The last several {{s3backup-eups}} builds have failed. Eg.,    https://ci.lsst.codes/job/sqre/job/backup/job/s3backup-eups/215/consoleFull    {code:java}  copy failed: s3://****/stack/redhat/el6/devtoolset-3/miniconda3-4.3.21-10a4fa6/<EMAIL> to s3://****/2017/11/29/2017-11-29T12:12:10Z/stack/redhat/el6/devtoolset-3/miniconda3-4.3.21-10a4fa6/<EMAIL> An error occurred (InvalidArgument) when calling the UploadPartCopy operation: Range specified is not valid for source object of size: 27092590    {code}  "
Answer: 322263.0

User story: "Write a DMTN reporting the findings on resource usage of the RC reprocessing"
Answer: 20060.0

User story: "auth_data isn't getting refreshed on login, so we never get a list of new containers."
Answer: 20103.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: Jenkins jobs that use docker are frequently hanging and {{dockerd}} / {{xfs}} errors are appearing in the {{dmesg}}:    {code:java}  [279961.166094] INFO: task dockerd:902 blocked for more than 120 seconds.  [279961.169742] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.  [279961.173508] dockerd         D ffff8800a188e010     0   902      1 0x00000080  [279961.176932]  ffff880033883d78 0000000000000086 ffff8803bb2e8fd0 ffff880033883fd8  [279961.180601]  ffff880033883fd8 ffff880033883fd8 ffff8803bb2e8fd0 ffff8800a188e000  [279961.184682]  ffff8800a188e040 ffff88036f27c140 ffff8800a188e068 ffff8800a188e010  [279961.188403] Call Trace:  [279961.190270]  [<ffffffff816a94e9>] schedule+0x29/0x70  [279961.193155]  [<ffffffffc01732ea>] xfs_ail_push_all_sync+0xba/0x110 [xfs]  [279961.196618]  [<ffffffff810b1910>] ? wake_up_atomic_t+0x30/0x30  [279961.199554]  [<ffffffffc015c2e1>] xfs_unmountfs+0x71/0x1c0 [xfs]  [279961.202526]  [<ffffffffc015cded>] ? xfs_mru_cache_destroy+0x6d/0xa0 [xfs]  [279961.205747]  [<ffffffffc015ee92>] xfs_fs_put_super+0x32/0x90 [xfs]  [279961.209261]  [<ffffffff81203722>] generic_shutdown_super+0x72/0x100  [279961.212640]  [<ffffffff81203b67>] kill_block_super+0x27/0x70  [279961.215738]  [<ffffffff81203ea9>] deactivate_locked_super+0x49/0x60  [279961.218801]  [<ffffffff81204616>] deactivate_super+0x46/0x60  [279961.221628]  [<ffffffff8122184f>] cleanup_mnt+0x3f/0x80  [279961.224301]  [<ffffffff812218e2>] __cleanup_mnt+0x12/0x20  [279961.227135]  [<ffffffff810ad247>] task_work_run+0xa7/0xf0  [279961.230449]  [<ffffffff8102ab62>] do_notify_resume+0x92/0xb0  [279961.233768]  [<ffffffff816b52bd>] int_signal+0x12/0x17  {code}    These problems seem to go away, at least for awhile, after the node is restarted (they will not soft reboot).  It isn't yet known if this is a kernel bug or some of random EBS I/O timeouts.  As it seems to be only (?) triggered by dockerd, it seems much more likely to be a kernel issue.  What is unusual is that this doesn't seem to have been an issue until ~ a week ago and this doesn't correlate with a kernel or dockerd version change.
Answer: 173787.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 {{ap_verify}} documentation for --DM-11592-- has exposed a number of difficult-to-explain behaviors in {{ap_verify}}. Those with an obvious solution have been ticketed separately, but a number are UI/roadmap decisions that need to be agreed on before the "correct" behavior can be documented.    This ticket is to set aside time for discussing the following questions, and updating the documentation accordingly (TODOs tagged with this issue ID):   * -How do we foresee installing datasets? Will they be automatically provided as part of {{lsst_distrib}} or another metapackage ({{ap_verify_hits2015}} is owned by the {{lsst}} GitHub group, but as far as I know it's not distributed by any of the Stack installers)? If users will be installing them manually, how will they be versioned?- {color:#707070}[To be determined later; no updates to documentation for now]{color}   * What is the rationale for giving datasets a command-line name distinct from their repository or EUPS name (see the "HiTS" : "hits_data" example in --DM-11118--)? Now that this feature is implemented and documented, it seems to only add user friction (e.g., it is difficult to work out where to download a dataset from its command-line name). {color:#707070}[Document that it's a placeholder for a future versioning system]{color}   * Following --DM-11118--, we added a {{--rerun-}} parameter that superficially resembles the {{-rerun}} parameter for {{CmdLineTask}}, but places results in the dataset directory. Its behavior is so unlike [repository chaining|https://pipelines.lsst.io/v/DM-11253/modules/lsst.pipe.base/command-line-task-data-repo-howto.html#using-reruns-to-organize-outputs-in-a-single-data-repository] that it is likely to confuse rather than help veteran Stack users, it requires users to know where a dataset is installed (something the rest of the design tries to hide), and it potentially makes changes to otherwise read-only datasets. I would like to revisit the question of whether this argument is desirable and, if so, what its behavior should be. {color:#707070}[To be modified as suggested by KSK; deferred to DM-13492 due to implementation constraints.]{color}   * Why does {{ap_verify}} take a parameter called {{\-\-dataIdString}} rather than {{\-\-dataId}} or, as command-line tasks do it, {{\-\-id}}? {color:#707070}[Change parameter to {{--id}}]{color}   * -{{ap_verify}} currently returns 0 if the pipeline ran to completion, and an interpreter-dependent value otherwise. Should we impose more specific guarantees? (Making {{ap_verify}} count failed dataIds the way command-line tasks do may have implications for its error-handling policy.)- {color:#707070}[To be determined later; no updates to documentation for now]{color}
Answer: 105023.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 implementation of {{ap_pipe}} requires knowledge of specific file naming conventions used by HiTS/DECam. The assumption behind the design of {{ap_pipe}} and {{ap_verify}} was that we could simply tell ingestion code "this directory has science images", "this directory has calibration files", etc., and the code would intelligently identify and organize the data. Consult an expert on ingestion and/or {{obs}} packages to determine whether this is a reasonable assumption.    As part of this ticket, the documentation of {{ap_verify}}'s dataset framework and the {{ap_verify_dataset_template}} package should be updated to include any requirements ("the {{calib/}} directory must have separate subdirectories for biases and flats") imposed by the {{obs}} framework, or a statement that the dataset structure is free-form.
Answer: 51786.0

User story: "This is to enable the full support for VO interfaces, specified in XML, conforming to W3C's XML Schema Recommendation.    The basic work flow is to map incoming VO  requests to JSON formatted output as specified by DAX Jason Schemas. Then output to XML to be generated, as alternative option to JSON (native for DAX).    The stilts tools  library, for VO compatibility checking, along with JSON Schema (as DAX dependency)."
Answer: 543400.0

User story: "Write the first version of the test report for LDM-503-2 test case DRP-00-05"
Answer: 28686.0

User story: "1st thoughs on the scope of the document:  Our measurements of the optical atmospheric transmission exploits natural celestial sources to back-light the atmosphere. This document enumerates the expected outputs from processing dispersed images from low resolution sprectrometer Telescope. It also lists by-products of the production pipeline that are identified as useful diagnosis tools and describes in detail how the observations can be used to produce atmospheric transmission curves."
Answer: 296907.0

User story: Currently qana uses database-global "ovelap" value as a match table "separation" parameter which is wrong. Database-global "ovelap" is supposed to be a default overlap value for tables that don't define their own overlap. Match table separation is not really related to overlap, so to reduce confusion we need to add new parameter to match table configuration in CSS and use is to set qana parameters.  
Answer: 80321.0

User story: "Create jupyter deployment tool."
Answer: 4374.0

User story: "This trivial job needs to be converted to pipeline in order to implement timeouts."
Answer: 93641.0

User story: "Generic bucket for keeping up with Jupyter upstream"
Answer: 136901.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: It appears that the puppet {{rvm}} module is throwing errors because the rvm managed ruby install is broken, most likely due to a system package change.    {code:java}  ==> el7-5: Error: /Stage[main]/Ruby::Dev/Package[bundler]/ensure: change from absent to latest failed: Could not update: Execution of '/usr/local/rvm/rubies/ruby-2.2.7/bin/gem install --no-rdoc --no-ri bundler' returned 1: Error loading RubyGems plugin "/usr/local/rvm/gems/ruby-2.2.7@global/gems/executable-hooks-1.3.2/lib/rubygems_plugin.rb": /lib64/libcrypto.so.10: version `OPENSSL_1.0.2' not found (required by /usr/local/rvm/rubies/ruby-2.2.7/lib/ruby/2.2.0/x86_64-linux/openssl.so) - /usr/local/rvm/rubies/ruby-2.2.7/lib/ruby/2.2.0/x86_64-linux/openssl.so (LoadError)  ==> el7-5: Error loading RubyGems plugin "/usr/local/rvm/gems/ruby-2.2.7@global/gems/gem-wrappers-1.3.2/lib/rubygems_plugin.rb": /lib64/libcrypto.so.10: version `OPENSSL_1.0.2' not found (required by /usr/local/rvm/rubies/ruby-2.2.7/lib/ruby/2.2.0/x86_64-linux/openssl.so) - /usr/local/rvm/rubies/ruby-2.2.7/lib/ruby/2.2.0/x86_64-linux/openssl.so (LoadError)  ==> el7-5: ERROR:  Loading command: install (LoadError)  ==> el7-5:  /lib64/libcrypto.so.10: version `OPENSSL_1.0.2' not found (required by /usr/local/rvm/rubies/ruby-2.2.7/lib/ruby/2.2.0/x86_64-linux/openssl.so) - /usr/local/rvm/rubies/ruby-2.2.7/lib/ruby/2.2.0/x86_64-linux/openssl.so  ==> el7-5: ERROR:  While executing gem ... (NoMethodError)  ==> el7-5:     undefined method `invoke_with_build_args' for nil:NilClass    {code}  
Answer: 124.0

User story: "Reprocess the HSC RC dataset, as defined in [DMTR-31 Sect. 4.1 |https://docushare.lsst.org/docushare/dsweb/Get/DMTR-31], using Stack w_2017_48.  Steps include {{makeSkyMap.py}}, {{singleFrameDriver.py}}, {{mosaic.py}}, {{coaddDriver.py}}, and {{multiBandDriver.py}} (DM-10129/DM-11020)."
Answer: 13085.0

User story: "The {{_47}} weekly release failed trying to tag git repos on all 3 attempts.  It seems that every attempt was being scheduled on {{jenkins-el7-4}} and there was some sort of jenkins remote communication error:    {code:java}  Cannot contact jenkins-el7-4: java.io.IOException: Remote call on JNLP4-connect connection from ip-192-168-123-181.ec2.internal/192.168.123.181:48368 failed  {code}    This node (as were all el7 nodes) was restarted last Wednesday as part of DM-12782, which may some how have triggered this new issue.    I noticed something funky was going on over the weekend and took that node offline at {{Nov 25, 2017 8:04:56 AM}}.  However, the weekly release still needs to be salvaged and the problem with that build node diagnosed.  "
Answer: 1794.0

User story: "Looking at residuals from spectra differences obtained from various aperture size would   reveal potential bias in the flux estimator.    -> Here is an update illustrating the bias (aperture40pix;png), and the noise increase (aperture130pix.png)"
Answer: 298101.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: "SQuaSH QC Tier 0 database is currently deployed on GKE based on the official MariaDB docker image, see https://github.com/lsst-sqre/squash-db    Since we are using MySQL 5.7 because of the JSON capabilities we can use Google Cloud SQL instead and benefit from database management, backups and replicas available in the GCP."
Answer: 55481.0

User story: "Implements RFC-418."
Answer: 9390.0

User story: "Add ext_shapeHSM_HsmShapeRegauss_e1, ext_shapeHSM_HsmShapeRegauss_e2, ext_shapeHSM_HsmShapeRegauss_resolution to the coadd comparison script to aid with assessing changes relevant to shear measurements."
Answer: 21501.0

User story: "We should be able to make the part of {{validate_drp}} that does the metric measurement into a {{Task}}.  That would allow us to persist the {{Job}} using the butler location rather than hard coding it."
Answer: 371311.0

User story: "Process the 3 tracts of the HSC RC data with  - DESDM framework packages, plugins and integration codes {{BPSstack}} tag {{lsstv14-desdmv1.01}}. This version is based on Stack v14.0            - wcl as of DM-12590 ([f6efaaa|https://github.com/lsst-dm/prod_wcl/commit/f6efaaabecfaee4a70c02aea0d5ae92823027340])"
Answer: 13148.0

User story: "<USER>suggests that photoCal might benefit from a signal-to-noise cut."
Answer: 23079.0

User story: "For the LSST Project and Community Workshop 2017, a version of the DM stack tutorial was developed that used Firefly for plots. This ticket covers that work and some followup work to make plots using the new Plotly capabilities of Firefly."
Answer: 165552.0

User story: "Brief Jenkins job reference and stack-os-matrix how-to guides for ci.lsst.codes that will be published in developer.lsst.io. An extension of DM-12107."
Answer: 12538.0

User story: "The recent upgrade of the python3 baseline after stack release 14.0 seems to have busted the Qserv container builds (and thus Travis CI for Qserv)"
Answer: 88.0

User story: "It is believed that the problems with bad colors in HSC-Z and Y that we observed in DM-12776 are due to the way we are using inverse variance maps to weight gradient steps in the deblender. When two bands have substantially different mean variance, certain colors converge more quickly than other colors, and at all times are capable of taking larger steps toward the minimum, which we believe results in poor colors in the bands with higher variance. Similarly, images with widely varying pixel variances could also see some pixels reaching convergence more quickly than others (although we have not observed this directly).    To combat this [~<USER> and I propose to normalize the weights for SED updates along each band, so that only pixel by pixel variations are weighted for each SED update, and normalize the weights for morphologies along each single band image. This should give us more uniform convergence and hopefully solve DM-12776 as well."
Answer: 8888.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: "Check on claimed epics each month as they are claimed .."
Answer: 354529.0

User story: The daily backups for {{s3://eups.lsst.codes}} were growing unbounded.  Backups have been prune down to retain only the 1st day of each month prior to the current month. Eg.    {code:java}  #!/bin/bash    #set -e  set -o xtrace    for m in {4..10}; do    mon=$(printf "%02d" $m)    for d in {2..30}; do      day=$(printf "%02d" $d)      aws s3 rm --recursive "s3://eups.lsst.codes-backups/2017/${mon}/${day}" &    done  done  {code}    Either a rotation script is needed or s3 object expiration needs to be set.  Ie., backups on every day but the first of the month have a 30 day expiration set on the objects.
Answer: 184270.0

User story: "Following RFC-415, rename ip_cpp to cp_pipe and add to lsst_distrib"
Answer: 34607.0

User story: "Planning, management, status tracking, architecture, T/CAM & DMLT activities, etc."
Answer: 30255.0

User story: "Planning, management, status tracking, architecture, T/CAM & DMLT activities, etc."
Answer: 38742.0

User story: "There appears to be a problem with the interface between the stack and the deblender. In the attached images, stack_output shows the data and the footprints created from the stack results, while deblender_output shows the results when the deblender is run using the exact same settings. This shows that somehow the results aren't being persisted properly in the pipeline.    This ticket is to investigate includes work the last few days to diagnose the problem and upcoming work to find and fix the bug."
Answer: 9994.0

User story: "The question can be answered by looking at the convergence of the flux with increasingly large aperture.  To do so :    —> Contamination from surrounding objects needs to be removed.    It is suggested to do so in two steps :          1)  Subtract 0th order light using an associated direct image (rescaled I don’t know how).          2)  Extract both  m+1 and m-1 order ->        - then normalize               - then Build a composite spectrum, out of minimum signal, to remove asymmetric m+1 contamination from other objects.          —> Mm, here, this second step shows its limit."
Answer: 307719.0

User story: "The {{w.2017.45}} weekly release git tag already can not be built via {{lsstsw/lsst-build}} due to a change in {{pytest-flake8}}.  This is a major problem for being able to reproduce a build from even a week ago.    The easiest solution should be to add the weekly release tags to the external repos."
Answer: 10577.0

User story: "When there is a large build backlog, cron triggered {{sqre/infrastructure/travissync}} instances start to pile up.  This results in 2 undesirable behaviors.    # multiple builds of {{travissync}} may end up running concurrently (pointless)  # many {{travissync}} builds may run back to back (uneeded)    The jenkins job should be modified to disable concurrent builds and to have a timeout <= the cron triggering interval, such that builds can timeout while queued (not running)."
Answer: 10660.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: "To reproduce, the first one with --cores=1 works, but second with --cores=2 does not:      {code}  source /software/lsstsw/stack/loadLSST.bash  setup lsst_distrib  export wideVisitsG=9852^9856^9860^9864^9868^9870^9888^9890^9898^9900^9904^9906^9912^11568^11572^11576^11582^11588^11590^11596^11598  coaddDriver.py  /datasets/hsc/repo --rerun RC/w_2017_46/DM-12545:private/<USER>psfMatching/newStack --time 500 --cores=1  --id tract=8766  patch=5,5 filter=HSC-G --selectId ccd=0..8^10..103 visit=$wideVisitsG   coaddDriver.py  /datasets/hsc/repo --rerun RC/w_2017_46/DM-12545:private/<USER>psfMatching/newStack --time 500 --cores=2  --id tract=8766  patch=5,5 filter=HSC-G --selectId ccd=0..8^10..103 visit=$wideVisitsG  {code}    Note to get any useful output you'd need to either switch:  makeCoaddTempExp.doApplyUbercal=False  AssembleCoadd.doApplyUbercal=False    OR     setup meas_mosaic (which I currently can't build with the python3 stack)"
Answer: 10115.0

User story: "This is the most minimal version of DM-12366, requested by NAOJ.  It makes sense to do it on a separate ticket.    This will mostly be highly HSC-specific code, as it's a lot harder to come up with a way to report fractions of different filters used when you can have more than two filters and arbitrary names for them; for HSC we know exactly which pairs of filters we need to take ratios of."
Answer: 14207.0

User story: "As part of DM-10765 it became apparently that SkyWcs needed many changes, including:  - Do not inherit from Transform  - Add FITS binary table persistence  - Add missing functionality as methods or free functions    In addition, it is possible to greatly simplify the code using the new {{ast::FrameDict}} class.    [~<USER> suggested, and I agree, that it is better to do the SkyWcs overhaul on a ticket separate than DM-10765, making DM-10765 itself smaller and more focused."
Answer: 32357.0

User story: "These are very useful for QA in comparing measurements on two different processing runs of the same data/field.  They got missed from the default list in the comparison scripts as they were inherited from the *coaddAnalysis.py* script whose Mag comparisons are all done w.r.t. the PSF mag, so would've been redundant."
Answer: 24610.0

User story: "Trey, et. al.    Qualys reports that the SSL certificate for https://lsst-demo.ncsa.illinois.edu expires on November 26th. Looks like this is a Let's Encrypt cert so it should auto-renew, but we believe that should have already happened by now and it has not so probably a good idea to look into why it has not renewed yet.    This is the SSL certificate used by the {{proxy}} Docker container installed by SUI, and not something general to the server.    Similarly, the SSL certificate for https://lsst-demo2.ncsa.illinois.edu has already expired."
Answer: 257814.0

User story: "In order to be usable as a component of other Persistable objects, afw::geom::Transform should be persistable.  "
Answer: 73090.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: "To be discussed at DMLT of 2017-11-20. Not the final plan: will still need to be refined in conjunction with science leadership & developers."
Answer: 27305.0

User story: "[~<USER> [writes|https://github.com/lsst/pipelines_lsst_io/issues/66]:    {quote}  There is a colon missing in [this file|https://github.com/lsst/pipelines_lsst_io/blob/master/install/demo.rst] so the note in https://pipelines.lsst.io/install/demo.html#download-the-demo-project does not render correctly.  {quote}"
Answer: 7.0

User story: "Following the hscPipe 6.0-beta1 release, we need to merge work involved in improving the CompareWarp coaddition."
Answer: 35241.0

User story: "Lauren points out that the star/galaxy classification between runs is scary high. Look into this.     https://lsst-web.ncsa.illinois.edu/~<USER>artifact_rejection/compare-DM-12445/HSC-R/tract-9813/compare-t9813-HSC-R-diff_modelfit_CModel-psfMagHist.png"
Answer: 215567.0

User story: "deployment of SUIT, PDAC using docker technology"
Answer: 191432.0

User story: "setup and deploy the {{ehcache}} server for Firefly    to enable each server node communicate with it for cache access.    This is needed for docker environment, as the existing multicast {{ehcache}}-discovery mechanism is difficult to set up in a containerized environment. We have experimented with K8S, but the issue is still there.          This is to have an alternative way for cache.     6/13/2018 XW    This was not implemented as described. Much work went  into resolving the issue of cache replicate NOT working in k8s environment, which was the cause for this ticket. "
Answer: 250614.0

User story: "Update the color mapping of the visit outlines such that each visit gets a unique color.  Also add a legend with the visit numbers such that they can be identified in the plot.  Additionally, allow for multiple tracts to be specified and have their outlines drawn on the plot with unique gray-scaling and added to the legend.  "
Answer: 5872.0

User story: "Switch defaults everywhere (not just obs_subaru coaddDriver).   Includes running ci_hsc with CompareWarpAssembleCoadd. "
Answer: 123862.0

User story: "Default quota is 500GB on a new account.   So reduce the default storage to be smaller than that."
Answer: 84.0

User story: Need to run a grid of config parameters to find the best combination. Many of the defaults were adopted from SafeClip.    * temporalThreshold/maxNumEpochs:   * spatialThreshold:    +   {code}          self.assembleStaticSkyModel.sigmaClip = 1.5          self.assembleStaticSkyModel.clipIter = 3          self.detect.thresholdValue = 5          self.detect.nSigmaToGrow = 2          self.detect.minPixels = 4          self.detect.isotropicGrow = True          self.detect.thresholdType = "pixel_stdev"  {code}
Answer: 681161.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: "Thus far I've been clipping any any region for which we don't have information from the PSF-matched warp. This includes more area than direct warp because of  matching kernel smears out the bad pixels and edges of calexps.  Test allowing saturated pixels through. Merge if it works. "
Answer: 34772.0

User story: "Following IHS-612, there will be multiple slurm queues on LSSTVC.   It would be great to be able to tell {{allocateNodes.py}} which queue to send jobs to. "
Answer: 15803.0

User story: "An integer maxNumEpochs is too crude. The original fraction temporalThreshold of the number warps entering an image is too crude.     Evaluate and test a fraction with a floor based on the local N_epochs. "
Answer: 105709.0

User story: "Help [~<USER> get some eyeballs on the data for checking if the WarpCompare is good to go.    Write a little snippet to help automate displaying the data and recording comments in such a way that others can use, and it will be easy to pull the images back up.    Once the above is done, use it to go through a bunch of visits, looking at the diff between SafeClip and WarpCompare"
Answer: 15319.0

User story: "While sorting out the best approach for getting jointcal to ingest a SkyWcs, we discovered that the {{ConstrainedPolyModel}} was ignoring the {{initFromWCS}} constructor boolean flag. Looking at the history, it appears it was never used: the chip transfo was always being initialized with the input WCS.    This is an easy fix, and I'll also make it a configurable, so we can test how larger datasets behave when it is {{False}}; the testdata all appears to be fine (initial chi2 is different, but it quickly settles down to the same value)."
Answer: 5595.0

User story: "labour cost of IVOA meeting"
Answer: 282246.0

User story: "The labour costs of team members attending the DM all hands meeting in March, 2018.  "
Answer: 169380.0

User story: "Add Sphinx-based stack package documentation boilerplate and documentation to the https://github.com/lsst/templates repo. It was temporarily removed in DM-12674 because some team members thought it was confusing to have material in the template when Sphinx docs weren't fully rolled out."
Answer: 209869.0

User story: "After the design document is delivered, set up a design review for the YAML camera description."
Answer: 642160.0

User story: "Walk through, at least notionally, the cookbook produced by Robert."
Answer: 1176747.0

User story: "Deliver example ZTF data to [~<USER> so he can verify that the ZTF format does not break assumptions of the template obs package."
Answer: 782322.0

User story: "Deliver notes from implementation of {{obs_auxtel}} to [~<USER> so he can build up a cookbook fro making a new obs package."
Answer: 347022.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: https://developer.lsst.io/processes/workflow.html#tickets makes various claims about the association of different types of issue (story/bug/improvement) with epics. In particular, it claims that "bug" and "improvement" type issues are not associated with epics.    This is simply incorrect: bugs and improvements should be associated with epics in just the same way as stories, and are treated identically for the purposes of earned value accounting.    (I think this bad documentation is based on a misunderstanding of the outcome of RFC-43.)
Answer: 506122.0

User story: "We will revert the Sphinx additions to the {{doc/}} directory of the [Stack package template|https://github.com/lsst/templates/tree/master/project_templates/stack_package/example] to avoid confusion until the Sphinx-based stack documentation system (DM-7500) is production-ready."
Answer: 19792.0

User story: "Documentation doesn't reflect current reality"
Answer: 1154.0

User story: "The fix is to set {{sctrl.setCalcErrorFromInputVariance(True)}}.  "
Answer: 1510.0

User story: _(copied from DM-12510)_    It looks like squash isn't accepting the results:    {code:java}  "https://github.com/lsst/lsst_ci.git"}], "date": "2017-11-16T16:55:57.130106+00:00", "ci_id": "b3217", "ci_name": "validate_drp", "ci_dataset": "cfht", "ci_label": "docker.io/lsstsqre/centos:7-stack-lsst_distrib-d_2017_11_16", "ci_url": "https://ci.lsst.codes/job/sqre/job/validate_drp/1126/", "status": 0}  400 Client Error: BAD REQUEST for url: ****jobs/  script returned exit code 1  {code}    From looking at the source, I'm guessing we're banging into a 16 char limit of the ci_label field. Previously, this was being set to the jenkins node label the sub-configuration was running, which was always centis-7. As part of the rewrite, I'm not setting this to the registry url of the docker image (eg., ocker.io/lsstsqre/centos:7-stack-lsst_distrib-d_2017_11_16).  Ihttps://github.com/lsst-sqre/squash-api/blob/master/squash/api/models.py#L18-L19
Answer: 243343.0

User story: "Use the prototype Registry from either DM-12613 or DM-12371 and the prototype Datastore from DM-12667 to implement a prototype Butler (as described in DMTN-056).  The only supported operations are {{Butler::get}}, {{Butler::put}} and {{Butler::unlink}} with a {{DatasetLabel}} (e.g. no querying, data-graphs or transfers).    The intent of this prototype is to inform design decisions for the final version. It should not be throw-away code but is allowed to be rough around the edges."
Answer: 46419.0

User story: "Implement a minimal Butler Datastore (as defined in DMTN-056) backed by a POSIX filesystem.    The intent of this ticket is to build a minimum prototype for testing purposes to be used with either the Registry from DM-12613 (or DM-12371).  This prototype is to be as simple as possible but should be useable to inform decisions about pluggability, chaining, caching and API layering for later versions."
Answer: 39251.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "[~<USER> encountered this while coadding CFHT data:  {code}  safeClipAssembleCoadd INFO: Weight of deepCoadd_directWarp DataId(initialdata={'patch': '2,4', 'visit': 1022065, 'filter': 'u', 'tract': 0}, tag=set()) = 127.976  safeClipAssembleCoadd INFO: Found 5 deepCoadd_directWarp  safeClipAssembleCoadd INFO: Assembling 5 deepCoadd_directWarp  safeClipAssembleCoadd FATAL: Cannot compute coadd (minimum=(7900, 15900), maximum=(9899, 17899)): 'lsst.pex.exceptions.exceptions.InvalidParameterErr' object has no attribute 'message'  safeClipAssembleCoadd FATAL: Cannot compute coadd (minimum=(9900, 15900), maximum=(11899, 17899)): 'lsst.pex.exceptions.exceptions.InvalidParameterErr' object has no attribute 'message'  {code}    I believe the root problem is that {{CROSSTALK}} in the {{removeMaskPlanes}} is defined only for HSC, but there is a failure to fail from {{e.message}} (introduced in [this commit|https://github.com/lsst/pipe_tasks/commit/75bb5a08dcb94dc0eeaea403f6292f10bf2c9d12]) doesn't exist in py3. I suggest we should:  1. Remove {{CROSSTALK}} from {{removeMaskPlanes}} (and put it in the obs_subaru overrides).  2. Revert the commit introducing {{e.message}}."
Answer: 1932.0

User story: "When a calexp overlaps a patch by < 1%, the PSF-matching is bad.   !Screen Shot 2017-11-15 at 5.59.58 PM.png|thumbnail!  This is especially problematic now that we're requiring the PSF-matched pixels to agree with a template PSF-matched coadd before the the DIRECT warp's pixels (which are probably fine) in a coadd.    Make it less bad or require that a calexp overlap by a minimum number of pixels before plopping it down.     "
Answer: 53074.0

User story: At least this fragment is hardcoded to write intermediate files into the validate_drp installation dir.  This behavior prevents a user without write permissions on the validate_drp dir from being able to run the driver scripts.  Eg., when running in an official container release.    https://github.com/lsst/validate_drp/blob/873b830a652326e88c0ad2d64c5213733b1db46d/examples/runExample.sh#L81-L82    {code:java}  RUNLIST="${PRODUCT_DIR}"/examples/${CAMERA}.list  makeRunList.py "${YAMLCONFIG}" > "${RUNLIST}"  {code}  
Answer: 18295.0

User story: "Link here in #2 is broken:    https://developer.lsst.io/coding/python_style_guide.html#standard-code-order-should-be-followed"
Answer: 1167.0

User story: "this local installer could be used for running integration tests on travis-ci."
Answer: 61134.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: Catalogs measured from CompareWarpCoadds don't have {{base_PixelFlags_flag_clipped}} set if clipped.   The only reason SafeClipped coadds do is because the coadd masks are manually set before writing out as a workaround for: DM-9953.    {code}          # Set the coadd CLIPPED mask from the footprints since currently pixels that are masked          # do not get propagated          maskExp = retStruct.coaddExposure.getMaskedImage().getMask()          maskExp |= maskClip  {code}     I"m going to add this to CompareWarp, but we should remember to remove it from both when DM-9953 is finished. 
Answer: 477.0

User story: "This epic is started with an examination/test of the FTS3 service, which serves to consolidate  the work with Rucio and GFAL2  of https://jira.lsstcorp.org/browse/DM-10707 and  https://jira.lsstcorp.org/browse/DM-11844 , and transition to initial work to support the spectrograph.    FTS3 (main site http://fts3-service.web.cern.ch , docs http://fts3-docs.web.cern.ch/fts3-docs/ )  is the reliable file transfer service that is used by experiments at CERN (ATLAS, CMS, etc) to  transfer data globally for processing. As such it is a mature, tested service that provides monitoring and summaries of transfers that have been submitted for management.  FTS3 utilizes GFAL2 (https://dmc.web.cern.ch/projects/gfal-2/home) to implement transfers for numerous commonly used protocols with a single API.  Here we show the submission of some test transfers to an FTS3 instance at NCSA using fts3-client commands and the monitoring interfaces that, for example, could enable multiple sites within a collaboration to follow the progress & status of intersite transfers."
Answer: 51883.0

User story: "DM-12454 is showing that we are having trouble with interactions of conda pyflakes with stack pyflakes now that conda is using a much newer version. The easiest solution is to update flake8 to v3.5 and pyflakes to 1.6 in our stack distribution."
Answer: 2950.0

User story: "It happened at least with the {{code_changes}} endpoint that breaks the monitor app when it returns null, example:    https://squash-api.lsst.codes/code_changes/?ci_dataset=demo&metric=AM1"
Answer: 637756.0

User story: "The two tests in `test_jointcal_decam` both fail, due to failed factorizations (non-positive definite matrices). This has always been true, but is made worse by the recent changes to improve the chi2 rejection logic in DM-12602. This may require reprocessing {{validation_data_decam}} as I don't know if the problem is due to bad initial fits/processing or something else.    The tests are currently pseudo-disabled with {{self.assertRaises()}}, since the code now raises {{RuntimeError}} when CHOLMOD fails, but the previously-valid metrics are still in place and most of which should still be valid once this is debugged."
Answer: 41869.0

User story: "Update the code to auto-generate the mask layers for all 32 bits when the mask extension is detected in the image. "
Answer: 125265.0