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: "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_38.  Steps include {{makeSkyMap.py}}, {{singleFrameDriver.py}}, {{mosaic.py}}, {{coaddDriver.py}}, and {{multiBandDriver.py}} (DM-10129/DM-11020).  "
Answer: 9932.0

User story: "Add the public HSC-I2 data at the SXDS field, identified by [~<USER> and [~price] and currently available at {{/scratch/pprice/sxds-i2}}, to {{/datasets/hsc/raw/sxds-i2/}} and ingest them into {{/datasets/hsc/repo}}. "
Answer: 18626.0

User story: "Attend Michael Strauss and Jenny Greene's observational galactic astronomy class to better understand the scientific applications of the deblender."
Answer: 17320.0

User story: "As per RFC-60, the LSST stack guarantees support for Python3 and Python2.7 simultaneously.  While {{pipe_analysis}} is not currently part of the official stack, the port should be done in order to ease a future integration into the main stack."
Answer: 27266.0

User story: "Allow specification of all CLI parameters from Jenkins job."
Answer: 1658.0

User story: "Add plots similar to the visit-level *calibUsed*-only versions added in DM-11322 but at the coadd level. This cannot be done until the flags are propagated to the coadd catalogs when DM-11866 lands."
Answer: 743367.0

User story: "The jenkins {{run-rebuild}} job does to artifact the build logs, other than the {{manifest.txt}} as is done by {{stack-os-matrix}}.  This makes debugging build problems difficult."
Answer: 107.0

User story: "The {{d_2017_09_20}} and {{d_2017_09_21}} nightly releases failed building qserv with this error:    {code:java}                 qserv: 12.1-97-gf3d1871f+1 ....................................:::::  [2017-09-20T07:48:39.795391Z] /usr/lib64/libssl.so.10: undefined reference to `<EMAIL>.10'  :::::  [2017-09-20T07:48:39.795401Z] /usr/lib64/libssl.so.10: undefined reference to `<EMAIL>.10'  :::::  [2017-09-20T07:48:39.795410Z] /usr/lib64/libssl.so.10: undefined reference to `<EMAIL>.10'  :::::  [2017-09-20T07:48:39.795419Z] /usr/lib64/libssl.so.10: undefined reference to `<EMAIL>.10'  :::::  [2017-09-20T07:48:39.795427Z] /usr/lib64/libssl.so.10: undefined reference to `<EMAIL>.10'  :::::  [2017-09-20T07:48:39.795435Z] /usr/lib64/libssl.so.10: undefined reference to `EC_curve_nist2nid@OPENSSL_1.0.1_EC'  :::::  [2017-09-20T07:48:39.795446Z] /usr/lib64/libssl.so.10: undefined reference to `<EMAIL>.10'  :::::  [2017-09-20T07:48:39.795455Z] collect2: error: ld returned 1 exit status  {code}  "
Answer: 7599.0

User story: "Fringe data of calibDate 2017-01-30 or newer (560 files; 112* 5 sets: 2017-01-30 2017-03-21 2017-03-25 2017-04-20 2017-04-27; from DM-8913?)  are not ingested into calibRegistry.sqlite3   at the repo of   {{/scratch/pprice/CALIB-LSST-20170105/}} or  http://tigress-web.princeton.edu/~pprice/CALIB-LSST-20170105/ "
Answer: 191643.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: "Having attended the meeting (DM-11968), write a brief note on what LSST should learn from it, e.g. as a CLO posting."
Answer: 27895.0

User story: "Fix python 3 compatibility issues in the prototype DCR code and StarFast simulator before stackification."
Answer: 956.0

User story: "Specifically:    - Make sure the overhead rate is correct (mail from David Kittelson, 2017-09-19);  - Account for Vanderbei & Naghib work on the scheduler, if applicable."
Answer: 69153.0

User story: From HSC year 1 to year 2 the i band filter was swapped from "i" to "i2".  It is possible to including this directly in the FGCM calibration as a time-variable filter passband (with a step function).
Answer: 57849.0

User story: "With one tract of the HSC RC data, run the equivalent steps of singleFrameDriver + coaddDriver + multiBandDriver using DESDM framework as of DM-12183 and DM-12240 (no newer features for now), based on Stack w_2017_33 + DM-11857 installation in the /project/production/python2/ space.    "
Answer: 63698.0

User story: "On 2017-09-18, [~<USER> circulated guidelines on monthly reporting to T/CAMs and interested others. Please include (an edited version of) this in DMTN-020 and make sure it's linked from https://confluence.lsstcorp.org/display/DM/Useful+DMLT+Links#UsefulDMLTLinks-MonthlyStatusReports."
Answer: 1174547.0

User story: "Miscellaneous fixes in the squash deployment."
Answer: 18800.0

User story: "Add science pipelines docs as a product.  Assign [~<USER> as the product owner.    I'd also like to make some small fixes to other products: e.g. change to [~<USER> as the manager for Alert Production."
Answer: 1176.0

User story: "We are publishing weekly and daily tags to the docker.io registry but it would be convent to also have {{7-stack-lsst_distrib-[dw]_latest}} tags."
Answer: 573258.0

User story: The {{ImageSelector}} subclass imported in https://jira.lsstcorp.org/browse/DM-10977 requires manually specifying minimum and maximum FWHMs for constructing a "best seeing" coadd.  This is limiting for several reasons and requires manual offline analysis to determine those numbers.    This ticket is to change the algorithm to automatically determine the N best-seeing images in a patch for coaddition.
Answer: 364623.0

User story: "Wil, Frossie, Tim, and I have discussed a new change-controlled document Git repository workflow to replace the current policy (release on master, work on draft).    The basic features of the new workflow are:    - Development on master in ticket branches. In general, document development should mirror code development workflows.  - Release branches (named after the corresponding RFC or LCR) that are never merged back to master.  - The release manager backports commits on the release branches (amendments requested by a CCB) to the master branch.  - Tags for docushare upload number and document version.  - A moving tag for the docushare preferred version.    These tags are an API for LSST the Docs (lsst.io) and for future DocuShare automation."
Answer: 92043.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: "Fixes to AL Decorrelation and Zogy implementations discovered during refactor DM-3704 and DMTN writeup DM-11813"
Answer: 1741.0

User story: "We're currently pretty stapled to GitHub.  Let's change that."
Answer: 82.0

User story: "https://pipelines.lsst.io/v/14-0/install/newinstall.html#running-newinstall-sh-in-an-already-set-up-shell"
Answer: 439.0

User story: "If detections exist somewhere in the butler hierarchy the detection task is not being run. This is problematic if the input repository is a reprocessing of data. Add option to force rerunning detections."
Answer: 23412.0

User story: The current behavior of {{newinstall.sh}} is to preserve the value of a pre-existing {{EUPS_PKGROOT}} in the {{loadLSST*}} scripts.  This can result in the initial {{EUPS_PKGROOT}} becoming "stuck" when an end-user attempts to update their env unless they manually {{unset EUPS_PKGROOT}} or use a clean shell env.  Eg.    {code:java}  newinstall.sh -cbt  source ./loadLSST.sh # defines EUPS_PKGROOT    # rerunning newinstsall.sh to update env  newinstall.sh -cbt  source ./loadLSST.sh # original EUPS_PKGROOT value is preserved   {code}    This should not be the default behavior but it may be useful in some cases, so it may be worth adding a cli switch to enable preserving {{EUPS_PKGROOT}}.
Answer: 365.0

User story: "Per RFC-385, we have defined a number of teams and standard labels for use on JIRA. Please ensure these are described in the Developer Guide."
Answer: 45100.0

User story: "Please verify that there are no tickets currently assigned to the following teams (this should be the case after DM-11943 is completed), then delete them:    - DMLT / Management  - T/CAMs  - Project Science  - Process Middleware  - Site Infrastructure"
Answer: 528832.0

User story: Per RFC-385, please ensure that all tickets currently assigned to "old" teams are assigned to one of the "new" teams.    The following direct mappings apply:    - Process Middleware → Data Facility  - Site Infrastructure → Data Facility    The following will need manual intervention to map tickets to whichever team is paying for the work:    - DMLT / Management  - Project Science  - T/CAMs
Answer: 43811.0

User story: "Per RFC-385, please create the following new JIRA teams:    - System Management  - DM Science  - Data Facility"
Answer: 528877.0

User story: "When putting together the compression tests in DM-11332, I added in tests that astropy could read our images with the new version, 2.0.2, before the new version was out. It turns out that astropy 2.0.2 doesn't read our images perfectly correctly, so we need to completely disable the astropy part of the tests until astropy is fixed."
Answer: 12.0

User story: "It would be nice to display all the bands on one plot by disambiguating by color and linestyle. We also have to make sure we display the specifications correctly since some of them also depend on the band."
Answer: 338451.0

User story: "Add daily builds to default menu"
Answer: 91.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: "Create an oauthenticator subclass that auths against cilogon (specifically, NCSA as auth provider there)."
Answer: 15980.0

User story: "Add information on compatible platforms and the DM reference platform (https://github.com/lsst/pipelines_lsst_io/pull/55#issuecomment-330275935) to the prerequisites page on pipelines.lsst.io"
Answer: 104884.0

User story: implement RFC-387.    [~<USER> says: "have a quick look to see if moto requires solely conda packages and can therefore be done as a non-stub package with conda dependencies (since we don't currently have any stack packages that require pip)."
Answer: 1848.0

User story: "mockCoadd only runs the basic assembleCoadd right now, leaving the other varieties untested.     This ticket  will make mockCoadd.py exercise SafeClipAssembleCoadd and CompareWarpAssembleCoadd too.  Test coverage = yay."
Answer: 13045.0

User story: "Data directory has to be create using mariadb image for cloud setup."
Answer: 126466.0

User story: "jointcal is giving these warnings since DM-4141 was implemented:    {code}  Unable to retrieve exit status ('Struct' object has no attribute 'exitStatus')   {code}    To fix this, I think I need to do the following:    * add this to the start of {{run}}: {{exitStatus = 0  # exit status for shell}}  * add {{exitStatus}} to the returned Struct  * wrap most of {{run}} in {{try: except:}}  *  set {{exitStatus=1}} (or some other number) if {{doRaise}} is False and something went wrong.    Anything else I'm missing?"
Answer: 58878.0

User story: "should have been done with DM-11885 yesterday."
Answer: 129.0

User story: "Travis is taking hours and in extreme cases days to start builds in the {{lsst}} org.  This behavior is not being observed in other orgs used by DM such as {{lsst-dm}}."
Answer: 5675.0

User story: "In an [RC run|DM-11189], [~<USER> discovered four CCDs that didn't complete {{ProcessCcdTask}} but did before, and pointed out:  {quote}  Both old and new have `calibrate.astrometry.matcher.maxOffsetPix=250` and `calibrate.photoCal.matcher.maxOffsetPix=300`. Does it matter one is 250 and the other is 300?  {quote}"
Answer: 52.0

User story: "Following DM-11924, get ci_ctio0m9 up and running, create a JIRA component for it, and get it run as part of the standard CI tests."
Answer: 27335.0

User story: "obs_comCam currently has _no_ tests and needs some.    The ticket is to implement some tests to secure it against breaking changes going forward, and once this is done, include it in the {{lsst_obs}} metapackage, and lsst_distrib."
Answer: 578904.0

User story: "I'd like to run {{validate_drp}} on output data products from {{obs_lsstSim}}.  To do this I need to be able to store a full visitId descriptor as something that {{multiMatch}} can index on.  Currently, that's just integers.      Is it possible to adapt (or replace) {{multiMatch}} to accept more general indexing keys to support {{obs_lsstSim}}?"
Answer: 208012.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 match method of DIAObject Collection currently returns the indices of the DIAObjects in the collection that are updated rather than their unique ids. This ticket is to change this return from the former to the latter."
Answer: 28611.0

User story: "Update the documentation at pipelines.lsst.io for the v14.0 release."
Answer: 646618.0

User story: "Image prepuller needs to be more flexible about what it can cache."
Answer: 5758.0

User story: With {{w_2017_36}}, coaddDriver crashes with errors like this:     {code:java}  Invoked with: <lsst.afw.image.tanWcs.TanWcs object at 0x7ff2edbc4e30>, Point2I(0, 0)  Traceback (most recent call last):    File "/software/lsstsw/stack/Linux64/ctrl_pool/13.0-6-gf96f8ec+26/python/lsst/ctrl/pool/pool.py", line 113, in wrapper      return func(*args, **kwargs)    File "/software/lsstsw/stack/Linux64/ctrl_pool/13.0-6-gf96f8ec+26/python/lsst/ctrl/pool/pool.py", line 237, in wrapper      return func(*args, **kwargs)    File "/software/lsstsw/stack/Linux64/ctrl_pool/13.0-6-gf96f8ec+26/python/lsst/ctrl/pool/pool.py", line 817, in reduceNoBalance      return self._reduceQueue(context, reducer, func, list(zip(range(num), dataList)), *args, **kwargs)    File "/software/lsstsw/stack/Linux64/ctrl_pool/13.0-6-gf96f8ec+26/python/lsst/ctrl/pool/pool.py", line 570, in _reduceQueue      resultList = [func(self._getCache(context, i), data, *args, **kwargs) for i, data in queue]    File "/software/lsstsw/stack/Linux64/pipe_drivers/13.0-18-g223e391/python/lsst/pipe/drivers/coaddDriver.py", line 221, in checkTract      for coord in box.getCorners()])  TypeError: pixelToSky(): incompatible function arguments. The following argument types are supported:      1. (self: lsst.afw.image.wcs.wcs.Wcs, arg0: float, arg1: float) -> lsst.afw.coord._coord.Coord      2. (self: lsst.afw.image.wcs.wcs.Wcs, arg0: lsst.afw.geom.coordinates.coordinates.Point2D) -> lsst.afw.coord._coord.Coord      3. (self: lsst.afw.image.wcs.wcs.Wcs, arg0: float, arg1: float, arg2: lsst.afw.geom.angle.angle.Angle, arg3: lsst.afw.geom.angle.angle.Angle) -> None    Invoked with: <lsst.afw.image.tanWcs.TanWcs object at 0x7ff2edbc4e30>, Point2I(0, 0)  application called MPI_Abort(MPI_COMM_WORLD, 1) - process 0  {code}
Answer: 1.0

User story: "Running  {{MosaicTask}} with {{w_2017_36}} and current {{meas_mosaic}}  gives many warnings like this:    {code:java}  root WARN: Failed to read {...}: 'lsst.afw.geom.coordinates.coordinates.Extent2I' object has no attribute 'getWidth'  {code}      "
Answer: 102.0

User story: "Follow up on team/site audit requests, taking actions necessary to resolve issues."
Answer: 198655.0

User story: "Send appropriate list of users to team/site representatives for verification."
Answer: 198661.0

User story: "Generate a list of current LSST systems users organized by team and/or site. This list will be used to by NCSA LSST management to query team/site representatives."
Answer: 1657.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: "Target activities:  * Render the LDF service architecture in enterprise architecture tool. Document our architecture modeling process. Understand the interface with Systems Engineering/MagicDraw documentation..  * Document the Data Backbone production services.  * Document the Data Access Center services from the facility perspective, including replanned Chilean DAC.  * Participate in working group to refine data retention and access policies, and technical and security implications.  * Work CCB and DM change requests/RFCs – e.g., data retention design and costing, compression working group.  * Revisions to technology forecasting and capacity planning.   * Steering -- L1 services, batch production services, containerized application management services, data backbone services, security services, ITC, service management.  * Work with project controls to implement replan in PMCS, pending approval of LCR.  * Refinements to plan, defining verification tests.  * Data Facility participation in commissioning planning."
Answer: 31826.0

User story: "DM-5922 changes the cameraGeometry model, and obs_ctio0m9 needs updating to work with this, (as did most/all of the other obs_packages - somehow this one just got forgotten).    Also, scripts in the {{/scripts}} dir should be exectuable.    Also also, it shouldn't have its own yamlCamera, that has now been moved to {{obs_base}} following DM-11196, so change to import from there  "
Answer: 11945.0

User story: "In DM-11672, I determined that pinhole images are slightly different than the actual pupil.  This ticket is to explore what the impact of that difference may be for fitting wavefronts from donut images.  I see two possible paths:    1) Figure out how to simulate pinhole images in Zemax.  Then use the pinhole image as the pupil to repeat some of the tests done in DM-11043.    2) Implement the detailed Zemax HSC model in batoid (these currently differ in the z-location of the  spider(s).  Verify that the batoid pupil matches the Zemax pupil when the models are identical.  Then trust the batoid predictions for the pinhole images, which I know how to produce already.  Proceed to repeat tests with pinhole instead of pupil a la DM-11043."
Answer: 815326.0

User story: "DM-11329 involved creating a deblender task to run the new deblender on HSC data. This ticket is designed to run that task on a few HSC fields to test its performance before the larger task of running the deblender on a large patch of data and analyzing the results (DM-11330). "
Answer: 1014447.0

User story: "This has already been implemented on the HSC side; transferring it over should be easy enough.    Can be done while simulations are running in the background."
Answer: 109659.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: "After further work on jointcal, I've realized that the basic definition of {{PhotoCalib}} should be multiplicative-{{instFlux * zeroPoint(x,y}}, instead of the current division-{{instFlux * zeroPoint(x,y}}. Fortunately, PhotoCalib isn't really used in the stack yet, so now is the time to fix it. Minor changes will also be required in jointcal and meas_mosaic creation of a PhotoCalib for persistence.    This shouldn't have any impact on the existing API, just on the internal calculations and persistence.    Not RFCing this, as it was defined this way in the original RFC and we changed it during implementation, and all of the current stakeholders have agreed to the change ([slack#dm|https://lsstc.slack.com/archives/C2JPL2DGD/p1505330578000322])."
Answer: 38853.0

User story: Virtually all {{newinstall.sh}} functions should be namespaced to facilitate using the script as a "library" from other scripts.  At present, only the most recently modified functions have been namespaced under {{n8l::}}.
Answer: 8331.0

User story: "{{lsstsw}}'s {{bin/deploy}} script should support select the conda env by git repo sha1 ref, similar to {{newinstall.sh}}, in order to facilitate testing multiple environments simultaneously under CI."
Answer: 703845.0

User story: Our Eigen package has an all-too-clever eupspkg.cfg.sh that "emulates" the CMake build that comes with Eigen - and fails to install files that other CMake packages can use to find it.    This was discovered while testing an external PR on ndarray that improves and cleans up its CMake build.    My planned solution is to simply remove the eupspkg.sh and let Eigen's CMake build do its thing.
Answer: 28658.0

User story: This story captures the current issues deploying squash with minikube.    Things that must be revisited:    - The mechanism to add new entries in /etc/hosts. Currently this is being done in the {{Dockerfile}} which is not ideal.  We should configure the pod using {{hostAliases}}, after tests  kubernetes deployment does not accept this configuration.    https://kubernetes.io/docs/concepts/services-networking/add-entries-to-pod-etc-hosts-with-host-aliases/      - {{nodePort}} is being assigned dynamically when the service is created. However, the {{squash-bokeh}} service needs the {{squash-dash}} host and port for the {{--allow-websocket-origin}} option when running the {{bokeh serve}} while the {{squas-dash}} service needs the {{squash-bokeh}} URL to embed the bokeh scripts. This causes a "chicken and egg" problem when initializing the services.  A solution for that is to make the {{nodePort}} static when the service is created.    For the moment we deciced to drop minikube support and carry on with {{development}} and {{production}} deployments on GKE.  
Answer: 23151.0

User story: "Read relevant sections of Synpipe paper to get up to speed with synpipe"
Answer: 60249.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: "Synpipe contains a lot of scripts for doing various bits of work. It is not clear what all of them do from at first glance as they are mostly not documented. I think some of them should be removed prior to being brought into lsst. This work is to understand what some of these scripts do, add notes where appropriate, and decide what can be removed safely."
Answer: 64753.0

User story: "A refactoring of the weekly-release pipeline inadvertently [silently] broke py2 tarball releases due to the way that closures behave inside of groovy loops."
Answer: 5.0

User story: "Make the following SpanSet operations faster:  * Constructing a SpanSet from a Mask  * Splitting a multi component SpanSet into pieces"
Answer: 8787.0

User story: "This includes understanding the plan as currently constituted and figuring how how to sensible extend it for another three months."
Answer: 111458.0

User story: "There should be minimal effort for the DRP mid-cycle replan, but I need to spend an hour or two to figure out what's on track and what isn't."
Answer: 115937.0

User story: "Send Wil O'Mullane an updated SoW and budget covering work at UW during FY18 NLT 2017-09-15.    This work has been almost entirely carried out by [~<USER> & Nikolina Horvat; I just need to confirm that it reaches its conclusion."
Answer: 12173.0

User story: "Send [~<USER> an updated SoW and budget covering work at Princeton during FY18 NLT 2017-09-15."
Answer: 12174.0

User story: "the old form {{super(<class name>, self)}} should be replaced with {{super()}}"
Answer: 5189.0

User story: "We need to upgrade the nom.tam.fits Java package in Firefly, bringing in the new version in GitHub."
Answer: 44369.0

User story: "ds9 sometimes stops working with XPA. Robert worked out how to fix this is some cases. Write this up as a how-to and post on CLO"
Answer: 5651.0

User story: "Following analysis of RFC-325, a change to the DM level design is proposed for keeping raw images on disk at both the US and Chilean Data Centers, either without compression or with lossless compression.   This ticket covers analyzing the technical and cost impact of this design change, including preparing an Observatory-level change request."
Answer: 1290649.0

User story: "In RFC-325 it is mentioned that we need to understand the latency requirements for accessing image products. The RFC mentions the following latencies:    * to display a movie strip in a UI (expected very short latency; ~1-2 or below)  * to deliver scientifically useful postage stamps for subsequent download or batch processing (longer latency ~20-30 seconds, may be acceptable, assuming decent throughput).    This ticket, though, should also include a latency for virtual product generation (maybe different for each virtual product), and a latency for cutouts of pre-existing products such as coadds.  "
Answer: 930830.0

User story: "The content in the spreadsheet linked from DM-10732 has been agreed upon and can now be imported into MagicDraw to generate a formal requirements document."
Answer: 1279.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: "I neglected to update LDM-463 as part of DM-11332. I'll do it here."
Answer: 10080.0

User story: As specified in RFC-365, use names like "R00" and "S00" instead of "R0,0" "S0,0" for raft and sensor IDs in obs_lsstSim.
Answer: 1603021.0

User story: "The QA scripts in {{pipe_analysis}} do a lot of column accessing & assigning of afw tables.  A recent [community post|https://community.lsst.org/t/afwtable-performance-degradation-using-brackets-vs-explicit-get-for-fields/2236] highlighted the inefficient nature of accessing catalog elements with {{catalog\[fieldName\]}} vs {{catalog.get(fieldName)}} (or, even better, {{catalog.get(filedNameKey)}}).  Please update the code for speed efficiency according to the findings and recommendations of [this community post|https://community.lsst.org/t/afwtable-performance-degradation-using-brackets-vs-explicit-get-for-fields/2236]."
Answer: 5973.0

User story: "See https://community.lsst.org/t/afwtable-performance-degradation-using-brackets-vs-explicit-get-for-fields."
Answer: 1841.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 build / eups distrib tag / tarball completed but the pipeline died in the container "build from eups distrib" before building the jupyterlabdemo image. Presumably, the failure was because {{lsst_distrib}} can no longer be built in the docker default 10GiB root volume size.    The easiest solution would be to replace the eupspkg build with a tarball install.    {code:java}      docker-centos-7: [ 72/111 ]  afw 13.0-97-g247b2c20e ... scons: building terminated because of errors.      docker-centos-7: IOError: [Errno 28] No space left on device:      docker-centos-7: File "/opt/lsst/software/stack/stack/miniconda3-4.2.12-7c8e67/Linux64/scons/2.5.0.lsst2+1/lib/scons/SCons/Script/Main.py", line 1346:      docker-centos-7: _exec_main(parser, values)      docker-centos-7: File "/opt/lsst/software/stack/stack/miniconda3-4.2.12-7c8e67/Linux64/scons/2.5.0.lsst2+1/lib/scons/SCons/Script/Main.py", line 1309:      docker-centos-7: _main(parser)      docker-centos-7: File "/opt/lsst/software/stack/stack/miniconda3-4.2.12-7c8e67/Linux64/scons/2.5.0.lsst2+1/lib/scons/SCons/Script/Main.py", line 1091:      docker-centos-7: nodes = _build_targets(fs, options, targets, target_top)      docker-centos-7: File "/opt/lsst/software/stack/stack/miniconda3-4.2.12-7c8e67/Linux64/scons/2.5.0.lsst2+1/lib/scons/SCons/Script/Main.py", line 1283:      docker-centos-7: jobs.run(postfunc = jobs_postfunc)      docker-centos-7: File "/opt/lsst/software/stack/stack/miniconda3-4.2.12-7c8e67/Linux64/scons/2.5.0.lsst2+1/lib/scons/SCons/Job.py", line 113:      docker-centos-7: postfunc()      docker-centos-7: File "/opt/lsst/software/stack/stack/miniconda3-4.2.12-7c8e67/Linux64/scons/2.5.0.lsst2+1/lib/scons/SCons/Script/Main.py", line 1280:      docker-centos-7: SCons.SConsign.write()      docker-centos-7: File "/opt/lsst/software/stack/stack/miniconda3-4.2.12-7c8e67/Linux64/scons/2.5.0.lsst2+1/lib/scons/SCons/SConsign.py", line 109:      docker-centos-7: syncmethod()      docker-centos-7: File "/opt/lsst/software/stack/stack/miniconda3-4.2.12-7c8e67/Linux64/scons/2.5.0.lsst2+1/lib/scons/SCons/dblite.py", line 119:      docker-centos-7: self._pickle_dump(self._dict, f, 1)      docker-centos-7: Exception IOError: (28, 'No space left on device') in <bound method dblite.__del__ of <SCons.dblite.dblite object at 0x350e490>> ignored      docker-centos-7: + exit -5  {code}  
Answer: 9043.0

User story: "Coord and Wcs will soon switch to using SpherePoint and SkyWcs (DM-11162). Since ap_association is not currently part of the stack this will require updating the code after the ticket mentioned perviously is implemented."
Answer: 286345.0

User story: "Now that flake8 testing can be enabled as part of normal tests, we should document how to do that."
Answer: 8294.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: DM-4878 added a mechanism for propagating flags from the input catalogues to the coadd catalogue indicating stars that were used for measuring the PSF. Since then, DM-9050 added similar calibration flags for astrometry and photometry which should also be added to the list of flags that get propagated from visits to coadds.    The default list of propagated flags is currently:  {code}flags = DictField(keytype=str, itemtype=float,                        default={"calib_psf_candidate": 0.2, "calib_psf_used": 0.2, },                        doc="Source catalog flags to propagate, with the threshold of relative occurrence.")  {code}  Please add the following to this list:   - calib_astrometry_used   - calib_photometry_used   - calib_photometry_reserved
Answer: 528550.0

User story: "Set up and learn to run HSC processing using DESDM framework, so be able to run small tests based on ci_hsc data and Stack {{w_2017_33}}. "
Answer: 24583.0

User story: "There is a bug in the strict monotonicity algorithm that occurs when a faint object is close enough to a bright object that its initial SED is a poor choice, and is closer to the SED of its brighter neighbor. In this case the algorithm completely fails.    To test the projection, I ran a deblend using only the symmetry operator, which resulted in the first attached image. I then ran the projection, which resulted in the 2nd image, which is not strictly monotonic. This ticket is to investigate the origin of this strange behavior."
Answer: 18170.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: {{writeFitsCatalogStorage}} calls {{obj.writeFits(logLoc.locString(), flags=flags)}}, where {{obj}} is "the object to be written". If {{obj}} is an {{afw.Persistable}}, this is an invalid call (Persistable.writeFits doesn't take {{flags}}), so I cannot persist PhotoCalibs in jointcal:    {code}      dataRef.put(photoCalib, 'photoCalib')    File "/home/parejkoj/lsst/lsstsw/stack/Linux64/daf_persistence/13.0-34-g674f0d6/python/lsst/daf/persistence/butlerSubset.py", line 216, in put      self.butlerSubset.butler.put(obj, datasetType, self.dataId, doBackup=doBackup, **rest)    File "/home/parejkoj/lsst/lsstsw/stack/Linux64/daf_persistence/13.0-34-g674f0d6/python/lsst/daf/persistence/butler.py", line 1429, in put      location.getRepository().write(location, obj)    File "/home/parejkoj/lsst/lsstsw/stack/Linux64/daf_persistence/13.0-34-g674f0d6/python/lsst/daf/persistence/repository.py", line 189, in write      return butlerLocationStorage.write(butlerLocation, obj)    File "/home/parejkoj/lsst/lsstsw/stack/Linux64/daf_persistence/13.0-34-g674f0d6/python/lsst/daf/persistence/posixStorage.py", line 264, in write      writeFormatter(butlerLocation, obj)    File "/home/parejkoj/lsst/lsstsw/stack/Linux64/daf_persistence/13.0-34-g674f0d6/python/lsst/daf/persistence/posixStorage.py", line 713, in writeFitsCatalogStorage      obj.writeFits(logLoc.locString(), flags=flags)  TypeError: writeFits(): incompatible function arguments. The following argument types are supported:      1. (self: lsst.afw.table.io.persistable.Persistable, fileName: str, mode: str='w') -> None      2. (self: lsst.afw.table.io.persistable.Persistable, manager: lsst.afw.fits._fits.MemFileManager, mode: str='w') -> None    Invoked with: PhotoCalib(spatially constant with mean: 7.30334e+12 err: 2.15887e+09), '/home/parejkoj/lsst/jointcal/jointcal/tests/.test/JointcalTestCFHTMinimal/run/jointcal-results/06AL01/D3/2006-05-20/r/0/photoCalib-849375-12.fits_mcaoaru'; kwargs: flags=0  {code}
Answer: 1079.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: [This commit|https://github.com/lsst/daf_persistence/commit/674f0d60ffa4549b7335ac12f477951be8892394] is causing {{Exception ignored}} messages on anything that uses an SqlRegistry. I'm quite surprised that this isn't triggering an actual error, but it's making it look like my {{obs_}} and {{jointcal}} package work is failing (due to the tracebacks, as pasted below). It looks like this isn't causing actual errors anywhere because we're not explicitly calling {{del sqlRegistry}}, but rather the interpreter is calling it during cleanup and not being able to propagate the error back up to anything, thus {{Exception Ignored}}.    The simplest fix would be to remove the call to {{super}} in {{SqlRegistry.\_\_del\_\_()}}.    Example traceback:    {code}  ...........x................................................................x.......Exception ignored in: <bound method SqlRegistry.__del__ of <lsst.daf.persistence.registries.SqliteRegistry object at 0x7fbb341e1f28>>  Traceback (most recent call last):    File "/home/parejkoj/lsst/lsstsw/stack/Linux64/daf_persistence/13.0-34-g674f0d6/python/lsst/daf/persistence/registries.py", line 320, in __del__      super(SqlRegistry, self).__del__()  AttributeError: 'super' object has no attribute '__del__'  Exception ignored in: <bound method SqlRegistry.__del__ of <lsst.daf.persistence.registries.SqliteRegistry object at 0x7f6220253c88>>  Traceback (most recent call last):    File "/home/parejkoj/lsst/lsstsw/stack/Linux64/daf_persistence/13.0-34-g674f0d6/python/lsst/daf/persistence/registries.py", line 320, in __del__      super(SqlRegistry, self).__del__()  AttributeError: 'super' object has no attribute '__del__'  Exception ignored in: <bound method SqlRegistry.__del__ of <lsst.daf.persistence.registries.SqliteRegistry object at 0x7fbf908ffb38>>  Traceback (most recent call last):    File "/home/parejkoj/lsst/lsstsw/stack/Linux64/daf_persistence/13.0-34-g674f0d6/python/lsst/daf/persistence/registries.py", line 320, in __del__      super(SqlRegistry, self).__del__()  AttributeError: 'super' object has no attribute '__del__'  Exception ignored in: <bound method SqlRegistry.__del__ of <lsst.daf.persistence.registries.SqliteRegistry object at 0x7fbf908ffbe0>>  Traceback (most recent call last):    File "/home/parejkoj/lsst/lsstsw/stack/Linux64/daf_persistence/13.0-34-g674f0d6/python/lsst/daf/persistence/registries.py", line 320, in __del__      super(SqlRegistry, self).__del__()  AttributeError: 'super' object has no attribute '__del__'  {code}
Answer: 5956.0

User story: "As discussed in RFC-361, the DESDM framework software uses {{,}} as the separator in lists, and software changes would be needed to handle the current patch IDs that contain commas.     For the October HSC run with DESDM, prepare the stack software packages that do not assume commas as patch ID separator based on {{w_2017_33}}.  "
Answer: 18404.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: "Webpack currently inserts such things MODULE_NAME, SCRIPT_NAME, help.base.url we want to change how we are doing build time global varibles so it inserts only one object such as `fireflyGlobals` then we have an accessor function."
Answer: 80537.0

User story: "Document all the build and deployment procedures for Firefly and SUIT portal.  "
Answer: 1480954.0

User story: "It has been requested that the {{shebang}} target should run before {{tests}} as other orders are confusing."
Answer: 11273.0

User story: "Collect use cases for the butler in the context of continuous integration and testing.    Integrate use cases with other use cases."
Answer: 2724.0

User story: "Meet with Keith to generate butler related use cases in the context of commissioning.    Turn meeting notes into fleshed out use cases.    Integrate commissioning use cases with use cases from other contexts."
Answer: 2728.0

User story: "Assemble use cases from the SQuaRE team to inform the butler working group and record them in the working group shared document.    This also involves stepping through the use cases with the WG to look for holes."
Answer: 2741.0

User story: "Following DM-10086, we should replace all uses of {{XYTransform}} with the new AST-backed (DM-6164) version. However, we don't have a good list of what work needs doing or how much effort is involved. Audit the stack, uncover uses of old-school {{XYTransform}}, and file tickets to have them all replaced."
Answer: 290955.0

User story: "The {{$LSSTSW/miniconda/.packages.deployed}} lockfile prevents automatic updates of the conda package set."
Answer: 441821.0

User story: At present, both {{lsstsw/bin/deploy}} and {{newinstall.sh}} import the conda package set into the default env.  This makes it "messy" to update the set of lsst deps in an pre-existing env.  This would be alleviated if a named conda env was created for each conda package set ref.
Answer: 441825.0

User story: "There's a kube cluster at NCSA now.  Make JupyterLab work there."
Answer: 17415.0

User story: "Install kubernetes and configure. Work with developer to modify and document as necessary,"
Answer: 77914.0

User story: "Perform security vetting & follow-up work on elastic services nodes."
Answer: 1.0

User story: "DM-10780 identified the required AP metrics for the first version of the MVP. Implement them."
Answer: 61.0

User story: "We install a globus-gridftp-server from the Open Science Grid yum repositories  as a service to provide access to a Rucio Storage Element on a remote system."
Answer: 4.0

User story: "There's a title parsing bug in the landing page for DMTN-036. This ticket is to create a test case around this document and improve the parsing. The document was prepared with Lyx, but I'm not sure it's related to the issue.    Note that DM-10928 will cover converting LaTeX entities to HTML."
Answer: 1593.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: "With pybind11 v2.2.0 the use of {{\_\_getstate\_\_/\_\_setstate\_\_}} are deprecated. This is currently used in {{daf_base}} and possibly other places. Upgrade these to use either {{\_\_reduce\_\_}} or the new pybind11 pickling API."
Answer: 453604.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 running a {{ctrl_pool}}/{{pipe_driver}} task such as {{singleFrameDriver}}/{{coaddDriver}}/{{multiBandDriver}}, the memory usage reported by {{sacct}} on {{lsst-dev}} seems too small to be true. Research other methods and estimate memory usage of a {{ctrl_pool}}/{{pipe_driver}} job. "
Answer: 39066.0

User story: "Firefly_client needs to be updated after DM-11601"
Answer: 99242.0

User story: "Update the firefly API document after implementation of ticket DM-11601."
Answer: 397433.0

User story: "We have done the preliminary research in ticket DM-9888 on the options for embedded database in Firefly table data support. This ticket is to implement the functions to replace the home-grown capabilities in table data operations. This will enable new functions:  * add calculated columns to the table   * allow more complicated filter on the table  * use the DB functions for sorting, filtering ...    Summary:  * HyperSQL was selected for its performance, built-in functions, and ease of use.  * Caching is changed to last only the during of a session.  * Some SearchProcessors were converted to the new interface while the rest were adapted via a common wrapper."
Answer: 68652.0

User story: "Write up summary of current status and issues with A&L Decorrelation and Zogy"
Answer: 24110.0

User story: "add a boto3 stub package to the stack"
Answer: 10000.0

User story: "per RFC-380 add Cerberus package to the stack."
Answer: 24309.0

User story: "Currently, {{flake8}} is installed with minimal plugins and does not include {{pep8-naming}}. This is problematic on two counts:    # The developer guide explicitly specifies naming tests with a set of ignored codes. These codes are not currently checked.  # If a developer happens to have {{pep8-naming}} installed their build can break because the flake8 testing in CI and in default builds is not testing what it should be.    I am going to add {{pep8-naming}} eups package and enable name testing. This will also require fixing any flake8 problems in the packages that have automated flake8 testing.    I do not believe an RFC is required to add this package as the developer guide already implies we are using it."
Answer: 2547.0

User story: As part of the overall shift to use py3 as the default, instead of py2, the "canonical" {{lsstsw}} based build env used for publishing {{eupspkg}} should also be switched to py3.  This inherently requires removing local state to prevent py2 / py3 linkage problems with previously installed eups products.  Removing the installed eups products would cause the eups {{<version>+<build>}} sequences to reset.  This can be mitigated by doing an eups distrib install of the most recent nightly release when starting from a clean workspace.    Additionally, there has long been a desire to migrate the "canonical" build off of {{lsst-dev}}, primarily motivated by performance issues with the filesystem {{~lsstsw}} resides on.  As this would also inherently involve a loss of state, it is nature to combine these tasks.
Answer: 1600.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: "Create an initial set of summary statistics for DIAObjects for ap_verify."
Answer: 101041.0

User story: "DM-11290 made a pegasus workflow to process a tract of HSC data with stack {{w_2017_28}}. Update this {{pegasus_workflow/rcHsc}} workflow to work with {{w_2017_33}} and generate the dax files for all 3 RC tracts.  Follow the DESDM test plan on whether to include {{MosaicTask}}. "
Answer: 1002821.0

User story: "The good-seeing ImageSelector ported in DM-10977 seems to be extremely slow compared to passing the visit ids directly to selectID.  This ticket is to investigate the cause of the slowness and see if it can be mitigated."
Answer: 53416.0

User story: "Testing on scaled up number of alerts and data volume.  Results to be reported in an update to DMTN-28."
Answer: 64872.0

User story: "Community members are interested in the new Pessimistic matcher due to it's ablity to successfully match sources in ultra dense, galactic plane pointings. Write a short post on LSST community describing its current workings."
Answer: 728786.0

User story: "Update the eups version to {{2.1.3}} for an important py3 compatibility fix."
Answer: 102.0

User story: "With the merge of DM-5922, {{meas_mosaic}} is currently broken with errors like:  {code}  src/mosaicfit.cc:2500:38: error: 'lsst::afw::cameraGeom::CameraTransformMap' has not been declared                       afw::cameraGeom::CameraTransformMap::Transforms newTr;                                        ^  {code}    Please update {{meas_mosaic}} to the new {{afw::cameraGeom}} API."
Answer: 11835.0

User story: "Since DM-4141, running {{makeSkyMap.py}} has this warning in the logs even when the job runs successfully:   {code:java}  root WARN: Unable to retrieve exit status ('NoneType' object has no attribute 'exitStatus'); assuming success  {code}    This message is confusing.  Perhaps the task needs to return an exit status, or the framework may accept {{None}} as a valid return value that can be safely assumed to indicate success?     I've also seen the same warnings in successful MosaicTasks. "
Answer: 1497.0

User story: "For testing purposes, the middleware team has to have an access to its own LSST stack installation on *lsst-dev* remaining under its full control."
Answer: 7.0

User story: "Run the HSC RC reprocessing using a Python 3 stack. "
Answer: 33213.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: This was presumably caused by the the build/publish being repeated several times due to failures, and the most recently published distrib tag not being visible due to s3's eventually consistency when replacing an object, or a slow s3 -> gcloud sync.  Adding a sleep into the release pipeline might largely mitigate this problem.  It might also help to stop running the build/publish/git-tag as a single triggered job and trigger each of these operations separately from the release pipeline.    {code:java}  https://raw.githubusercontent.com/lsst/versiondb/master/manifests/b3044.txt  Traceback (most recent call last):    File "/home/jenkins-slave/workspace/release/tag-git-repos/venv/bin/github-tag-version", line 9, in <module>      load_entry_point('sqre-codekit==3.1.0', 'console_scripts', 'github-tag-version')()    File "/home/jenkins-slave/workspace/release/tag-git-repos/venv/lib/python2.7/site-packages/codekit/cli/github_tag_version.py", line 258, in main      debug=args.debug)    File "/home/jenkins-slave/workspace/release/tag-git-repos/venv/lib/python2.7/site-packages/codekit/codetools.py", line 265, in eups2git_ref      'not match manifest', eups_ref, eupsver)  RuntimeError: ('Something has gone wrong, release file does not match manifest', '13.0-94-ga1c4440+6', '13.0-95-g793934f')  Build step 'Execute shell' marked build as failure  {code}  
Answer: 23047.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 jupyterlabdemo build failed attempting to import eups.    https://ci.lsst.codes/job/sqre/job/infrastructure/job/build-jupyterlabdemo/19/console    {code:java}  Setting up environment to build package 'display_firefly'.  Could not find EUPS product dir for 'display_firefly'; using /usr/share/git/display_firefly.  scons: done reading SConscript files.  scons: Building targets ...  eups declare --force --flavor Linux64 --root /opt/lsst/software/stack/stack/miniconda3-4.2.12-7c8e67/Linux64/display_firefly/unknown -Z /opt/lsst/software/stack/stack/miniconda3-4.2.12-7c8e67 display_firefly unknown  Traceback (most recent call last):    File "/opt/lsst/software/stack/eups/2.1.3/bin/eups", line 12, in <module>      import eups.cmd  ImportError: No module named 'eups'    During handling of the above exception, another exception occurred:    Traceback (most recent call last):    File "/opt/lsst/software/stack/eups/2.1.3/bin/eups", line 15, in <module>      if os.environ.has_key("EUPS_DIR"):  AttributeError: '_Environ' object has no attribute 'has_key'  scons: *** [declare] Error 1  scons: building terminated because of errors.  The command '/bin/sh -c cd /usr/share/git &&      source /opt/lsst/software/stack/loadLSST.bash &&      pip install        https://github.com/Caltech-IPAC/firefly_client/zipball/master &&      git clone https://github.com/lsst/display_firefly &&      cd display_firefly/ups &&      sed -i -e        's/setupRequired(firefly_client)/#setupRequired(firefly_client)/'        display_firefly.table &&      cd .. &&      setup afw &&      scons install force=True &&      scons declare force=True' returned a non-zero code: 2  Docker build failed.  {code}  
Answer: 5836.0