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: [~<USER> and [~<USER> have recently reported high memory usage by {{SafeClipAssembleCoadd}} for examples with either large N (number of warps) or large patch sizes.  For simulated data processed by DESC,   [~<USER> reported 70GB processes coadding 6kX6k patches and unknown N. (Fill this in if you remember)   For DES data, [~<USER> reported memory usage >32GB  with 10kX10k patches and unknown N.  (Note: patches this large are not recommended). Masks were still uint16 at the time.     Profiling reveals that this memory usage was likely due to holding N masks in memory. In this example, patches were 4200X4200, mask pixels = int32, and N=33. 4200*4200*4*33/2**20 = 2220MiB. Full profiling print out attached.     {code}  Line #    Mem usage    Increment   Line Contents  ================================================    1294    556.6 MiB      0.0 MiB       @profile    1295                                 def detectClip(self, exp, tempExpRefList):    1296                                     """!    1297                                     \brief Detect clipped regions on an exposure and set the mask on the individual tempExp masks    ...                               1326    586.2 MiB      0.0 MiB           clipFootprints = []    1327    586.2 MiB      0.0 MiB           clipIndices = []    1328                                 1329                                     # build a list with a mask for each visit which can be modified with clipping information    1330    586.2 MiB      0.0 MiB           tempExpClipList = [tmpExpRef.get(self.getTempExpDatasetName(self.warpType),    1331                                                                      immediate=True).getMaskedImage().getMask() for    1332   2806.8 MiB   2220.7 MiB                              tmpExpRef in tempExpRefList]    1333                                 1334   2813.1 MiB      6.3 MiB           for footprint in footprints.getFootprints():    1335   2813.1 MiB      0.0 MiB               nPixel = footprint.getArea()  {code}    For the simulated data example, N=~1000, patch size = 6KX6K, mask pixel size = uint16 (May 2016) , would have yielded a theoretical usage of 6e3*6e3*2*1000/2**30 = 67GiB.   For the DES, example with the 10kX10k patches any more than 150 visits would have not fit on the 32G system.    Now that we've switched to int32 masks this is even more important, as the memory usage doubles for examples with  large N or large patches. Even with 4k X 4k patches, it only takes N=180 to get memory usage > 10GB.    This ticket will  remove the assumption that N masks can fit in memory from the implementation of {{CompareWarpAssembleCoadd}}. Because the solution will likely be the same for SafeClipAssemble too it will likely be implemented at the same time. 
Answer: 156782.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 test hsc mini wcl does not include filters that need fringe correction, hence no fringe correction is run in that test.  This makes testing the fringe workflow difficult.     Pick images (visit/ccd IDs) for a new wcl with at least one filter with fringe correction  and at least one without fringe correction. This input data set should be as small as possible. "
Answer: 5786.0

User story: "In the submit folder of running DESDM jobs, one file is created for each ccd job in the {{inputwcl}} folder. As a tract can easily have >10k files, this step could take long.  With a test case, test if pointing the submit folder to /ssd would help, compared to having this on GPFS /scratch.  "
Answer: 5610.0

User story: The s3 doc push is done using the pypi {{awscli}} package command {{aws s3 sync}}.  This operation has become extremely slow, and is taking over 10 hours.  I suspect it is a reflection of the 10's of millions of objects in the s3 bucket that is being uploaded to and some sort of "bad" behavior of {{aws s3 sync}}, such as enumerating every object in the bucket.
Answer: 6175.0

User story: "Please add a couple of tweaks to the {{afwDisplay}} interface:  - Add {{setImage}} to set the image being displayed.  This is a no-op for ds9, but needed for e.g. {{display_matplotlib}} if you want to set an e.g. {{zscale}} stretch before displaying.  - Add a way to recover the bitplane colour dict (i.e. to return {{Display.__maskPlaneColors}}); probably by allowing {{name == None}} in {{getMaskPlaneColor}}"
Answer: 12805.0

User story: "The daily backups on community.lsst.org _should_ be uploaded to S3 (builtin Discourse functionality), but they aren't. We are doing weekly DigitalOcean snapshots that mitigate some of the data loss risk, but it would be better if we copied those daily backups.    Check if it's a permissions issue that can be fixed. Alternatively, set up a {{cron}} service that {{scp}}s the backup to S3."
Answer: 1412852.0

User story: "While several updates have been made to the visit and coadd scripts, the run comparison and color analysis scripts have suffered some bitrot.  Please update the visit and coadd run comparison scripts and the coadd color analysis script to current APIs."
Answer: 15536.0

User story: "I was trying to build dax_webserv off master with tag 'dax_latest', both SKIP_DEMO and SKIP_DOCS are checked.    See log for build 302: https://ci.lsst.codes/job/release/job/run-rebuild/301/console    Build parameters:  https://ci.lsst.codes/job/release/job/run-rebuild/302/parameters/  "
Answer: 3829.0

User story: "This ticket is to document the commands used in the (manual) construction of coadds in https://jira.lsstcorp.org/browse/DM-10978 in the DMTN-039 technote."
Answer: 614957.0

User story: "Convert the Butler Use Cases developed by the Working Group into an LDM document ready for DM internal review."
Answer: 100422.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: "If you run {{rebuild -r}} with a ref that does not exist in the products that you are trying to build, {{rebuild}} will build the default refs without complaint. This can sometimes lead to much confusion if a typo has been made in the ref. {{rebuild}} should refuse to complete if none of the products have a matching ref."
Answer: 14.0

User story: "Implementing database support for requests and jobs"
Answer: 9954.0

User story: " Job Scheduler to allow Job execution, tracking, cancellation, preemption, etc. based on job importance and semantics"
Answer: 79557.0

User story: "Abstractions and implementations for the high-level replication operations (the concept of the Replication Job, etc.)"
Answer: 79559.0

User story: "Database schema to support persistent states for requests, complex replication operations, replicas statuses (including file sizes, checksums), and persistent logging."
Answer: 21.0

User story: "Full implementation of the worker-side operations for requests, including incremental (progressive) execution of the lengthy or otherwise resource intensive. Implemented a simple file server to facilitate file migration across worker nodes"
Answer: 20.0

User story: "Refined and improved communication model providing master-side connection pull and logical connection multiplexing"
Answer: 19.0

User story: "Designed a hierarchy of master-side abstractions for various requests (repeal lookups, replications, replica deletion, worker service management, request status inquiries, request cancellation)"
Answer: 19.0

User story: "General design of the system and its architecture. This also includes evaluating technologies and writing simple prototypes to get a sense of each."
Answer: 17.0

User story: "Just as we have a checklist for Stack releases, we should develop one for major system maintenance that might include the following (each of which should also have appropriate warning/preparation times attached):  * Heads-up to the weekly Infrastructure telecon  * Notification in the following places:  ** Confluence System Status page  ** #dm-infrastructure  ** #announce-everyone  ** Community's DM Notifications category (also gatewayed to #general)  * If the verification cluster or other batch system is going down, suspending operation so that jobs can be drained from the system in advance    Having a routinized checklist that is visibly followed should help to reduce miscommunication."
Answer: 756009.0

User story: "Turn DMTN-056 into a polished, internally-consistent proposal for a new Butler design.    This should include:   - Python and SQL interfaces at and above the Registry and Datastore level   - walkthroughs of how the design supports various use cases   - a preliminary list of the concrete Registry and Datastore implementations needed.    This is the ticket for [~<USER>'s piece of the work; DM-12132 captures [~<USER>'s.  "
Answer: 73704.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: "Turn DMTN-056 into a polished, internally-consistent proposal for a new Butler design.    This should include:   - Python and SQL interfaces at and above the Registry and Datastore level   - walkthroughs of how the design supports various use cases   - a preliminary list of the concrete Registry and Datastore implementations needed.    This is the ticket for [~<USER>'s piece of the work; a similar ticket will follow for [~<USER>."
Answer: 74896.0

User story: From the September 12, 2017 PST Meeting:    3) How will LSST report flux measurements?     Short discussion ended without much controversy. Robert, as Calibration Scientist, didn’t raise any objections. Chris expressed unhappiness that we’d call our flux units Jansky, instead perhaps "pseudo-Jansky” (Jansky is a unit for the specific flux, not a broad-band measure). Since no other survey ever had a delta function as their bandpass, every other survey that reported flux in Jansky is guilty, too. If you find this discussion exciting (Robert said he didn’t), please read https://github.com/lsst-pst/fluxunits/blob/master/fluxunits.pdf    Action item: Mario will propose a revised text for DPDD (switch discussion weights  given to Jansky and maggies). 
Answer: 483322.0

User story: "The filter maps are not quite right in validate_drp for HSC any more.  Fix up the filtermaps so that y-band data can run to completion."
Answer: 6873.0

User story: "A new LTS minor release series is out: {{2.71.x}}.  The main reason to update is to keep up with core changes.  The bundled groovy version update may resolve some issues that have been encountered during pipeline script development.  The ssh update may remove a irritating log message.    https://jenkins.io/changelog-stable/  https://jenkins.io/doc/upgrade-guide/2.73/#upgrading-to-jenkins-lts-2-73-1    Jenkins 2.89.1 was released 2017-12-06."
Answer: 97637.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: "Holding place for 15-minute presentation plus 30-minute jam session."
Answer: 8775.0

User story: "We want to use CILogon as source of truth, but also do the GitHub magic."
Answer: 66271.0

User story: "Working with DAX team on MetaServ API v1.   Define use cases: https://confluence.lsstcorp.org/display/DM/Metadata+Service   Design API   Test API and give feedback"
Answer: 323968.0

User story: "Work with DAX team in testing and refining the ImageServ API -v1    relevant information from DAX team:  https://confluence.lsstcorp.org/display/DM/ImageServ+API+-+v1  JSON schema: https://github.com/lsst/dax_imgserv/blob/master/python/lsst/dax/imgserv/config/imgserv_api_v1.schema  Test cases:  https://github.com/lsst/dax_imgserv/tree/master/integration/input_v1  "
Answer: 178598.0

User story: "[~<USER> reports that {{ci_hsc}} is now py3 compatible and build-able via {{stack-os-matrix}}.  This is the last end-user facing DM job that triggers another job and the last user of {{science-pipelines/py2-boondocks}}.    Does anyone object to the removal of the {{ci_hsc}} job?"
Answer: 131.0

User story: "As it stands now, fake sources that are added according to wcs positions are using the wcs provided by the telescope which can be off. If adding fake sources this should happen after wcs has been updated. This also means that detection and measurements will need to be re-run such that the fake sources are inserted,"
Answer: 31532.0

User story: "Create dev/user documentation for the DM Jenkins instance.  Presumably, to supplant or be linked to from:    https://developer.lsst.io/processes/workflow.html?highlight=jenkins#testing-with-jenkins"
Answer: 78372.0

User story: Add the "apr-iconv" package to our stack. This is intended to prevent apr_utils from accidentally picking up iconv from miniconda or anaconda. Anaconda's iconv iconv renames the symbols, which causes apr_utils to fail to load)
Answer: 495331.0

User story: "The specification for the data model of imageREST_v1 is based on the standard JSON schema specification: http://json-schema.org.    The schema validator package for JSON-based queries is available on Github: https://github.com/Julian/jsonschema.  "
Answer: 84001.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 illuminated portions of off-axis pupils currently being generated for HSC are off-center in their arrays since the vignetting by the first HSC lens introduces obscuration at a particular azimuthal angle, but the center of the array corresponds to the center of the unvignetted primary mirror.  In Zemax, the pupil is recentered after taking into account this additional obscuration.  I suspect that this makes the Zernike polynomials on the centered pupil closer to orthogonal than the Zernike polynomials on the uncentered pupil.  I'm guessing that the effect on the PSF is just a shift in the image, but this needs to be checked.    This ticket is to a) investigate the orthogonality of the Zernike polynomials on centered/uncentered vignetted pupils and what effects centering has on the implied PSFs, and b) if it looks interesting, add (optional) pupil recentering to the afw pupil API."
Answer: 47968.0

User story: "Add input validation for the new {{SpherePoint(double, double, AngleUnits)}} constructor"
Answer: 253.0

User story: "Add  debugging plots to CompareWarpAssembleCoaddTask to be generated when assembleCoadd.py --warpCompareCoadd --debug is run"
Answer: 46611.0

User story: Note that these jobs are completing all work but the overall job is failing due to the "archiving" step no longer being inside of a {{node}} block due to recent refactoring of error handling.  The fix is trivial.     {code:java}  org.jenkinsci.plugins.workflow.steps.MissingContextVariableException: Required context class hudson.FilePath is missing  {code}    
Answer: 1685.0

User story: "According to nagios, squash/bokeh have been down for ~4 days now:    {{(for 4d 23h 9m 46s)  (Has been acknowledged)}}"
Answer: 89.0

User story: "Following DM-12070, we are now running ci_ctio0m9 as part of lsst_ci. There's therefore no reason for it to be a separate timer job in Jenkins. Please disable it."
Answer: 97.0

User story: "The source code of the DESDM framework is kept under *Subversion* version control system. The goal is to convert selected revisions/tags of its packages to git repositories."
Answer: 1.0

User story: "We've started reviewing the proposed SSObject schema with the Solar System Science Collaboration. The spreadsheet we use to record the progress of this discussion is at:    https://docs.google.com/spreadsheets/d/1E0rTlvuJC0CvpLNsuWLK0x70uhpZww4v6GB5QkiQr-Q/edit?usp=sharing    This JIRA ticket is to track that work & lead to an LCR for any modifications."
Answer: 609063.0

User story: "Testing on scaled up producers. Results to be reported in an update to DMTN-28.  "
Answer: 51784.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "As presently specified in the DPDD, we only provide (aperture corrected) aperture flux for DIASources. While this is fine for point sources, for extended objects (comets) it would be useful to measure in multiple radii (similar to what we do for Objects). Even a small fixed number of radii may be helpful.    This addition has been proposed by the Solar System Science Collaboration, to better enable comet (and cometary phenomena)-related science cases."
Answer: 415441.0

User story: "Since suppressing the property name error doesn't have JL support yet, we will instead instruct the user to ignore the error.  Ugh."
Answer: 1506.0

User story: "Spectograph component has been implemented.  It has been updated with new message glossary.  It can send, receive messages and pulls a CCD from the spectrograph.  The receipt file has been implemented. The use of this file is to be determined.  Confluence page for spectograph messages are updated.  Test for spectograph_component is in progress"
Answer: 5768.0

User story: "Sometimes there's an extra error dialog you need to click through when you do shutdown from the save-and-quit menu.  This is because the refresh fires but the underlying app has gone away."
Answer: 11440.0

User story: "Add {{obs_comCam}} to https://github.com/lsst/repos"
Answer: 6.0

User story: "For PDF landing pages (Lander project), determine the revision date metadata for an lsstdoc-based LaTeX document through these methods, in priority:    1. Date provided in {{\date}} command  2. Git timestamp for the most recent commit that affected document content.  3. Run time    This will make the revision dates posted on the document landing pages more consistent with the dates printed in the PDF. It will also prevent the post revision date from changing for administrative commits to a document's repo."
Answer: 9977.0

User story: "This needed enhancement addresses the critical case that occurs when a consumer thread throws an exception and effectively dies. Now the death of a thread is detected and restarted. In addition, thread cleanup is now handled by events maintained in the thread manager."
Answer: 177083.0

User story: "Write up technical notes on current status and findings related to consolidated systems management."
Answer: 265100.0

User story: "Evaluate Katello.  * Is this an alternative to pakrat?  * Pro's & con's of integration with foreman"
Answer: 35972.0

User story: "Evaluate the Foreman management tool for physical and virtual servers.  * Integrate with existing puppet deployment  * Bare metal OS deployment  * VM provisioning  * IPMI control to force pxeboot  * Serial over LAN support  * Remote deployment (all the above to a remote location)"
Answer: 264692.0

User story: "Evaluate the pakrat package for managing yum repositories."
Answer: 5622.0

User story: "The current interactive QA system is designed for point-wise metrics that have a value for each source.  We also need metrics that are calculated over spatial bins.  Extend the QA system to handle this."
Answer: 629980.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: "Implementation ticket for RFC-391.    Get {{obs_ctio0m9}} and {{obs_comCam}} included in {{lsst_obs}} and thus {{lsst_distrib}}"
Answer: 2789.0

User story: "There is existing comment inside imageREST_v1.py mentioning the desirability of writing Image object to data object in memory instead of to a temporary FITS file, then reading it into memory, to improve image response performance and avoidance of using temp files in the local file system.     Since afw.Image does not provide an existing/ready method to do so, some investigation of alternative ways of doing this is warranted.      "
Answer: 20471.0

User story: "Create a 20 minute presentation on the deblender and the LSST's current plan for photometry in crowded fields."
Answer: 1815.0

User story: "Many of the requirements have comments from other members.  Reword, clarify, or remove requirements as needed."
Answer: 2.0

User story: "Add monitor tools and dashboard to check cluster and nodes health"
Answer: 185797.0

User story: "GPFS won't be mounted no Nebula cluster, using Cinder Volume instead for persistent storage mounted on the master node and serve using NFS"
Answer: 6.0

User story: "Docker does not behave very well inside Openstack in our Nebula implementation, we have adapted a Daemon Set from kubernetes to run on every node to pull big images"
Answer: 185801.0

User story: "Allow ingress rules with SSL security for services in the cluster"
Answer: 10.0

User story: "Minimal support, maintenance , bug fixing, upgrades and general admin work for the kubernetes cluster in nebula"
Answer: 185809.0

User story: "test_methods.py issues {{DeprecationWarnings}} while testing deprecated assert methods. As of Python 3.2 unittest offers {{assertWarns}} which would allow us to make sure the deprecated methods actually do issue the appropriate warning, and stop pytest from complaining.    The trick will be making sure the tests run under older versions of Python (even if pytest warns in that situation).  "
Answer: 202.0

User story: "Work on requirements spreadsheet (writing, reading, commenting)."
Answer: 4110.0

User story: "Normally 2 hours calls on Tues and Thurs.  4-hour calls the 26th and 28th."
Answer: 4112.0

User story: "We don't have unlimited space for images...so we should dump the ones that do not appear on our current menu.  If they're in use, docker rmi will fail so we won't trash existing containers"
Answer: 318.0

User story: "Recent improvements to the {{firefly_client}} package need to be gathered into a v1.2 release due to some API changes. At an appropriate point, tag this version, publish to PyPI (for {{pip install firefly_client}}, and synchronize the fork in the lsst Github org."
Answer: 72029.0

User story: "Investigate the memory usage with one example of coaddDriver.  Consider one fixed small set of input data."
Answer: 18769.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://confluence.lsstcorp.org/display/LDMDG/git+development+guidelines+for+LSST  The above page provides guidelines on using git which duplicate (and maybe more useful than) the material in the developer guide. Please transfer any useful information to the developer guide and deprecate this page."
Answer: 507.0

User story: "As the {{/project}} disk space is filling up and more than 4 newer processed repos have been generated, please copy (rsync using a worker node) the processed w_2017_30 repo of HSC RC data to {{/scratch}} and make a softlink from {{/project/hsc_rc/}}"
Answer: 10128.0

User story: "As the {{/project}} disk space is filling up and more than 4 newer processed repos have been generated, please copy (rsync using a worker node) the processed w_2017_27 repo of HSC RC data to {{/scratch}} and make a softlink from {{/project/hsc_rc/}}"
Answer: 10128.0

User story: "Run 'clean', ie, starting from a sanitized build env with no existing state, builds of {{lsst_distrib}}, {{qserv_distrib}}, and {{dax_webserv}} on a nightly basis."
Answer: 10170.0

User story: "The {{d_2017_08_28}} nightly-release pipeline failed, after completion all triggered jobs, while archiving:    {code:java}  groovy.lang.MissingPropertyException: No such property: euptsTag for class: groovy.lang.Binding  {code}    which is a simple typo."
Answer: 90.0

User story: "In order to explore using the interactive QA plots at an interesting scale, run the {{pipe_analysis}} scripts on the full PDR1 dataset at lsst-dev.  Most importantly these should create the parquet tables (DM-12030), but they can also make the static plots."
Answer: 159347.0

User story: "After setting a recipe in obs_subaru, I'm confronted with the following error:  {code}  RuntimeError: Recipes provided in /scratch/pprice/compression/obs_subaru/policy/writeRecipes.yaml may not override those in /software/lsstsw/stack/Linux64/obs_base/13.0-51-ga83c964/policy/writeRecipes.yaml: set(['FitsStorage'])  {code}    The test for whether we're overriding needs to be pushed down a level."
Answer: 120585.0

User story: "Initial document design of the Header Client and review internally. This will be the prime input into a design review for the Header Client."
Answer: 9846.0

User story: "Together with [~<USER>, ensure that the pipe_analysis scripts efficiently & effectively dump all the information that Tim's plotting scripts need to Parquet files without wasting time generating redundant plots or stripping out useful data."
Answer: 73243.0

User story: "In DM-11727 we are updating the version checking to require new minimum versions for python/numpy/matplotlib/astropy. The shared stack needs to be updated before we can force the version checking.    We announced on community that this would happen in early October 2018 but we can't update until the shared stack has had {{conda update astropy}} (etc) run on it. Since the shared stack is python2.7 this should not require a rebuild of the stack, just an update of the packages."
Answer: 56299.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 reference, dax_imgserv is implemented in Python as a web service in flask 0.12.  Furthermore dax_imgserv relies on Butler to retrieve images from image datasets or repositories. Butler in turn uses afw to load FITS files into objects, i.e. afw.Image.     Instantiating Butler takes noticeable time and causes significant latency when servicing user requests. The nature of this latency needs to be analyzed and better understood, identifying possible areas to reduce this latency issue."
Answer: 62070.0

User story: "Several {{newintall.sh}} bugfixes have merged to since the {{14.0}} branch was split off.  These fixes should be included in the next v14 rc."
Answer: 359.0

User story: "Add a paragraph to LDM-294 about how the SST should handle regression monitoring.  The draft is:    All KPMs and other regression monitoring metrics should be presented to the SQuaSH tool and recalculated on a regular cadence (daily if possible).  On a biweekly bases, the SST will review the traces of the various metrics to attempt to identify regressions in performance over the past two week period.  If regressions are identified in any of the metrics, the SST will identify a team to take lead on investigating the regression and will communicate with the DM Project Manager to schedule the necessary resources."
Answer: 7235.0

User story: "I've been asked to outline the DRP pipelines to kick off DESC's Blending Task Force on Monday, October 2 at 12pm.  This will take some preparation.  "
Answer: 7042.0

User story: "In order to make interactive QA plots such as DM-11682, we need to persist parquet files containing the compiled data that are used to make the static matplotlib plots.  Admittedly, this should be a temporary step until all the source info is easily loadable from a column-store database, but for now it is necessary.  At the visit level it might be less so, but I'll do it anyway.  This is probably technically part of DM-10859, but I thought it might be useful to get it in its own ticket so it can be merged quickly."
Answer: 7169.0

User story: Now that the stack supports tile compression of FITS files, and a number of bugs related to handling of FITS image metadata were fixed (DM-11332), I can recompress the images (really just holders of the metadata) I zeroed out in {{testdata_jointcal}} so that they aren't just gzipped files. Once done I can use the new butler calls (DM-9060, DM-9153) to directly access that metadata. This should drastically speed up file ingestion for jointcal.    The compression step is probably best done via a short bash script that runs gunzip and then fpack, with some carefully chosen parameters (the files are zeroed, so it probably doesn't matter much which compression scheme is selected).    If this works, we can close DM-6911 as well, as that probably got fixed "for free" as part of DM-11332.
Answer: 30188.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: {code:java}  Craig Loomis [10:40 AM]   A fresh `https://raw.githubusercontent.com/lsst/lsst/master/scripts/newinstall.sh`, run without installing a miniconda, generates a loadLSST.bash which contains a troublesome `export PATH="/bin:${PATH}"`. Not entirely sure what is supposed to be happening with the `miniconda_path`, etc. variables in the use-user-anaconda case. MacOS 10.12, anaconda 4.4.0.      <USER> [10:42 AM]   @josh  I think you need to protect `export PATH="${miniconda_path}/bin:${PATH}"` so that it only happens if we installed miniconda. (edited)      [10:43]   actually it’s this line sorry:  ```local cmd_setup_miniconda="export PATH=\"${miniconda_path}/bin:\${PATH}\""```  {code}  
Answer: 1320.0

User story: "The various {{lsst.afw.geom.Transform}} classes are not pickleable. {{lsst.afw.geom.XYTransform}} is, so the new {{Transform}} class provides less functionality than we had before. This is easy to remedy because there are already methods that read and write to strings."
Answer: 22116.0

User story: "The purpose of this is to see what types of issues arise in trying to deploy OpenShift Origin."
Answer: 4346.0

User story: "Research RedHat OpenShift Container Application Platform.  Bucket epic to bridge gap between 17a and October planning package epics.    This is ongoing research; deliverable for September consists of scripts and installation notes in Github."
Answer: 51735.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: A "tarball" build of {{v14_0_rc2}} is failing in the {{scons}} smoke test.  Presumably, due to the smoke test using {{lsst/base}} on {{master}}, which has since diverged from the {{v14}} branch.    {code:java}  ++ scons  scons: Reading SConscript files ...  EUPS integration: enabled  Checking who built the CC compiler...gcc=4.8.5  CC is gcc version 4.8.5  Checking for C++11 support  Checking whether the C++ compiler works... yes  C++11 supported with '-std=c++11'  Setting up environment to build package 'base'.  TypeError: tests() got an unexpected keyword argument 'pySingles':    File "/smoke/base/SConstruct", line 4:      scripts.BasicSConstruct("base")    File "/smoke/stack/miniconda3-4.3.21-10a4fa6/Linux64/sconsUtils/13.0-7-gc601e82+1/python/lsst/sconsUtils/scripts.py", line 65:      versionModuleName, noCfgFile=noCfgFile, sconscriptOrder=sconscriptOrder)    File "/smoke/stack/miniconda3-4.3.21-10a4fa6/Linux64/sconsUtils/13.0-7-gc601e82+1/python/lsst/sconsUtils/scripts.py", line 137:      SConscript(script)    File "/smoke/stack/miniconda3-4.3.21-10a4fa6/Linux64/scons/2.5.0.lsst2+1/lib/scons/SCons/Script/SConscript.py", line 604:      return method(*args, **kw)    File "/smoke/stack/miniconda3-4.3.21-10a4fa6/Linux64/scons/2.5.0.lsst2+1/lib/scons/SCons/Script/SConscript.py", line 541:      return _SConscript(self.fs, *files, **subst_kw)    File "/smoke/stack/miniconda3-4.3.21-10a4fa6/Linux64/scons/2.5.0.lsst2+1/lib/scons/SCons/Script/SConscript.py", line 250:      exec _file_ in call_stack[-1].globals    File "/smoke/base/tests/SConscript", line 6:      pySingles=['testModuleImporter2.py'], pyList=[])  {code}  
Answer: 11410.0

User story: When a pytest-xdist worker process ("slave", if you must) segfaults, it is automatically restarted. If the segfault is persistent, it will immediately segfault again, and so on, ad infinitum (or, at least, until you run out of processes and are kicked off the system).    Per discussion of  2017-09-26 on #dm-pytest, the solution seems to be to specify {{--max-slave-restart=0}} when invoking Pytest. Please implement that, or some equivalent fix.
Answer: 29044.0

User story: Transform the calibration validity ranges of the "20170105" calibration registry into the "ops_calibration_lookup" table in the oracle db. 
Answer: 24524.0

User story: "Explain to [~<USER> how to use k8s on ccqserv100 to ccqserv124 and improve related documentation."
Answer: 93943.0

User story: Per e-mail with [~<USER> of 2017-09-25 (and around then), he prefers that epics which have been scheduled in PMCS not be marked as "won't fix", but rather:    - That they must contain a single story;  - That story may be marked as "won't fix";  - The epic should then be marked as "done".    This process is documented: he is going to check exactly where. At that point, we should make sure that DMTN-020 is consistent with his documentation.
Answer: 256688.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Currently, meas_mosaic uses its own persistence format for its calculations of new catalog values, etc. From DM-10007, meas_mosaic now persists an {{afw.image.PhotoCalib}} containing the same model. We should switch to using that persistence format for the catalog updates, to make the switch to jointcal more trivial.    Once done, we can more reliably confirm that the changes in DM-11905 did not affect meas_mosaic's {{PhotoCalib}} persistence by regenerating the files in the {{tests/data//}} directory (I had manually hacked them to work for the ticket itself) and re-running {{tests/test_FluxFitBoundedField.py}}."
Answer: 577025.0

User story: "Go through CI, commissioning, and SQuaRE use cases and derive requirements for them."
Answer: 1.0

User story: "Needs some updates about how to use other authenticators/volume strategies."
Answer: 5883.0

User story: "Starting with the min test wcl file from DM-10474, go through the junk tar balls and add new filetypes as needed.  Ignore those that were renamed to allow Butler to locate the files.     Files needed to be taken care of are:   - SRCMATCH  - SRCMATCHFULL  - ICSRC  - BKGD  - metadata boost files  - thumbs pngs  If possible, also do:  - (output) schema files  - (output) config files  - package version pickes    "
Answer: 15543.0

User story: "Firefly needs to be able to show different groups of images that can be search based on the context that is is running in. Image master data should know the UI (title, project, help, tooltip, etc) details of the data as well as how to retrieve a selected image.    This ticket will implement that other tickets will build on."
Answer: 7929.0

User story: "The {{w_2017_38}} weekly-release is still in progress. In appears that there may have been some sort of network lurch over the weekend that interrupted the ssh connections between the master and the osx build nodes.  Jenkins reconnected via ssh and was displaying the tarball build pipeline script fragment as running on an osx node, but not progress was being made.  The tarball builds needed to be manually aborted so the {{weekly-release}} pipeline would retry.    I suspect that setting timeouts on the tarball builds would avoid this. Also, splitting the tarball builds up into one build per python major version/os/conda env, would make retrying vastly more efficient."
Answer: 4263.0

User story: "Part two of the v14 release installation instructions update. This ticket follows on DM-10636, which is already merged to the v14 integration branch. The goals of this ticket are:    - Copy edit new content from DM-10636.  - Improve installation instructions based on early user feedback (particularly around binaries).    See also DM-11936 for an update to how supported platforms are documented."
Answer: 42129.0

User story: "Following discussion at the 2017 Project & Community Workshop, implement a minimal test suite for firefly_client. A minimum automated test is to import the package. "
Answer: 72379.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: "Following discussions at the 2017 Project & Community Workshop, add a minimal test suite to the display_firefly package. Since a Firefly server is needed to use this package, a minimal test suite can implement an import test. Interactive user tests are already included in the afw.display package."
Answer: 56596.0

User story: "obs_test Camera has an incorrect focal plane to field angle transform and the distortion coefficient is incorrectly labeled. The radial coefficients describe field angle to focal plane, and the C3 term is in 1/rad^2. Fix this and provide a unit test in obs_base that sanity-checks the plate scale by converting focal plane to field angle near 0,0 and comparing against the known camera plate scale."
Answer: 146690.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: Begin forwarded message:    From: Knut Olsen <<EMAIL>>  Subject: Re: [LSST-MilkyWay-etc] A few more astrometric thoughts  Date: September 22, 2017 at 9:57:06 AM PDT  To: <USER><<EMAIL>>  Cc: John Gizis <<EMAIL>>, "John K. Parejko" <<EMAIL>, stubbs <<EMAIL>>, <USER><<EMAIL>>, <EMAIL>    Hi Zeljko,     I understood this to be a problem from reactions to one of the metrics that came out of the first cadence workshop in Phoenix.  The fast transient group wanted a metric that used the difference in flux between snaps, and the feedback we got (from K-T, I believe) was that the snaps would not be differenced for this purpose.  But I see the data product indeed defined in the DPDD as you note.  However, if you read the intro to section 1.2, it says:    "A raw image (baselined as a pair of successive 15-second exposures, called snaps), delivered by the LSST camera, is processed by the Instrument Signature Removal (ISR) pipeline, to produce a single-visit image with, at least conceptually, counts proportional to photon flux entering the telescope pupil (in reality, there are many additional optical, pixel and bandpass effects, including random counting noise and various subtle systematic errors, that are treated during subsequent processing). This single-visit image processed by the ISR is called a “Processed Visit Image” and its main data structures include counts, their variance and various masks, all defined on per pixel basis. After the ISR step is completed, the pixel values and their variance are not modified any more. These single-visit images are used downstream to produce coadded and difference images. The rest of the processing is essentially a modelbased interpretation of imaging observations that includes numerous astrophysical and other assumptions.”    The paragraph sure makes it appear that the snaps are used to create single-visit images, and then these are used in the DIA pipeline.  But good to know that this impression is incorrect!    Knut        bq. On Sep 22, 2017, at 9:36 AM, <USER><<EMAIL>> wrote:  bq.   bq.            Hi Knut,  bq.   bq. On Sep 22, 2017, at 9:28 AM, Knut Olsen <<EMAIL>> wrote:  bq. Hi Zeljko,  bq.  I’m very likely not up to date, but I thought that there was no intention to use the exposure pairs to look for fast transients, as this would impose a large new burden on DM.  Has this changed?  bq.   bq.   bq. DPDD (ls.st/dpdd) says on page 19 that DIASource table will list diffFlux (and its error),   bq. defined as:   bq. "Calibrated flux for point source model centered on radec but measured on the   bq.   bq. difference of snaps comprising this visit”    bq. (see also footnote 46).   bq.   bq.   bq.   bq. Do you know what is the origin of the claim that "there was no intention to use the   bq.   bq. exposure pairs to look for fast transients”? I don’t recall hearing it or reading it. If there are  bq.   bq. any docs claiming something like that, they should be fixed.   bq.   bq.             Cheers, Zeljko   bq.        
Answer: 947633.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}} needs to access various columns from source catalogs to do its work.  Not all of these have slots defined.  I am going to add the slot that's missing so the validation scripts are more future proof."
Answer: 5795.0

User story: "Similar to SwiftStorage, this allows existing LSST science code that uses the Butler for local filesystem repositories to send those objects to repositories in S3 containers."
Answer: 82088.0

User story: "A 30% DR1 dataset is needed at IN2P3 to use as a basis for the F17 KPM measurements.    Given the amount of RAM on the computers, the chunks are already larger than they should be. The data will need to be partitioned into smaller chunks."
Answer: 190429.0

User story: "Zogy suffers if there is inaccurate relative calibration between the two images. This issue can be seen in DMTN-061. Not clear how frequently this occurs. This can be fixed by fitting for the relative calibration and setting them as the Fr and Fn parameters for Zogy, or else ensuring that the LSST stack calibration is accurate. Another possibility is that the images are not being loaded for Zogy correctly or that a (already measured?) flux calibration should be applied to the pixels in the images before running Zogy."
Answer: 1259032.0

User story: "Occasionally seen with both Zogy and AL Decorrelation: depending upon the dimensions of PSFs/kernels/input images, the resulting Zogy diffim or decorrelated diffim can have an erroneous 1-pixel offset (shift). Several attempts have been made to fix this but it still occurs on occasion."
Answer: 1297560.0

User story: "The {{d_2017_09_22}} nightly-release failed building the {{docker.io/lsstsqre/centos:7-stack-lsst_distrib-...}} image.    {code:java}  Reading configuration data from /opt/lsst/software/stack/stack/miniconda3-4.3.21-10a4fa6/ups_db/_servers_/https://eups.lsst.codes/stack/redhat/el7/gcc-system/miniconda3-4.2.12-7c8e67/config.txt  Tag d_2017_09_22 not supported at https://eups.lsst.codes/stack/redhat/el7/gcc-system/miniconda3-4.2.12-7c8e67  Tag d_2017_09_22 not supported at https://eups.lsst.codes/stack/redhat/el7/gcc-system/miniconda3-4.2.12-7c8e67  eups distrib: Product lsst_distrib d_2017_09_22 not found in any package repository  Removing lockfile /opt/lsst/software/stack/stack/miniconda3-4.3.21-10a4fa6/.lockDir/exclusive-lsst.17  {code}    There are actually two problems here.      # https://github.com/lsst-sqre/docker-tarballs/blob/master/Dockerfile has a hardcoded {{EUPS_PKGROOT=https://eups.lsst.codes/stack/redhat/el7/gcc-system/miniconda3-4.2.12-7c8e67}}, which is no longer the latest env.    # No tarballs for {{miniconda3-4.2.12-7c8e67}} were built, likely caused by this commit https://github.com/lsst-sqre/jenkins-dm-jobs/commit/0d34bcf75e09a4827eecebce35ce21aa34df66d7"
Answer: 5179.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: "{{newinstall.sh}} is failing on OSX due to a recently routine cleanup that removed the usage of {{eval}}.  It seems that {{declare -g}} is a bash 4.x-ism.    {code:java}  bash: line 708: declare: -g: invalid option  declare: usage: declare [-afFirtx] [-p] [name[=value] ...]  script returned exit code 2  {code}      bash 3.2.57:    {code:java}  $ help declare  declare: declare [-afFirtx] [-p] [name[=value] ...]      Declare variables and/or give them attributes.  If no NAMEs are      given, then display the values of variables instead.  The -p option      will display the attributes and values of each NAME.            The flags are:              -a to make NAMEs arrays (if supported)        -f to select from among function names only        -F to display function names (and line number and source file name if       debugging) without definitions        -i to make NAMEs have the `integer' attribute        -r to make NAMEs readonly        -t to make NAMEs have the `trace' attribute        -x to make NAMEs export            Variables with the integer attribute have arithmetic evaluation (see      `let') done when the variable is assigned to.            When displaying values of variables, -f displays a function's name      and definition.  The -F option restricts the display to function      name only.            Using `+' instead of `-' turns off the given attribute instead.  When      used in a function, makes NAMEs local, as with the `local' command.    {code}  "
Answer: 48.0

User story: "to save column metadata when writing afw_table to databases, Butler formatters need a way to be able to save that information with the data in the database."
Answer: 83491.0

User story: "A DM tech note DMTN-060 is written to summarize the work done in epic DM-10707. "
Answer: 2.0

User story: "for evolvability we need to track the serialization version of afw_tables that are written to the database."
Answer: 83495.0

User story: "The *base_InputCount* plugin adds a *base_InputCount_value* field to the output catalogs that reports the {{doc=Number of images contributing at center, not including any clipping}} per object.  Our HSC collaborators have noticed some potential issues with the setting of this value (namely that some objects having non-zero flux have a *base_InputCount_value = 0*).  They have requested a plot showing the value of this field be added to the qa scripts.  In particular, they would like this to be a sky view with the actual image as background if possible (i.e. if this can be made readable & informative in the context of these static plots.  Some sub-selection of samples may be required to avoid overcrowding.)"
Answer: 615230.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_40.  Steps include {{makeSkyMap.py}}, {{singleFrameDriver.py}}, {{mosaic.py}}, {{coaddDriver.py}}, and {{multiBandDriver.py}} (DM-10129/DM-11020).  "
Answer: 31681.0