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: "This ticket will incorporate psf-matched coadds into DRP and include the following:    1) Develop plan for processing Psf-Matched coadds as part of DRP including interface in pipe_tasks commandline tasks, and butler data product naming convention and mapped filesystem paths: https://community.lsst.org/t/who-are-the-stakeholders-for-psf-matched-coadds/1439  2) RFC plan.  3) Add new data products to appropriate mapper files, including getting input on ones with unique file paths like obs_subaru and obs_sdss.  4) Edit command line tasks (currently WarpAndPsfMatch, MakeCoaddTempExp, AssembleCoadd) to treat psf-matched and non-psf-matched coadds as separate entities.  "
Answer: 253662.0

User story: "Because warping changes the dimensions of a PSF, we need the ability to resize the reference PSF when psf-matching WarpedPsfs.  DM-8088 implemented this for two common model Psf models Single and Double Gaussian PSFs. This ticket will extend the self-resizing capability to all PSFs and test. "
Answer: 129672.0

User story: "[Executor|https://github.com/mxk62/Executor]'s role is to create locally an environment allowing it to run a given LSST task and collects data of interest after the task is finished. This process includes creating _a local_ butler repository. However, there is no generic protocol/interface allowing to do that from scratch for different cameras. Thus adding a support for a new data repository requires code extension/refactoring."
Answer: 3347.0

User story: "This is the new (taking over from DM-6168) top level ticket for gathering all pybind11 wrappers. When this ticket is merged into master the port is complete."
Answer: 140977.0

User story: "Fix issues in pybind11 wrapping revealed in {{pipe_tasks}}."
Answer: 90703.0

User story: "fix and update the following LSST catalog search panel issues:     - Catalog polygon search doesn't work (wrong parameters passed)  - Can not switch to catalog search after image search fails on creating the plot.   - shorten the decimal number display on the title of table tab.    "
Answer: 1819.0

User story: "The generated wrappers will live parallel to the Swig wrappers. This ticket only covers the C++ wrappers themselves, not the Python layer on top (which will continue to use the old wrappers) all work will stay on a separate branch and will not be merged to master until DM-6168 is complete.    The tests included in this ticket are:  # {color:#14892c}testRaWrap.py{color}  # {color:#14892c}testCoordptr.py{color}  # {color:#14892c}testChebyshevBoundedField.py{color}  # {color:#14892c}testStatClipException1045.py{color}"
Answer: 2479.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: "PSF estimation deteriorates in crowded fields due to sources in wings of PSF stars. We need to implement a method that can remove those residuals from the PSF wings. This can either be done iteratively (fit PSF; detect; subtract faint sources; re-fit PSF, etc.) or by doing some kind of filtering (e.g. median or other more sophisticated co-add type of method) to combine PSF stars into a final PSF."
Answer: 1793012.0

User story: "Update and resolve confusion about the DM onboarding process:    - Remove instruction to email IT for project credentials, instead indicate that hires should remind T/CAMs to fill out https://project.lsst.org/onboarding/form.  - Link to project onboarding instructions https://confluence.lsstcorp.org/display/IT/Account+Management  - In general, provide more direct instructions to T/CAMs on their role in onboarding, and link to the LSST IT onboarding page from those instructions. (The current instructions are written primarily for new hires rather than managers)."
Answer: 74630.0

User story: "Create the new flexible AST-backed WCS class.    This will be called {{lsst::afw:;geom::SkyWcs}} to indicate that it is a celestial WCS. It will implement most of the methods of the existing {{lsst::afw::image::Wcs}}. It will subclass from {{lsst::afw::geom::Transform<Point2Endpoint, SpherePointEndpoint>}}, because that class already performs the necessary pixel-to-sky transformations. It will include various standard frames to support the LSST pixel convention.    Note that this ticket is purely to create the new WCS class. It is not intended to replace usage of the existing WCS class."
Answer: 221913.0

User story: "Once the new point classes are implemented in DM-1987 this will provide the wrapper on top of astshim to pass them in and get them out both as lists and as single points."
Answer: 149932.0

User story: "Currently this consists of working all the way through and digesting the Every Page is Page One (EPPO) book and taking notes."
Answer: 18892.0

User story: "Wrap any afw tests in {{tests/test.txt}} that are not covered.    This includes:  # testExecutables.py  # -testLeastSquares.py-  # -testTableIO.py-  # -testVisitInfo.py-  # -testWeather.py-"
Answer: 40743.0

User story: "Collate responses from database needs questionnaire."
Answer: 204802.0

User story: "Formulate and send questionnaire to identified project collaborators to assess individual database needs. "
Answer: 55.0

User story: "Discuss database needs with data management architect, database owners, and local experts. Document known project databases. "
Answer: 56.0

User story: "- collect information about SDSS stripe 82 data  - understand the DAX queries  - help others in SUIT team to understand the whole system better  - and all the other things related to PDAC"
Answer: 2951.0

User story: "May not require any wrapping, if so then this ticket is just for tracking. Otherwise, adjust SP."
Answer: 40358.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: "May not require any wrapping, if so then this ticket is just for tracking. Otherwise, adjust SP."
Answer: 29937.0

User story: "May not require any wrapping, if so then this ticket is just for tracking. Otherwise, adjust SP."
Answer: 41774.0

User story: "May not require any wrapping, if so then this ticket is just for tracking. Otherwise, adjust SP."
Answer: 40368.0

User story: "May not require any wrapping, if so then this ticket is just for tracking. Otherwise, adjust SP."
Answer: 44710.0

User story: "Wrap {{meas_base}} with pybind11."
Answer: 72007.0

User story: "Create minimal tool to snapshot Github repos for a given org into S3 (later, to Nebula)."
Answer: 4.0

User story: "The following tasks depend on both {{afw::image}} and {{afw::table}}. Wrap them.    # testApCorrMap.py (enable one skipped test)  # testBox.py (add a test for the copy constructor)  # testExposureTable.py  # testPolygon.py  # testTableIO.py  # testTableUtils.py  # testValidPolygon.py  # testVisitInfo.py  # testWeather.py  "
Answer: 12618.0

User story: "The evaluation of A&L vs. ZOGY in dense fields (DM-8047) was summarized in a [github repository|https://github.com/lsst-dm/diffimTests/blob/master/shootout.md]. This should be migrated to a full DMTN so that it can be communicated to, and reviewed by others."
Answer: 1794351.0

User story: "Pickling of {{afw}} objects is done in several places. This ticket involves wrapping all cases with pybind11.  The following tests have to pass (more may be added over time when encountered):    * {color:#14892c}testPickles.py{color}  * {color:#14892c}testImagePickle.py{color}  * {color:#14892c}testTicket2233.py{color}  * {color:#14892c}testSourceMatch.py{color}  * {color:#14892c}testPolygon.py{color}  * {color:#14892c}testBackground.py{color}    The following tests in {{obs_base}} need to pass:  * {{testOutputRoot.py::OutputRootTestCase::testBackup}} (depends on pickling of {{Point2I}})"
Answer: 34215.0

User story: "SQuaSH uses MySQL/MariaDB for the development and production databases, it is implemented through the Django-MySQL package to add specific features of MySQL/MariaDB to Django. In particular, we are interested in the JSON data type to store the validate_drp outputs. That seems very convenient as these outputs can vary widely and we don’t want to to turn all the details into a relational model. "
Answer: 2960.0

User story: "As part of requirements tracing, go through DPDD, determine where requirements are missing and create new requirements in LSE-61 as required. This will also involve updating some of the existing requirements to match DPDD."
Answer: 1167.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 spent 4 nights observing at the CTIO .9-m telescope.  The site, El Cerro Tololo is next to Cerro Pachon, where the LSST auxiliary telescope will be built.  Besides the usual calibrations frame (bias dark and domeflats), I dedicated the observations to an extensive follow up of two Calspec stars, HD14943 and MuCol, so as to get a fine timeline monitoring of the relative variation of the atmospheric transmission.  The ~700 images will now be reduced to extract the spectra and measure the relative variation of atmospheric absorption as a function of airmass for 4 nights."
Answer: 160824.0

User story: "Update {{post-qa}}'s shim based on the JSON format in {{validate_base}}, as implemented in {{validate_drp}} after the port in DM-7933."
Answer: 2940.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: These are task taken from [~<USER> comments in DM-7321 that need to be done the the firefly library. They are the issues that are exclusively on the Firefly client/server side. I am also including some comments:    * -Putting up an image often generates a small image (zoom=1); a small resize of the window causes a resize.- *(#2)* - _implemented in DM-10948_  * -It'd be nice to have an option for a horizontal layout (cf. ds9) – displays tend to be wider than high, but the firefly (and default ds9) display is higher than wide so you lose image area. *(#3)*-  _implemented in DM-10948_  * In the layers display, one layer seems to be the image. Why does it have a colour and a tickbox? *(#5)* DM-13124  * Pixel coords are off by (0.5, 0.5) – the middle of the bottom left pixel should be (0, 0) (i.e. offset by (1, 1) from the fits standard, which assumes fortran-style 1-indexed arrays) *(#7)* DM-13126  * There doesn't seem to be a way to show coordinates allowing for XY0 *(#8)* _I am not sure what this means, i will need more detail_  (DM-13152)  * The nice inset detail of the image doesn't show the mask planes *(#11)* DM-13127  * The inset detail isn't always centred on the cursor. E.g. at the lower left corner, if you put the cursor on the LL pixel, that pixel is shown at the LL of the inset, not the centre *(#12)* _I am not sure this behavior is wrong, I need to be convinced_ DM-13128    * Colours for masks appear to be case sensitive (unlike at least most web standards), and illegal colours such as RED are silently ignored *(#13)*  DM-13132  * Support a rapid stream of visualization actions, some which come before async actions complete (_from slack discussion_). DM-13131          More notes:  * We have talked about make another type of api html entry point that will allow for grid type layout display. We might do this as part of the QA efforts. _*#2* and *#3* implemented in DM-10948_  * *#4, #9, #10* are probably on the python api side or need to be worked on both sides and need other tickets. I will works this out with [~<USER>, they need separate tickets  * *#6* -  -I don't think this is an issue-, _update_ - will solve *#6* as I documented in the comment below.  *#1, #14* - already fixed as part of DM-7321      More issues:    Fast zooming + restore failed:  How to repeat:  Catalog search Gaia at m81: Got an coverage image.  Image search WISE at m81: The WISE image swapped the Gaia coverage map.  When zoomed in fast and all the way till the zoom option panel shows, clicked Restore before closed the zoom option panel, the image got lost and the error message showed:  "ZoomOptionsPopup.jsx:52 Uncaught TypeError: Cannot read property 'zoomFactor' of null  at getInitialPlotState (ZoomOptionsPopup.jsx:52)  at Array. (ZoomOptionsPopup.jsx:87)  at dispatch (createStore.js:186)  at middleware.js:86  at index.js:85  at index.js:14  at dispatch (applyMiddleware.js:45)  at PlotImageTask.js:178  at Object.dispatch (index.js:11)  at process (ReduxFlux.js:269)  "  
Answer: 560317.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: "Kubernetes might be an interesting alternative to Swarm, this ticket will provide a Kubernetes setup using Openstack in order to evaluate this tool."
Answer: 100671.0

User story: "The details of the Stripe82 PDAC load need to be documented at:  * [https://confluence.lsstcorp.org/display/DM/Loading+catalogs+into+PDAC]"
Answer: 271681.0

User story: h1. The goal    A 20% DR1 dataset is needed at IN2P3 to use as a basis for the F16 KPM measurements.    h2. Additional considerations and requirements:    * The new data set does not have to be scientifically meaningful  * The referential integrity of the dataset between its three tables: Object, Source and ForcedSource is *mandatory*  * It's desired to preserve uniform object density within a spatial area area covered by the present 10% DRP catalog  * the replication procedure to be developed in a course of this effort has to be scalable to allow producing much large data sets in the future (30%, 40%, etc. of DRP1)  * investigate options to increase the dataset in either or a combination of three dimentions:  ** the spatial coverage  ** the density  ** the temporal depth  * the procedure has to be explained and documented to be repeated (for larger data sets) in the future  ** NOTE: use the this ticket as a raw document for the effort. Consider producing a refined documentation in a form of a DM Technical Note (DMTN).    h2. Background info and references    LSST Key Numbers:  * [https://www.lsst.org/scientists/keynumbers]    Some basic info (including numbers and hardware) for the 10% scale test in Summer 2015:  * [https://confluence.lsstcorp.org/display/DM/S15+Large+Scale+Tests]    The JIRA ticket for: "Summary 2015 Large Scale test planning (10% fraction of the LSST DRP1)":  * [https://jira.lsstcorp.org/browse/DM-2189]    A package with scripts, configurations used during the preparation of the original (KPM 10%) dataset:  * [https://github.com/lsst-dm/db_tests_summer15]    Partitioner-Duplicator Tools:  * [https://github.com/lsst/partition/blob/master/doc/duplication.md]    Ganglia Monitoring of the *Qserv* cluster at *IN2P3*:  * [http://ccqservmon.in2p3.fr:443/?c=Qserv&m=load_one&r=hour&s=by%20name&hc=4&mc=2]    A package with new tools and procedures and various configuration files prepared for the new (KPM 20%) dataset:  * [https://github.com/lsst-dm/db_tests_kpm20]  
Answer: 103683.0

User story: "There any now many, many package updates that it would be nice to have as part of the base image rather than having to run manual updates."
Answer: 837980.0

User story: "Package name is now linked to the corresponding git commit and a Date column was added to the Code Changes table.      Current master is running here:  https://angelo-squash-squash.lsst.codes/dashboard"
Answer: 1185.0

User story: "Review  and give feedback of the draft SUIT requirement document. "
Answer: 1.0

User story: "Summary of our first discussion with Gregory and K-T which covered few simplest use cases."
Answer: 8875.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: "Attend the HSC data processing preparation meeting across multiple institutes to sync up on middleware topics, as decided in a previous [Current-Infrastructure Meeting|https://confluence.lsstcorp.org/display/DM/Current-Infrastructure+Meeting+2016-11-10],   The meeting will happen after the replan, likely in January."
Answer: 129572.0

User story: "Learn to run the prototype Pegasus workflow developed in DM-8339 on Verification Cluster."
Answer: 33039.0

User story: "Learn to run basic Pegasus examples on Verification Cluster    Use DM-8156 to properly allocate nodes and run jobs on the worker nodes.  "
Answer: 31935.0

User story: "pipe_tasks provides {{examples/calibTask.py}}, which exercises {{CharacterizeImageTask}} and {{CalibrateTask}}.    As [reported by Mandeep Gill|https://community.lsst.org/t/problem-running-calibtask-py-example-script-from-pipe-tasks-dir-examples/1426] this currently fails as follows:    {code}  RuntimeError: No such FITS catalog file: /tigress/HSC/LSST/stack_20160915/Linux64/obs_test/12.1-9-g3e397f1+2/data/input/schema/icSrc.fits  {code}    In addition to that, the code also attempts to pass a {{VisitInfo}} to an {{ExposureF}} constructor, which fails."
Answer: 17079.0

User story: "Discuss with relevant parties regarding AST adoption by LSST pipeline. Make a list of possible solutions for Firefly.    Read:    RFC-193: Adopt AST for WCS and transforms    [http://dmtn-010.lsst.io/]:  WCS and Distortion Requirements and Existing Options    Follow DM-3874:  Produce a design for the new Wcs classes    Two more epics related to AST:    DM-3875: Implement new Wcs classes    DM-6164: Implement the API replacing XYTransform"
Answer: 930418.0

User story: "Codekit currently requires Python 2.  We should fix this."
Answer: 39093.0

User story: "write the draft requirement for Level 3, and its relationship with data space and JupyterHub. "
Answer: 566258.0

User story: "Write the draft version of  narrative description of Level3 ConOps "
Answer: 753419.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: "tasks to finish the deployment:  - setup a LSST SUIT repo, it is the application PDAC  - logo and necessary background images change  - work with SLAC team to add very basic monitoring into the nagios monitor SLAC setup for DAX    We can use the logos and background image from here: https://lsst-web.ncsa.illinois.edu/schema/includes/images/lsst_long_banner1.jpg, https://www.lsst.org/sites/default/files/logo_1.png    More Notes:  * Don't use the banner, use the logo where we have the firefly fogo  * We need build and deploy using the new repo  * app name should be 'suit'      XW  copied from github commit information 12/21/2016  * setup LSST/suit repo  * added lsst logo onto the banner  * make sure build scripts are fully functional  * minor code refactoring  setup:  git clone https://github.com/lsst/suit  ensure both repos (firefly and suit) are in branch 'DM-8385_pdac_v1'    Things to test:    * able to build and deploy suit     gradle :suit:buildAndDeploy  * ensure dev mode works. webpack should monitor firefly's source code as well as suit.     gradle :suit:dev  * verify that LSST logo is used and that suit application is working as expected. This require vpn into ncsa."
Answer: 41933.0

User story: "There have been several recent incidents where the jenkins master proceses unexpectedly exited.  This may be due to plugin / core conflicts or stale configuration.  All plugins and plugin related configuration should be updated with the goal of resolving all warnings in the jenkins master log."
Answer: 60709.0

User story: "DM has completed its migration away from hipchat and the jenkins {{job-dsl}} interface used for hipchat notifications has been log deprecated."
Answer: 118195.0

User story: "There have been several recent incidents where the jenkins master proceses unexpectedly exited.  This may be due to plugin / core conflicts or stale configuration.  All plugins and plugin related configuration should be updated with the goal of resolving all warnings in the jenkins master log."
Answer: 625005.0

User story: "The {{pipeline}} directory in {{lsst-sqre/jenkins-dm-jobs}} should be reorganized to better reflect the containing folders / job names."
Answer: 292640.0

User story: "Similar to DM-8378, jenkins swarm client processes should be automatically restarted if they exit.  It should be straight forward to accomplish this on {{el7}} by converting the sysv init script to a proper systemd service unit.  This has not been a frequent issue, so we may continue to punt on {{el6}} where systemd is not available."
Answer: 60718.0

User story: "There have been at least 3 instances in the last ~month where the production jenkins master instance has exiting without any output in the log.  While this problem needs to be resolved, it can be largely mitigated by having a monitor restart the master process.  It should be fairly simple to accomplish this by converting the existing sysv init script into a proper systemd service unit."
Answer: 60720.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: "mariadb and mariadbclient eups package contains 330 GB of tests binaries/data. This should be removed to have a lighter stack. A mariadb package with test could be added in order to test mariadb install (or this could be performed at build time...).    {code}  qserv@worker3:/qserv/stack/Linux64/mariadb/10.1.18-1-g0e935dc$ du -skh *  20K     COPYING  28K     COPYING.LESSER  88K     COPYING.thirdparty  4.0K    CREDITS  12K     EXCEPTIONS-CLIENT  12K     INSTALL-BINARY  4.0K    README  20K     README-wsrep  285M    bin  12K     data  4.7M    include  66M     lib  712K    man  327M    mysql-test  24K     scripts  3.0M    share  2.8M    sql-bench  {code}"
Answer: 20824.0

User story: "{{AstromFit::Minimize}} has a {{while (true)}} loop and it's not clear that the loop will always exit. We should try to specify a clear ending condition (say, limit it to 100 steps), or show that it will always finish after a reasonable number of steps."
Answer: 1062731.0

User story: "Using SQuaSH after the last deployment DM-8195 two improvements were suggested by users. One is to include the Date in the code change table, so that it becomes evident when a given package changed. The other improvrment fixes the git url linking the package name right to the git commit of the respective change."
Answer: 1275.0

User story: "User needs to have a line chart, connecting the dots together    https://github.com/Caltech-IPAC/firefly/pull/273"
Answer: 91920.0

User story: "With the implementation of RFC-203, {{pex_logging}} is no longer used within {{pipe_tasks}}.  Please check if there are project-supported codes that still use pex_logging and need to be ported, update documentations if necessary, and formally deprecate {{pex_logging}}. "
Answer: 1413118.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: To Search: goto LSST panel, choose the Deep Source catalog, choose the polygon search method and input {{9.4 -1.2, 9.6 -1.2, 9.4 -1.0}}    * When you reload the pdac there is an error  * When I load a table the working icon shows on the table UI until I make it page.  * For catalogs the xyplots and overlays are not coming up.  * On the client log:  {code}  Error: edu.caltech.ipac.firefly.server.query.DataAccessException: DataAccessException:Unexpected error from:unknown  {code}  * On the server log:  {code}     Error while processing request:id=StatisticsProcessor&RequestClass=ServerRequest&searchRequest={"startIdx":0,"pageSize":1000000,"use":"lsst_catalog_overlay","SearchMethod":"Polygon","id":"LSSTCataLogSearch","META_INFO":{"title":"Lsst-RunDeepSource (Polygon)"},"table_name":"RunDeepSource","meta_table":"RunDeepSource","polygon":"9.4 -1.2, 9.6 -1.2, 9.4 -1.1\n","constraints":"","RequestClass":"ServerRequest"}&tbl_id=tbl_id-4&pageSize=1000&META_INFO=tbl_id=tbl_id-4&title=Statistics for tbl_id-1  java.lang.RuntimeException: Data row must start with a space.   at edu.caltech.ipac.util.IpacTableUtil.parseRow(IpacTableUtil.java:289)   at edu.caltech.ipac.util.IpacTableUtil.parseRow(IpacTableUtil.java:213)   at edu.caltech.ipac.util.IpacTableUtil.parseRow(IpacTableUtil.java:209)   at edu.caltech.ipac.firefly.server.util.ipactable.IpacTableParser.getData(IpacTableParser.java:97)   at edu.caltech.ipac.firefly.server.query.IpacTablePartProcessor.getData(IpacTablePartProcessor.java:239)   at edu.caltech.ipac.firefly.server.query.IpacTablePartProcessor.getData(IpacTablePartProcessor.java:72)  {code}    * Also, make sure firefly can load the fits table from here: http://irsa.ipac.caltech.edu/data/Planck/release_2/all-sky-maps/previews/LFI_SkyMap_044-24_1024_R2.01_full/index.html
Answer: 10528.0

User story: At the bottom of DM-5433, [~<USER> writes:    {quote}  Can you update the "SKIP_DEMO" text to say  "Do not run the continuous integration or demo after all packages have completed building."  instead of  "Do not run the demo after all packages have completed building."  {quote}    We've just wasted time figuring out how to avoid building lsst_ci, so I repeat this request.
Answer: 223.0

User story: "Remove {{pex_logging}} dependency in {{ctrl_pool}}. "
Answer: 33939.0

User story: "Switch from using {{pex_logging}} to {{log}} in {{meas_mosaic}}. "
Answer: 42255.0

User story: "Switch from using {{pex_logging}} to {{log}} in {{meas_modelfit}}. "
Answer: 29310.0

User story: "Switch from using {{pex_logging}} to {{log}} in {{ci_hsc}}. "
Answer: 42258.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: E.g. when running ip_isr's {{examples/runAssembleTask.py}}:    {code}  Traceback (most recent call last):    File "runAssembleTask.py", line 36, in <module>      runAssembler()    File "runAssembleTask.py", line 21, in runAssembler      assembledExposure = assembleTask.assembleCcd(assemblyInput)    File "/scratch/<USER>ip_isr/python/lsst/ip/isr/assembleCcdTask.py", line 200, in assembleCcd      ccd = next(assembleInput.values()).getDetector()  TypeError: list object is not an iterator  {code}    Looks like a bad conversion to Python 3: it assumes that {{dict.values()}} returns an iterator, but in Python 2 it returns a list. Simple (but ugly) fix:    {code}  --- a/python/lsst/ip/isr/assembleCcdTask.py  +++ b/python/lsst/ip/isr/assembleCcdTask.py  @@ -197,7 +197,7 @@ class AssembleCcdTask(pipeBase.Task):           ccd = None           if hasattr(assembleInput, "has_key"):               # Get a detector object for this set of amps  -            ccd = next(assembleInput.values()).getDetector()  +            ccd = next(iter(assembleInput.values())).getDetector()               # Sent a dictionary of input exposures, assume one amp per key keyed on amp name                 def getNextExposure(amp):  {code}    Better suggestions welcome.    Rather shocking that this wasn't caught by tests. Sufficiently shocking that I'm wondering if I missed something. I suggest that rather than just committing the above tweak, this ticket should include a test which demonstrates that the task actually runs. An easy way to do that might be to simply migrate a slightly modified version of the code from {{examples/}} to {{tests/}}.
Answer: 115386.0

User story: "Request by Q-serv team for automated CI-driven container builds for qserv development  "
Answer: 13193.0

User story: "DM External libraries need to follow EUPS best practice so EUPS sees them as TaP repositories. This change is required because the new version of conda-build (2.x) creates a {{conda_build.sh}} file in the root directory of the repository.    This was worked around by using an older version of conda-build but the right way to fix it is to update all repositories with changes so that EUPS sees them as TaP repositories.    In each DM External repository I will create a {{./.tap_package}} and insert TAP_PACKAGE=1 to the {{ups/eupspkg.cfg.sh}}."
Answer: 829181.0

User story: "The first draft has been reviewed and put in docushare.   It needs to go through another round of review and revision, approved by TCT, and put under document control. "
Answer: 277754.0

User story: "Piff uses GalSim as it's PSF image generation back-end.  Out-of-the box, GalSim is quite a bit slower than donutlib at generating images, but it would be really nice to keep GalSim's flexibility compared to donutlib.  This issue is to implement some ideas found during DM-7959 to speed up GalSim OpticalPSF, mostly by adjusting the sizes of the FFTs needed to convert between pupil plane, image plane and Fourier plane."
Answer: 190.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: pull.sh is failing with a no route to host error.  {code}  (venv)/afs/in2p3.fr/home/j/<USER>working/qserv/admin/tools/docker/deployment/in2p3(0)>./pull.sh  bash: /afs/in2p3.fr/home/j/<USER>.bashrc: Permission denied  Pulling repository docker.io/qserv/qserv  Error while pulling image: Get https://index.docker.io/v1/repositories/qserv/qserv/images: dial tcp 52.207.178.113:443: getsockopt: no route to host  {code}    env.sh  {code}  # Rename this file to env.sh and edit configuration parameters  # env.sh is sourced by other scripts from the directory    # shmux path  PATH=$PATH:/opt/shmux/bin/    # Image names  # ===========    # Used to set images names, can be:  #   1. a git ticket branch but with _ instead of /  #   2. a git tag  # example: tickets_DM-5402  #BRANCH=dev  BRANCH=tickets_DM-7109    # `docker run` settings  # =====================    # Data directory location on docker host, optional  HOST_DATA_DIR=/qserv/data    # Log directory location on docker host, optional  HOST_LOG_DIR=/qserv/log    # ulimit memory lock setting, in bytes, optional  ULIMIT_MEMLOCK=10737418240    # Nodes names  # ===========    # Format for all node names  HOSTNAME_FORMAT="ccqserv%g.in2p3.fr"    # Master id  MASTER_ID=100    # Workers range  WORKER_FIRST_ID=101  WORKER_LAST_ID=124    # Master id  # MASTER_ID=125    # Workers range  # WORKER_FIRST_ID=126  # WORKER_LAST_ID=149    # Advanced configuration  # ======================    DIR=$(cd "$(dirname "$0")"; pwd -P)  . "${DIR}/common.sh"    {code}
Answer: 254775.0

User story: "If we choose Kubernetes to manage the clusters and container microservices, we can then manage Jupyterhub as well. This story might be pushed for next cycle"
Answer: 221806.0

User story: "Default is start with Cinder:NFS but then moved to GPFS"
Answer: 221811.0

User story: "Update codekit to use current github3    https://jira.lsstcorp.org/browse/DM-8340"
Answer: 1404.0

User story: "Follow the pipeline steps in {{ci_hsc}} to make an abstract workflow in Pegasus in a shared-many-thing scheme using existing task/butler interface. In this ticket, ignore orchestration details, and executor will not be used.     "
Answer: 23255.0

User story: "It appears that {{lsst/versiondb}} updates are no long being pushed.  Presumably, this is due to the {{lsst-dev -> lsst-dev-old}} rename that occurred last week."
Answer: 29.0

User story: "The jenkins {{build-publish-tag}} job failed last night due to a known logic error that was noticed and already fixed in DM-7807 (currently, still unmerged).  The fix simply needs to be cherry-picked and merged to master."
Answer: 29.0

User story: "qserv/qserv:dev image is based on qserv/qserv:latest and may become huge if former one isn't update on a regular basis.    This ticket will allow to create qserv/qserv:dev from scratch to reduce its size."
Answer: 35748.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 flatfielding step is implemented in the pipeline. This correspond to :  (raw_image - masterdark)/ synthetic_flat    The synthetic flat is built out of a set monochromatic flatfields combined so as to :  - Build a map of pixel defects as a function of wavelength.  - Determined the pixel by pixel response as a function of wavelength.    "
Answer: 290252.0

User story: "The image search should be different from the catalog search.  Currently, both image search and catalog search are used the same method and same parameters.  We now need to separate the catalog and image search.  For image search, there is no search method involved.  Instead it has other parameters to handle.   It may have search type, and the parameters for each type.  It may have LSST filter etc.  "
Answer: 16902.0

User story: "A basic terraform deployment that setups a VPC, ACLs, an EIP, and route53 entries for {{status.lsst.codes}}."
Answer: 17550.0

User story: "Parse the output of keeper.lsst.codes/products in order to retrieve a list of published products, and monitor the health of those endpoints."
Answer: 76688.0

User story: "Write an attractive wrapper around the JSON that the monitoring solution provides."
Answer: 200496.0

User story: "Minimal viable monitoring solution to give us up/down status and notification for major services.    * Lives at status.lsst.codes  * Provides front-end unauthenticated liveness status  * Provides authenticated interface to monitoring system to acknowledge service status changes  * Sends notifications when service status changes"
Answer: 94.0

User story: "Currently, the code dealing with calculating the phase is in 2 places, one in the client (DM-8006) for the slider feature and one in the server (as a search processor).    If we want to keep the server side, we need at some point to get the same calculating phase that runs from 0 to 2 instead of 0 to 1.    12/8/2016:  The conclusion is to only have the phase folding algorithm in the client side.  "
Answer: 30016.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 change of hardware for lsst-dev has broken the {{run-rebuild}} and {{run-publish}} jobs. See: https://community.lsst.org/t/official-release-of-lsst-dev01-and-replacement-of-lsst-dev/1386    There seems to be sort of odd problem with git checkouts:    {code:java}    ERROR: Error fetching remote repo 'origin'  hudson.plugins.git.GitException: Failed to fetch from https://github.com/lsst-sqre/buildbot-scripts.git   at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:797)   at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1051)   at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1082)   at org.jenkinsci.plugins.multiplescms.MultiSCM.checkout(MultiSCM.java:143)   at hudson.scm.SCM.checkout(SCM.java:495)   at hudson.model.AbstractProject.checkout(AbstractProject.java:1269)   at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604)   at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)   at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529)   at hudson.model.Run.execute(Run.java:1741)   at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)   at hudson.model.ResourceController.execute(ResourceController.java:98)   at hudson.model.Executor.run(Executor.java:410)  Caused by: hudson.plugins.git.GitException: Command "git fetch --tags --progress https://github.com/lsst-sqre/buildbot-scripts.git +refs/heads/*:refs/remotes/origin/* --depth=1" returned status code 128:  stdout:   stderr: fatal: git fetch-pack: expected shallow list  fatal: The remote end hung up unexpectedly  {code}  
Answer: 1326.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: Get latest FF version from 'dev' and migrate/add WCS target search feature in IRSAViewer so MOST can make use of it.    The plan for release the IRAViewer with this feature is by January, so it need to be added by end of December and ready for testing (together with histogram, see DM-8309)    MOST generated HTML page that make use of FF API and have a function that is used to call the viewer externally on each row (column added to the file attached):    {code:html}  <a href='javascript:mostPlot("http://irsa.ipac.caltech.edu/ibe/data/wise/merge/merge_p1bm_frm/5b/49025b/143/49025b143-w1-int-1b.fits",330.347003, -2.774482)'><img src="/images/fftools-logo.png" border="0" align="bottom" alt="View"></a>  {code}    where {{mostPlot}} function is:    {code:javascript}  <script type="text/javascript"> {       function mostPlot(url, ra, dec) {                      var pos = ra + ";" + dec + ";EQ_J2000"          var params = { "Type"  : "URL",                               "URL"      : url,           "OverlayPosition"    : pos }             firefly.getExternalViewer().plot(params)       }       onFireflyLoaded= function() {           firefly.debug= true;           var external= firefly.getExternalViewer();           external.setDefaultParams({               "TitleOptions" : "FILE_NAME",               "ColorTable"   : "1",               "TitleFilenameModePfx" : "most",               "OverlayPosition"    :  "\ra\;\dec\;EQ_J2000",               "RangeValues"  : firefly.serializeRangeValues("Sigma",-2,10,"Linear")       }) ;       external.setTarget("_mostWin");   } } </script>  {code}
Answer: 41730.0

User story: "The story is about to branch off 'dev' a version of IRSAViewer to have the latest version of Firefly and enable:    - histogram feature (simple UI, no binning method options, only column/expression input)    Test version should be ready by beginning January.     Release plan for end of January.      "
Answer: 116456.0

User story: "update the LSST search panel to work on   - catalog table and image table selection  - spatial search for either catalog or image search  - fix DD table operation bugs including     . constraint column entry is not focused  - Update status store for LSST search panel - store the status for each catalog.      "
Answer: 17159.0

User story: "Create Mac OS X and Linux Conda binaries for 0.13.0 (v13.0) release."
Answer: 202803.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: "Need to follow https://github.com/lsst/qserv/blob/master/UserManual.md#spatial-constraints-should-be-expressed-through-our-qserv_areaspec_-functions  to use the qserv functions, like     qserv_areaspec_box(      lonMin               DOUBLE PRECISION,  # [deg]    Minimum longitude angle      latMin               DOUBLE PRECISION,  # [deg]    Minimum latitude angle      lonMax               DOUBLE PRECISION,  # [deg]    Maximum longitude angle      latMax               DOUBLE PRECISION   # [deg]    Maximum latitude angle  )    qserv_areaspec_circle(      lon                  DOUBLE PRECISION,  # [deg]    Circle center longitude      lat                  DOUBLE PRECISION,  # [deg]    Circle center latitude      radius               DOUBLE PRECISION   # [deg]    Circle radius  )    qserv_areaspec_ellipse(      lon                  DOUBLE PRECISION,  # [deg]    Ellipse center longitude      lat                  DOUBLE PRECISION,  # [deg]    Ellipse center latitude      semiMajorAxisAngle   DOUBLE PRECISION,  # [arcsec] Semi-major axis length      semiMinorAxisAngle   DOUBLE PRECISION,  # [arcsec] Semi-minor axis length      positionAngle        DOUBLE PRECISION   # [deg]    Ellipse position angle, east of north  )    qserv_areaspec_poly(      v1Lon                DOUBLE PRECISION,  # [deg]    Longitude angle of first polygon vertex      v1Lat                DOUBLE PRECISION,  # [deg]    Latitude angle of first polygon vertex      v2Lon                DOUBLE PRECISION,  # [deg]    Longitude angle of second polygon vertex      v2Lat                DOUBLE PRECISION,  # [deg]    Latitude angle of second polygon vertex   ...  )    See more examples in https://confluence.lsstcorp.org/display/DM/PDAC+sample+queries+and+test+cases    "
Answer: 8178.0

User story: "An examples subdirectory can be added to the firefly_client repository at the top level. It can contain sample Jupyter notebooks. The starting point can be notebooks for the Python API from the firefly repository, where the API was first developed."
Answer: 250109.0

User story: "To support the afwDisplay backend for Firefly, firefly_client is being added to the stack as a third-party package. To more easily incorporate changes as firefly_client is developed, firefly_client has been forked to the LSST Github org from the Caltech-IPAC org. A branch will be created and the eups tables will be added to it."
Answer: 38926.0

User story: "Following the developer instructions for third-party packages, add the {{ws4py}} package as a third-party package that is installable by eups."
Answer: 37518.0

User story: "Usuless data, backup, and docker images should be removed."
Answer: 228253.0

User story: "Fix travis PR build are broken for unknown reason since a few month"
Answer: 30193.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 reading RHL's [hard|https://github.com/lsst-dm/calibration/blob/master/calibration.pdf] and [easy(er)|https://github.com/lsst-dm/calibration/blob/master/calibrationPipelines.pdf] calibration documents, and in conjunction with his [IPython notebook|https://github.com/RobertLuptonTheGood/notebooks/blob/master/calibration%20figures.ipynb], become intimately familiar with the mechanism by which photometric flats will be produced from regular flat-field screen images using CBP spot illuminations.    Familiarity will be used to write and give a talk at PACCD-2016 on using Collimated Beam Projectors to improve photometric accuracy in the LSST survey."
Answer: 27573.0

User story: "Imgserv needs to be able to retrieve images from different data repositories (stripe82, WISE, LSST) different releases within these repositories.     Some details of the REST interface deemed insuficient to support this requirement, for historical reference, are here: https://confluence.lsstcorp.org/display/DM/API.    The gaps are to be filled by the use of JSON schemas, guided closely by relevant IVOA standards & recommendations, to represent ImageServ API v1 interface, and a new internal execution engine that can interpret and translate image requests written in the new language.  Desired XML input & output format, per IVOA standards, are being translated from/to JSON on the fly by ImageServ.  "
Answer: 470883.0

User story: "Will make initial pages in reST for all Tasks in a consistent style, beginning with at least a descriptive format (using the current doxygen pages, and parsing the code itself), but keeping in mind that we'll want to fill in the 'how to use' section later by carefully running each example code (which have been created for most of the Tasks), and leaving a placeholder for this."
Answer: 19070.0

User story: "Production workflow system wants to know the estimates of the resources used by pipeline tasks for a particular set of input data, this is to be able to select best site that matches the requirements. We need some support from SuperTask side for that which is relatively simple, does not require a lot of effort from task author, and flexible."
Answer: 20468.0

User story: Updating development server documentation (lsstdev01 + Verification cluster, legacy lsst-dev-old) for the event of the "release" of lsst-dev01 as lsst-dev, 'downgrade' of current lsst-dev to lsst-dev-old. 
Answer: 20823.0

User story: "Take account of muon tracks' angle of incidence on the sensor. This will improve spectral resolution."
Answer: 178615.0

User story: "Fit the spectra presented in DM-6030 (or some variation thereof) with Landau-Gauss convolutions."
Answer: 178625.0

User story: "This requires new hardware, which has been ordered; delivery expected in December 2016."
Answer: 90522.0

User story: "Update Ansible role repositories, test, publish to Ansible Galaxy, recreate images using {{packer-panopticon}}."
Answer: 21974.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: "There is a new version of Riemann. Upgrade our ansible role to use it.    https://github.com/riemann/riemann/blob/master/CHANGES.markdown#version-0211    The fluentd package should use Xenial (16.04) now instead of Trusty (14.04)."
Answer: 22149.0

User story: "DM-8126 made a simple Pegasus workflow to do processCcd and makeDiscreteSkyMap with some {{obs_test}} data. Make the equivalent based on some HSC data from {{ci_hsc}}.  "
Answer: 18575.0

User story: "{{daf_ingest}} is currently failing tests because it assumes that the log object from tasks supports {{logdebug}}. The package assumes {{pex_logging}} and needs to be ported to understand {{log}}."
Answer: 84910.0

User story: SimpleMapper in the pipe_base mocks expects metadata queries to supply a "level" parameter, even though this was removed from the Butler in DM-4683. This manifests as an incorrect number of parameters passed to {{queryClosure()}} (simpleMapper.py:215), and should also require a fixup in {{RawMapping.query()}}.
Answer: 1806333.0

User story: "daf_ingest requires some minor changes to get it working on Python 3."
Answer: 1806204.0

User story: "Learn how to wrap code using pybind11 and wrap afw::table tests not wrapped in DM-7056. These tests are    # testTableAliases.py  # testTicket2026.py  # testTicket2707.py  # testMatchFits.py  # testSourceMatch.py # except a pickle segfault to be fixed in DM-8415  # testAmpInfoTable.py  # testAstropyTableViews.py  "
Answer: 24414.0

User story: "{{datarel}} is a deprecated package but is still there as a root for the documentation system. It optionally depends on scisql and that is the only package blocking Python 3 for lsst_distrib. I propose we remove the optional dependency and allow lsst_distrib to work with Python 3."
Answer: 54821.0

User story: "This is the ticket for the v13.0 release prep.     List other tickets as blockers if you're not ready.     Community post with current status: https://community.lsst.org/t/fall-2016-release-status-and-discussion/1398"
Answer: 190149.0

User story: "Gather partial COSMOS dataset including 291 public DECam raw data files from Feb 2013. Process them on Verification Cluster using pipe_drivers tasks as exercises. "
Answer: 14356.0

User story: "An algorithm to perform the first task of the processing is implemented :  The CTIO .9-m imager is a one CCD camera read by 4 amplifiers.  Each one of the 4 segments are bias subtracted and assembled to produce one continuous image.    A python class selects the relevant informations from the fits header. It can recognize between the two imagers of the telescope. "
Answer: 1810699.0

User story: "Following on from RFC-251 we need to create a new package called {{lsst_obs}} and add all the obs packages to it. This package should then be added to {{lsst_distrib}}. The {{lsst_obs}} package should be documented to allow broken packages to be removed if they are holding up a release if they are not officially supported by DM."
Answer: 56830.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: "CmdLineTask gets confused when it's given a rerun folder that already exists but is empty, and resulting in this error message:   {code:java}  Error: input directory specified by --rerun must have the same mapper as INPUT  {code}    This happens in use cases similar to what's wanted in RFC-249: a user creates a symlink for a rerun before running the task. "
Answer: 29009.0

User story: "Butler needs to allow repositories to contain a mix of compressed files (that end in .gz) and not compressed files, where the policy template does not specify the compressed file extension (gz)"
Answer: 226.0

User story: Two tables are added in the LSSTCatalog's UI.  Thus, the search processors in the server side need to be updated to reflect the changes in the UI.      The following work will be done:  * Find out the ra and dec columns based on the table name passed from the UI  * Process the constraints passed from the UI and add to the SQL's "where" clause  * Re-arrange the codes   * Test all four tables to make sure they work for each of the search method except mutli-object.  * Add error handling when the search method is not supported  * Add error handling when the data type defined in the metadata of the DAX's JSON file is not the same as in the actual datatype in the same JSON file.   
Answer: 11170.0