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: "There are several sections with inaccurate information about the North American portion of the LHN and the implementation of the networking into NCSA as well as the base site commissioning cluster architecture."
Answer: 220164.0

User story: "With Steve and James distill the actual data movement requirements, the mechanism to broker those transfers and the network technology to ensure the real-time transfer of images"
Answer: 653334.0

User story: "To prototype the layer 2 circuit LSST will eventually have."
Answer: 54573.0

User story: for "something else" there are 2 major options: pex_config (dislike because the 'data' gets executed), and yaml (very well supported, is just data). 3rd option: we could use the sqlite registry, and define a schema for that.     (sqlite benefits: has support for write locks that will be necessary very soon. Except, need write-once-compare-same mechanism; so we'll need that 1. for normal files and 2. across n nodes. so maybe there's no benefit).    also, while we're there:  as noted in DM-4170, registries.py needs to not use astropy and instead should use pyfits. If it's quick, that change should be made here (or turned into a separate ticket)
Answer: 75022.0

User story: We want to be able to keep the .paf file in the repository, with the data for which it provides configuration information.    At least for the time being it needs to be optional; it looks first in the repository and second in the "old" location for the paf.    In the case of a repository chain, the child should 'win'.
Answer: 26086.0

User story: "As part of the GWT conversion to pure JavaScript, we've came up with a new design based on redux and react.  This task is to create all of the major components of the framework with minimal functionalities.  This will allow other developers to build upon this foundation core."
Answer: 1.0

User story: We just came across a problem with configuration on the HSC side (https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1342).    There is an algorithm, {{flags.pixel}}, to set flags based on bits set in the Mask.  I just added an option to set a new bitplane (by default "BRIGHT_OBJECT"), and when it's enabled you would also like to add flags such as {{flags.pixel.bright.object.any}} (the fact that the _ in the name becomes . is a different topic).    However, this appears to be impossible.  By the time the config parameter is parsed we've finished creating the measurement task, and its config is frozen so I cannot add the extra bits.  The workaround is to add it in a task override file (in this case in obs_subaru) but this is unsatisfactory as it's not just in a different file but a different package.
Answer: 2283242.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 assembleCoadd.py task has a configuration option doSigmaClip which chooses between MEAN and MEANCLIP. Please replace this with an option to specify the algorithm to be used. Note that afwMath.stringToStatisticsProperty can be used to convert a string to an enum value. In particular, this would allow me to specify a MEDIAN stack if desired (e.g. to make pretty RGB images)  "
Answer: 945514.0

User story: "The technical report from DM-4155 and DM-4156 should have as its conclusion a recommendation for what Wcs system the LSST stack should adopt (either our own implementation, a third-party library, or some combination thereof). Beyond the conclusion section of that report, this will be provided as an RFC that includes:     * executive summary   * mock API   * links to the relevant documentation (beyond just the above technical report)   * a bullet list of the rationale for this decision    The conclusion of this RFC represents the end of this Epic."
Answer: 311063.0

User story: "As part of the requirements document in DM-4155, we need a report-likely section(s) of that same document-on the currently available Wcs libraries (including, but not limited to AST Starlink and astropy.Coordinates) and summaries and references from the current literature about how other surveys and projects have managed their Wcs.    For each of the currently existing options, the report should include at a minimum:   * implementation language.   * API and languages that can interface to that API.   * how well supported (including number of contributors) is the project and how active is ongoing development.   * its performance and optimization for both scalar and vector calculations, and its scalability to large data sets.    We also need to look for and/or request technical reports and other literature from existing and completed surveys, including DES (<USER>, Pan-STARRS (<USER>, STScI (Erik Tollerud), and SDSS (Lupton and/or Blanton?)."
Answer: 232971.0

User story: "Based on the information compiled from DM-4153 and DM-4152, prepare a requirements document (LaTeX, with references) describing all of the known Wcs requirements for the various portions of the LSST stack. This document could live in afw or in its own repository, and could potentially become a published technical report/conference proceeding."
Answer: 280962.0

User story: For any given column or columns (expression of columns such as col1+log(col2) ) of a IpacTable data, the variable bin histogram is needed.  The variable bin is based on "Bayesian Blocks" algorithm (http://jakevdp.github.io/blog/2012/09/12/dynamic-programming-in-python/).  The output is a new IpacTable (DataGroup) with three columns, numPoints, binMin and binMax.
Answer: 21316.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: "File an RFD requesting information about current and possible future use cases for a Wcs system in the stack. This should get feedback from, at minimum, the alerts pipeline, DRP, and Level III data producers. It should also get feedback from our resident wcs experts.    Whether those use cases are currently implemented in our code, or could be generalized from it, isn't important to this RFD as this information will feed into a subsequent requirements document and RFC about what needs to be written/changed.    Some use cases/buzzwords that will likely be included:   * Efficient x,y -> x',y'   * Stacking a sequence of transformations efficiently   * easy extensibility   * should color terms be included in the Wcs or dealt with elsewhere?   * pixel distortion effects (e.g. tree rings, edge roll off)   * Simultaneous Astrometry (i.e. from image stacks)"
Answer: 203444.0

User story: "The information from DM-4151 should become a brief report on the kinds of usage of Wcs in the stack. This could be posted to Community or Confluence, or it could be a brief LaTeX document attached to the afw repo.    Included in this report should be whether each current usage requires C++, or whether it could be done with e.g. vectors returned from python."
Answer: 203465.0

User story: "Search through the stack for all the uses of our Wcs implementation (Wcs, TanWcs, makeWcs, and any other hidden objects) and make a list of all of those uses (on Community for example). This list should note whether the usage is in C++ or python."
Answer: 128374.0

User story: "Component breakdown and explanation of components as part of FY16 purchases in order to plan optimal purchasing through vehicles available to NCSA."
Answer: 1.0

User story: Yesterday AndyH expressed a valid concern that qserv prints too much info which makes it hard to find errors. By default scons prints whole command line for C++ compilation and linking which are quite long (~half screen depending on your screen size). Most of the time we don't need to see that, so it would be better to replace that with shorter messages like "Compiling Something.cxx" and have an option to print full command with --verbose option.
Answer: 8916.0

User story: "Demonstrate use of breathe for utilizing the existing Doxygen API documentation in the new Sphinx-based doc platform."
Answer: 7254.0

User story: "We need XML output from Doxygen in order to import existing API documentation into Sphinx. In this story I find out how to achieve this within the stack build system."
Answer: 2301.0

User story: "description from DM-3591: Read information (in particular the observation time and length) out of an input dataset's file representation in order to provide rendezvous with calibration data in another repository (that does have a registry). Today, that read is handled by genInputRegistry.py so that the butler doesn't need to look into the dataset itself. If there's no registry, such a read will be necessary."
Answer: 1385.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: "Current implementation of JSON-packed keys in CSS has one complication - the name of the container for packed keys is the same as the key itself (plus .json suffix). This complicates handling of the subkeys because these keys need to be filtered out and these names are all different. It would be better to have easily identifiable packed key names."
Answer: 30459.0

User story: "The values of DECam gain, read noise, and saturation value need to be updated.     This ticket is to update them in the Detector amplifier information, which is used in IsrTask.     Talked to <USER> These values should take precedence over the values in the fits header. They seem stable and do not seem to vary with time.   "
Answer: 21532.0

User story: "The DHT test fixture, developed during the preliminary work with kademlia, needs some updates for the next stage of the prototype:  * adapt to reworked http library  * adapt DHT interface to be more generic  "
Answer: 13203.0

User story: "This experimental library turned out to be quite useful.  Next stage of prototyping will be making greater use of this, and I anticipate this library will also be used in production code.  Spend some time cleaning up and organizing this lib so it doesn't get off to a bad start, and prepare for general review/feedback from the team."
Answer: 13205.0

User story: "The bug appeared first when flipping an image with mask overlaid on it. Further study showed that the flip function has a bug when the FITS image values are integers. "
Answer: 496794.0

User story: "I am seeing failure to build due to test  failures for ctrl_events on a CentOS7 instance on the Nebula Openstack.  Details to follow."
Answer: 2627.0

User story: "LSST IaM draft recommendations from NCSA.  Group includes: Jim Basney, Terry Fleury, and Dan Thayer."
Answer: 25488.0

User story: "Build instance and snapshot on Nebula for HTCondor worker with v11_0 LSST stack."
Answer: 14475.0

User story: "October 8, 2015    - Refresh of security plan, sub-plan       - Talk about camera subsystem refusal to buy-in to security plan    - IaM work moving along       - Continue bi-weekly meetings with developers       - Most likely going with kerberos       - Iain meeting with Jim and Co on authn/z work    - Joint technical meeting in February       - when and where?  Santa Cruz, Feb 22-24th 2016    - security plan refresh:       - cover email with old document and instructions       - DM: Don P. and <USER>      - EPO       - PO: Iain       - Camera       - Incidents: all reports are collected and acknowledged"
Answer: 1.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: "October 14, 2015 (local)    - Drawing identity access management architecture on whiteboard.    - DB access via kerberos       - mariaDB does pam but does it do kerberos tickets?            - could then simply access with a ticket   - if users are exporting VMs/containers, do they need keytabs?  how do we support this?   - what does the ID linking?   - do we need replication to base site so that base site can operate independent     - Can we get 2 LSST VMs?     - NCSA cyber-infrastructure standards?  MIT Kerberos?  OpenLDAP?    - Meeting with <USER>   "
Answer: 1.0

User story: "Improve the presentation of the New docs overall:    # Add a Creative Commons license  # Remove stub documents from the presentation  # Put READMEs in all doc directories to explain what content will go in them  # Clean up and update the source installation guide to reflect 11_0"
Answer: 7258.0

User story: "Support for cloning from lfs backed repos, when indicated via repos.yaml, is needed.  "
Answer: 20097.0

User story: "{{ORDER BY}}, {{objectId IN}} and {{objectId BETWEEN}} predicates support have been improved, this should be documented.    "
Answer: 146736.0

User story: "It seems safe to update the Discourse trust level of all members of the LSSTDM group on community.lsst.org to Level 4 (full permissions). See https://meta.discourse.org/t/consequences-of-using-or-bypassing-trust-levels-for-company-organization-staff/34564?u=<USER>   This should alleviate concerns that DM staff are being prevented from fully using the forum.    This ticket implements a small notebook to exercise the Discourse API to make this trust level migration possible."
Answer: 5.0

User story: "The overscan and prescan regions of instcal data have been trimmed, but they are included for raw data.  The amplifier information in the current camera descriptions were made for instcal data and do not include overscan and prescan regions.      While processing raw data with the current camera descriptions, the bounding boxes from the camera object seem incorrect for raw data.     Code change summary:  - Use non-zero overscan and prescan regions  - Update the pixel array layout. My schematic of pixel array layout is attached in DecamAmpInfo.png    Screenshots are post-ISR images processed with bias and flat correction using the old or updated camGeom.  "
Answer: 16930.0

User story: "Small API change in latest xrootd, requires a parallel change to qserv.  Paves the way for DM-2334"
Answer: 132.0

User story: The "cat" package has a table which the Logger in ctrl_orca uses to insert information from logging messages.  The format of the log messages has changed, and therefore the table in "cat" needs to be changed as well.
Answer: 244776.0

User story: "The Logger.py file uses df_persistence to insert log messages.  Switch this to use db/SqlAlchemy."
Answer: 334041.0

User story: "Attend DM boot camp to learn more about DM stack, butler, and task. "
Answer: 40805.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 DM boot camp to learn more about DM stack, butler, and task.     Most of the presentations are located at URL https://community.lsst.org/t/dm-boot-camp-announcement/249. Presentations like afw, eups, tasks, and butler are necessary to participate in LSST, so everyone on LSST must understand these concepts. Look at the list of presentations covering these topics and make sure your understand them. Some of the remaining talks go into more detail or cover more specialized topics. Those talks should be scanned to see if they are of interestß to you."
Answer: 40809.0

User story: "Attend DM boot camp to learn more about DM stack, butler, and task. "
Answer: 40809.0

User story: "A focused week long design meeting on Firefly conversion from GWT to React/FLUX.  Design document at https://confluence.lsstcorp.org/display/DM/Firefly+Client+Application+Architecture.  "
Answer: 242.0

User story: "A focused week long design meeting on Firefly conversion from GWT to React/FLUX. Design document at  https://confluence.lsstcorp.org/display/DM/Firefly+Client+Application+Architecture  "
Answer: 246.0

User story: "A focused week long design meeting on Firefly conversion from GWT to React/FLUX.    Produce the first draft of design document   https://confluence.lsstcorp.org/display/DM/Firefly+Client+Application+Architecture"
Answer: 244.0

User story: "A focused week long design meeting on Firefly conversion from GWT to React/FLUX.   Agenda and notes here https://confluence.lsstcorp.org/pages/viewpage.action?pageId=41786446  Design document at https://confluence.lsstcorp.org/display/DM/Firefly+Client+Application+Architecture  "
Answer: 238.0

User story: "If the logging mechanism is turned off in ctrl_execute, the ctrl_orca Logger doesn't get launched.  The current shutdown mechanism waits for the last logging message to be transmitted before shutting down so it doesn't kill off that process.   If the logger.launch config file option is set to false, this process never get launched and ctrl_orca hangs after the shutdown waiting for the message to arrive."
Answer: 53571.0

User story: "We need a React component, which manages tabs. "
Answer: 28338.0

User story: "lodash has become a superset of underscore, providing more consistent API behavior, more features, and more thorough documentation. We'd like to convert our underscore package dependencies to lodash while we have only ~20 calls to underscore functions"
Answer: 28343.0

User story: "RFC-95 proposes new features in the Butler (probably actually implemented in {{CameraMapper}}) and the {{CmdLineTask}} argument parser to support running the pipeline on intermediate data products produced by external pipeline, such as the DECam community pipeline.    This issue represents the implementation of that feature."
Answer: 2046414.0

User story: "Remove es6-promise, react-modal, other cleanup"
Answer: 28603.0

User story: "Review and assemble eslint rules, which enforce clean JavaScript and JSX code.    Code cleanup to avoid too many rule violations."
Answer: 28600.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 can't seem to clone a tag to master anymore, and in fact something has gone wonky with the tag "master":  {code}  localhost$ eups tags --clone b951 master  eups tags: Unsupported tag(s): master    # I can't even list master anymore:  localhost$ eups list -t master  Ignoring unsupported tags in VRO: master  eups list: Unsupported tag(s): master    # and indeed master is not listed in global.tags; should it be?  localhost$ echo $EUPS_PATH  /Users/<USER>LSST/lsstsw/stack  localhost$ cat /Users/<USER>LSST/lsstsw/stack/ups_db/global.tags   current stable latest b860 b861 b862 b863 b864 b865 b866 b867 b868 b869 b870 b871 b872 b873 b874 b875 ... b950 b951    # and of course there are packages tagged b951  localhost$ eups list -t b951  afw                   11.0-5-g97168e0  b950 b951  afwdata               8.0.0.1+29  b949 b948 b946 b945 b944 b943 b941 b950 b951 current  astrometry_net        0.50.1+8    b949 b948 b946 b945 b944 b943 b941 b950 b934 b951 b935 current b933  ...    # this is with eups version 1.5.8  localhost$ eups --version  EUPS Version: 1.5.8  {code}    Any idea how my stack got into this state and how best to fix it?  
Answer: 137.0

User story: "While still prototyping I need to fill documentation on new code as well as do some clean up as well"
Answer: 70637.0

User story: "Incorporate Configuration and data reference to implementation"
Answer: 50630.0

User story: "Starting to implement the structure of the Super Task framework for process execution"
Answer: 9.0

User story: "This story captures issues/topics that we want to bring up with mysql team."
Answer: 224741.0

User story: "Re evaluate previously proposed storage policies: https://wiki.ncsa.illinois.edu/display/LSST/Storage+Policy?src=contextnavpagetreemode    Plan new policies:  https://wiki.ncsa.illinois.edu/display/LSST/Changes+to+Storage+Policy+and+Design?src=contextnavpagetreemode"
Answer: 15778.0

User story: "Coordinating with storage expertise to test and tune GPFS from Condo to dev environment, NFS from GPFS into dev environment and GPFS/NFS into OpenStack."
Answer: 14383.0

User story: "Approval process for FY16 procurement plan. This requires approval from Jeff K, Victor and NSF (due to the cost increment being greater than $250K).    Expected approval time frame: Dec 2015."
Answer: 14389.0

User story: "Discussions with vendors on planned procurement. Details of discussions will not be described here. This is for story point tracking only."
Answer: 14389.0

User story: "Prepare plan and ICI-group-specific points of interest for hardware/service deployment plans. "
Answer: 14391.0

User story: "Pan Starrs data release (PS1) will be used in the integration QServ environment purchased as part of FY16. Catalog and file space requirements must be understood."
Answer: 4.0

User story: "Add remaining components: power estimates, vSphere annual licensing, networking, PDUs, login nodes    review: misc expense fund, decommissioned services, financial targets"
Answer: 1.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: "- Verification datasets meetings  "
Answer: 24598.0

User story: "Use of  QsRestrictor::PtrVector introduces a useless indirection. it maybe could be replace by std::vector<QsRestrictor> and use of move constructor. This would simplify code (currently a confusion exists between empty vector and nullptr) and ease maintenance."
Answer: 1979609.0

User story: "Switch from a {{json}} cache to a redis cache from the community_mailbot."
Answer: 2646279.0

User story: "jointcal currently uses a combination of raw pointers and a custom reference-counted smart pointer class, {{CountedRef}} (similar to {{boost::intrusive_ptr}}).  The code needs to be modified to use a combination of {{shared_ptr}} (most code), {{unique_ptr}} local-scope variables and factory functions, and {{weak_ptr}} (at least some will be necessary to avoid cycles in some of the more complex data structures).  As part of this work, we'll also have to remove a lot of inheritance from {{RefCounted}}, which is part of the {{CountedRef}} implementation.    This ticket looks like it will require a lot of work, because we'll have to be careful about every conversion to avoid cycles and memory leaks.  Nevertheless, I think it will be necessary to do this conversion before attempting any other major refactoring, as I'm worried that having a newcomer make changes to the codebase without first making the memory management less fragile could be very dangerous."
Answer: 830492.0

User story: "Produce a screencast tutorial of the DM git-lfs implementation."
Answer: 84852.0

User story: "Per review comments for DM-3690, the community_mailbot can have slight code refactoring    - Refactor scripts into smaller testable units  - Refactor the Discourse feed classes around an ABC  - More testing"
Answer: 2646359.0

User story: "Per review comments to DM-3690, the configuration should move to YAML with the following goals    - Have a Configuration object that can be tested and passed around  - Redesign the configuration to allow for additional types of message handlers, such as twitter, hipchat/slack, etc.  - Move secret keys entirely into the configuration file  - Provide a configuration template  - Move any sort of hard-coded configuration to the expanded YAML file (e.g., Mandrill templates)"
Answer: 2625112.0

User story: "With the agreement to switch many of our boost usage to the modern C++11 equivalent, we also need to update the recommendations for how {{boost}} is used by developers. This ticket involves transferring the trac document from [https://dev.lsstcorp.org/trac/wiki/TCT/BoostUsageProposal] to Confluence (or where the current documentation lives) and updating it to reflect the outcome of RFC-100."
Answer: 169459.0

User story: "Try out some new functionalities of afw.cameraGeom.utils (from DM-2437) for DECam raw data. Raw data in {{testdata_decam}} are retrieved through Butler and displayed as a focal plane mosaic.  "
Answer: 28423.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: "Inside obs_sdss there is a yanny.py that looks like it was copied from either sdss_python_module or pydl. We should just depend on pydl (https://github.com/weaverba137/pydl), so we can use whatever improvements it gets for free, and to prevent yet annother yanny reader floating around."
Answer: 36276.0

User story: "Add doc directory and fix doxygen warnings."
Answer: 15817.0

User story: "Started studying LSST coding policies and best practices via confluence.  Colloquium.  Small meetings with other LSST team members throughout day.  Rebuilt PhoSim/LSST-Stack to take advantage of multiple cores when rendering portion of sky to a file. Built these commands into Stack code. They would have to be custom #defined by ./configure at build time depending on computer arch. which is too much to do when just gaining familiarity so stuck to MacBook  multi-core specs, where I was working.  Logged into JIRA and studied how tasks were proposed, realized, and checked as done.  Extensive talk about BBQ in group area of NCSA/LSST.  Close reading and note taking of LDM-230 and related docs."
Answer: 171362.0

User story: "Completed setup of confluence access.  Set up LSST HipChat.  Jumped into PhoSim a bit more and resolved errors by dropping in a few symlinks here and there;  not a solution for a proper execution environment, but a time-save just to see PhoSim work and  have a platform for tinkering with camera attar's.  PhoSim ran successfully.  Learned about FTTS format and how the file is built up. Learned about how Key/Val pairs   can proceed ANY data section throughout file by using data offset values."
Answer: 171369.0

User story: "Installed and built LSST tutorials package.  Setup, fixed minor issues and ran First tutorial to check that initial stack  installation was successful.  Learned about CCD operation and how the LSST CCD is laid out.  Learned about raw CCD data from amplifiers, as well as other camera attributes  Studied stack code for these things.  Read description of Astronomy Associative relations as well as CoAdds.  Pulled PhoSim from repo. Built and Installed.  Had trouble getting PhoSim to run due to dynamic link library issues.  Instrumented PhoSim code with PDB commands.  Walked to bookstore and picked up new ID badge."
Answer: 171372.0

User story: "Installed correct Xcode + misc. for stack version.  Downloaded LSST stack from GitHub repo and built/installed.  "
Answer: 171375.0

User story: "Requisitioned used macbook and monitor from IT and set it up.  Located LSST stack site and read build and install documentation  More HR account items.  Requested confluence credentials from LSST.org  Learned about SDSS/Stripe 82"
Answer: 13448.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: "Meeting with HR at 8:30AM.  Taken around for introductions through 10AM.  Remainder of day was proceeding through HR punch list for new hires such as:   NCSA Intranet account setup   Gain familiarity with NCSA Intranet   Kerberos and Enterprise ID setup   Read and Sign-off  on Security and NCSA policy.   Outlook mail and calendar setup  2pm DM meeting"
Answer: 13451.0

User story: "DM boot camp tutorial.    "
Answer: 70655.0

User story: "Write a developer workflow guide to walk through and document best practices for developing against the LSST Stack."
Answer: 86398.0

User story: "Document cleanup. Added PDUs, networking estimates, power costs, vsphere licensing."
Answer: 1.0

User story: "Replace boost::tuple with <tuple>    This ticket will be completed as part of the DM bootcamp at UW."
Answer: 315258.0

User story: "Review LTS-210 and discuss design of EFD cluster with <USER>    Are there opensource clustering solutions?"
Answer: 2.0

User story: We use names like "forcedPhotCcd.py" for bin scripts but "ProcessCcdForcedTask" for class names; these need to be made consistent, and it's the former convention that was selected in an old (non-JIRA) RFC.
Answer: 1405033.0

User story: "The {{FlagHandler}} utility class makes it easier to manage the flags for a measurement algorithm, and using it also makes it possible to use the {{SafeCentroidExtractor}} and {{SafeShapeExtractor}} classes.  Unfortunately, its constructor requires arguments that can only be provided in C++.  A little extra Swig wrapper code should make it usable in Python as well."
Answer: 368401.0

User story: The templates that ctrl_execute fills in still use "root", instead of the new "config".  This causes extraneous warning messages to appear from pex_config when executing "runOrca.py"
Answer: 117.0

User story: "Currently raw DECam data can not be processed with the stack for Instrumental Signature Removal (ISR).  This issue includes efforts to understand how ISR is done in the stack, learn about processCcd, basic DECam ISR, and what is missing in the code stack to proceed.    "
Answer: 39988.0

User story: "To switch from QservAdmin to CssAccess interface in our Python tools we will need to replace zookeeper with mysql implementation because we do not have C++ KvInterface implementation for zookeeper."
Answer: 15688.0

User story: "No obs_* packages have a doc dir. I suggest starting with obs_test since it is perhaps less obvious what it is used for than the others and in some ways acts as a template."
Answer: 5550.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: "Write a guide in the prototype LSST Stack Docs (https://github.com/lsst-sqre/lsst_stack_docs) covering how to document the LSST Stack under the new doc infrastructure.    This exercise will implicitly involve designing how the new docs will work. Content includes:    # How to write a user guide to a package (both content wise and in terms of organizing a package's doc files)  # How to write python doc strings  # Coverage of reStructuredText and Sphinx as implemented by the LSST Stack Docs.  "
Answer: 29052.0

User story: "The current scrolling system will not work as well with masking layer.  It is also suspected to use too much browser memory since is creates a very large div.  Firefly will scroll images manually now."
Answer: 272.0

User story: "Support for lsst-dev cluster, OpenStack, and accounts  for week ending September 26, 2015."
Answer: 5.0

User story: "Support for lsst-dev cluster, OpenStack, and accounts  for week ending September 19, 2015."
Answer: 4.0

User story: "Created backup of pugsley in anticipation of new hardware and shutdown of temp Mac OS solution"
Answer: 21487.0

User story: "Support for lsst-dev cluster, OpenStack, and accounts  for week ending September 12, 2015."
Answer: 21.0

User story: "Provided Josh Hobblitt details specs for procurement request"
Answer: 1.0

User story: "Support for lsst-dev cluster, OpenStack, and accounts  for week ending September 5, 2015."
Answer: 11.0

User story: "{{SourceDeblendTask.run}} takes both an {{Exposure}} and a {{Psf}}, even though it can get the latter from the former and always should."
Answer: 370470.0

User story: "Qserv latest release can be deployed easily on cc-in2p3 cluster using Docker. This ticket will allow developers to prepare worker and master containers using a specific Qserv version and deploy it on cc-in2p3 cluster."
Answer: 90009.0

User story: "Qserv multinode test can be launched on n hosts using docker, but not on one unique host.  This ticket will allow developers to run multinode test on their workstation."
Answer: 193433.0

User story: "DM-1135 mostly was inconclusive or at least not highly significant, due to the fact that the error bars were around the same size as the differences in most of the tests. This in spite of the fact that we ran 6x as many sample galaxies as great3sims.    Investigate the reason for this, and see if we can estimate the errors more accurately.  Investigate what the best way (or at least the way it is done in GREAT3) to estimate the errors on the bias parameters.     If it is not from the covariance matrix of the regression parameters, there could be some work here."
Answer: 87772.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 stampsize and nInitalRadius tests were not conclusive in the September Sprint. and the error estimates appeared to be overly large. The nGrowFootprints test was barely significant.  This is a continuation of work started on DM-1135 (DM-1135, 3375, 3376) , after a study of the sizes of our error estimates was conducted (DM-3984).    We started with a sample with 12 million galaxies (not all of which were used in DM-3375 and 3376.  They appeared to all be useful once we had new error estimates, so the studies were run against with this larger sample. "
Answer: 87780.0

User story: "Make FitsRead work better for multi-threads"
Answer: 1362.0

User story: "Implement some minor tweaks take came in late through PR comments, mostly related to sqlalchemy related migration"
Answer: 48.0

User story: "provide switch quantities, weight, power and budgetary costs"
Answer: 101999.0

User story: "Qserv restrictors should be converted from string to int in Qserv C++ code for more efficiency and better maintenance."
Answer: 2379824.0

User story: "Db module is expected to be used by science pipelines, and (per K-T, see qserv hipchat room) we have to package it through eups."
Answer: 598.0

User story: "Dealt with impending new hire.   Good deal of intergroup coordination, and deal with NCSA re organization."
Answer: 140974.0

User story: "NCSA or Astronomy Department activities.   - NCSA All-hands  - Local LSST group meetings   - DES-Illinois meetings  - Colloquia  - other seminars, info sessions, or other local meetings"
Answer: 2976.0

User story: "verification datasets weekly meetings and tech-talks"
Answer: 2983.0

User story: "Building a proof-of-concept prototype of provenance.    Deliverable: a working, standalone (not connected to any data producer) prototype of the Data Provenance. Not optimized / alpha version."
Answer: 115291.0

User story: "Think through the issues of querying provenance. Deliverable: write up attached to this story. IT will be transferred to more official provenance documentation through DM-3961"
Answer: 90542.0

User story: "Revisit estimates of the size of provenance information."
Answer: 80593.0

User story: "Discuss existing provenance design with the team, brainstorm and improve. Primary focus on capturing provenance information. Deliverable: proof-of-concept prototype + description."
Answer: 46228.0

User story: "CModel needs to run in CalibrateTask before PhotoCal in order to compute aperture corrections, but it also needs a Calib objects as input, and that isn't available until after PhotoCal is run.    On the HSC side, we dealt with this by adding preliminary PhotoCal run before CModel is run, but we could also deal with it by removing the need for a Calib as input, at least in some situations."
Answer: 323864.0

User story: "Db module is expected to be used by science pipelines, and (per K-T, see qserv hipchat room) we have to package it through eups."
Answer: 1513.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: "Files generated on instances of the Nebula openstack  should be managed with some commensurate  level of data replication/backups.     We investigate services that might serve this task within the cloud context."
Answer: 256494.0

User story: Maybe some cleanup can also be performed in lua code. Indeed "objectId" hint and parseObjectId() which seems useless.    Indeed miniParser.parseIt and miniParser.setAndNeeded seems useless.    Removing this code will ease maintenance of objectId management.
Answer: 5011.0

User story: "qserv_objectId restrictor can be replaced by the IN restrictor. This story involves checking if performance is acceptable if we use IN restrictor instead of qserv_objectId restictor, and if it is, doing the switch and removing the qserv_objectId restictor code."
Answer: 52676.0

User story: " {{selectStars()}} is the primary method in {{lsst.meas.algorithms.SecondMomentStarSelector}} and all other StarSelectors in meas_algorithms. The primary method in {{lsst.ip.diffim.DiaCatalogSourceSelector}} is {{selectSources}}. Source selectors should have the same API to facilitate using as swappable subtasks in {{ImageDifferenceTask}}.    The simplest solution is to rename the method in {{DiaCatalogSourceSelector}} to {{selectStars}}.  "
Answer: 295637.0

User story: "Remove remaining dependencies on mysqldb in qserv.:  {code}  ./core/modules/tests/MySqlUdf.py  ./core/modules/wmgr/python/config.py  {code}    and use the sqlalchemy from db module instead."
Answer: 190157.0

User story: "Move remaining code that depends on mysqldb to db module"
Answer: 4624.0

User story: Create the "Orchestration and Control" slide set for DM Bootcamp, which is being held from Oct 5-7, 2015.  After review (and any revisions), the slide set will be uploaded to confluence, and a link to it will be put here.
Answer: 15859.0

User story: "This ticket is in preparation for DM-2984, which is to run both the HSC and LSST pipelines on 2-3 visits of HSC data, and do a detailed comparison of the science quality and robustness for the single-frame processing (ProcessCcdTask) stage only.  Essentially, it is a detailed audit of all the functionality currently used in HSC single-frame processing and ensuring all relevant features have been pulled over to the LSST stack such that the comparisons to be done in DM-2984 will be meaningful and informative."
Answer: 52296.0

User story: "Fy16 purchase planning needs to be split for specific audiences (NCSA planning, Aura purchase approval)"
Answer: 7634.0

User story: "The HSC fork includes additional work to improve temporary file usage in the butler:  * [HSC-1275|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1275]: Probable resource leakage by butler  * [HSC-1285|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1285]: eups.version files ignore umask  * [HSC-1292|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1292]: Prevent opening files that are already open"
Answer: 49981.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: To reproduce:  {code}  >>> import lsst.daf.persistence as dafPersist  >>> butler = dafPersist.Butler('/lsst8/image_diff/calexp_dir_Blind14A_10/')  CameraMapper: Loading registry registry from /lsst8/image_diff/calexp_dir_Blind14A_10/registry.sqlite3  >>> butler.get('calexp', visit=289493, ccdnum=15)  <lsst.afw.image.imageLib.ExposureF; proxy of <Swig Object of type 'boost::shared_ptr< lsst::afw::image::Exposure< float,lsst::afw::image::MaskPixel,lsst::afw::image::VariancePixel > > *' at 0x7f5882437de0> >  >>> butler.get('calexp_md', visit=289493, ccdnum=15)  Traceback (most recent call last):    File "<stdin>", line 1, in <module>    File "<string>", line 1, in __repr__    File "/home/lsstsw/stack/Linux64/daf_persistence/11.0.rc2+10/python/lsst/daf/persistence/readProxy.py", line 41, in __getattribute__      subject = oga(self, '__subject__')    File "/home/lsstsw/stack/Linux64/daf_persistence/11.0.rc2+10/python/lsst/daf/persistence/readProxy.py", line 136, in __subject__      set_cache(self, get_callback(self)())    File "/home/lsstsw/stack/Linux64/daf_persistence/11.0.rc2+10/python/lsst/daf/persistence/butler.py", line 236, in <lambda>      location, dataId)    File "/home/lsstsw/stack/Linux64/daf_butlerUtils/11.0.rc2+15/python/lsst/daf/butlerUtils/cameraMapper.py", line 317, in <lambda>      afwImage.readMetadata(location.getLocations()[0]))    File "/home/lsstsw/stack/Linux64/afw/11.0.rc2-2-g04d2804+2/python/lsst/afw/image/imageLib.py", line 1146, in readMetadata      return _imageLib.readMetadata(*args)  lsst.pex.exceptions.wrappers.TypeError:     File "src/PropertySet.cc", line 858, in virtual void lsst::daf::base::PropertySet::_add(const string&, boost::shared_ptr<std::vector<boost::any> >)      LTV2 has mismatched type {0}  lsst::pex::exceptions::TypeError: 'LTV2 has mismatched type'  {code}
Answer: 1505.0

User story: "When load the big.fits file, the image never came out.  It stopped at Histogram.  There was an infinity in Histogram.   "
Answer: 22.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "A number of issues with sandbox-stackbuild, or rather its infrastructure.    1. Problem with the librarian-puppet plugin and its mismatch with the puppet forge API ([~<USER> has a PR open apparently)    2. As a workaround to above, one needs to    {code}  gem install librarian-puppet  librarian-puppet install  {code}    but that runs into an issue with swap_file needing a downgrade to work with Ubuntu 14.04. Working state as of the time of this bug report for the Puppetfile is:    {code}    forge 'https://forgeapi.puppetlabs.com'    mod 'puppetlabs/stdlib'  mod 'camptocamp/augeas', '~> 1.4'  mod 'stahnma/epel', '~> 1.1'  mod 'petems/swap_file', '1.0.1'  mod '<USER>sysstat', '~> 1.1'  mod 'maestrodev/wget', '~> 1.7'    mod '<USER>lsststack', :git => 'https://github.com/lsst-sqre/puppet-lsststack.git'  {code}    3. Which brings us to the fact that the Vagrant puppet-install plugin is broken with Puppet 4, and new platforms are not supported under Puppet 3. Ergo, as is, can't bring up Ubuntu 15.05 etc.     Ticket is to get PRs merged, fork and fix them ourselves, or find alternatives.   "
Answer: 1148061.0

User story: "Added physical breakdown for Alert Postage Stamp Images file system, co-add images file system and image cache file system"
Answer: 1.0

User story: "  Input is being gathered here:  http://ls.st/sli    [Team membership affects the application of the tagging policy]    "
Answer: 809587.0

User story: "Implement proposed in RFC-96 change to log macros. This ticket only covers defining new set of macros (LOGS() and friends) which use ostringstream for formatting messages. Migration of all clients and removal of LOGF macros will be done in separate ticket."
Answer: 99593.0

User story: "DId this    {code:java}    publish -b b1694 -t v11_0_rc3 lsst_distrib  {code}    and unexpectedly ended up with a bunch of sims packages in:    https://sw.lsstcorp.org/eupspkg/tags/v11_0_rc3.list    Could be publish, could be lsstsw, could be buildbot, could be my user error - filing so I don't forget, not an action item for anyone in SQuaRE at this point.    Data point: happened for 10.1 too. "
Answer: 254352.0

User story: "Centralize Sphinx configuration for design documents in {{documenteer}} and provide a facility for design document authors to use YAML files to store document metadata rather than editing {{conf.py}} files."
Answer: 2.0

User story: "Workers in multi-node setup no longer require granting mysql permissions for test datasets since direct mysql connections are no longer used by the data loader."
Answer: 28.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 and deploy a git-lfs-s3 server.    High level requirements:    * The server should use github to authenticate users. Any github user who is a member of the lsst organization has write access. This means they can push objects to the git-lfs server.  * The server should allow for anonymous read access. This means anyone can clone, pull, fetch, etc.  * Use an S3 compliant API to store objects.  * Simple, well defined method to redeploy.  * Uses https.  * Backs up to Amazon Glacier (or similar) periodically. The data should be "slow" so backing up approximately once a day is OK.
Answer: 85219.0

User story: "Thinking, (but not delivered use case)  -- what is the flow of tickets and the division of use cases between the Science and Data Operations?  What kind of tooling needs can be assumed to exist to support service management what does that mean for the support of processes?  (specifically  looked at a summary of the state the market, and took specifics look at what ITSM process supporting tools are open source. -- as may be useful to prototype processes before committing to something..  Looked at several, ITOP seemed to be mature/documented to a level that may be useable.    "
Answer: 7.0

User story: "Deal with comments,  coordinate with Jason Alt. Deal with comments on existing work from KT and GDF"
Answer: 13.0

User story: "This will demonstrate how LaTeX-based DM design documents can be continuosly deployed to the web with Travis CI onto GitHub pages. tex4ht is the HTML rendering engine."
Answer: 114059.0

User story: "There are a couple of ctrl_events tests that attempt to execute outside of the valid domains acceptable by the tests, when they shouldn't be.  There's a check in place for tests to find this, but a couple of the tests do not have this check."
Answer: 10.0

User story: "This is a port of [HSC-1106|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1106]    When running tasks that write out config settings files ({{processCcd.py}}, for example), if multiple processes start simultaneously, an I/O race condition can occur in writing these files.  This is solved here by writing to temp files and then renaming them to the correct destination filename in a single operation.  Also, to avoid similar race conditions in the backup file creation (e.g. config.py~1, config.py~2, ...), a {{--no-backup-config}} option (to be used with --clobber-config) is added here to prevent the backup copies being made.  The outcome for this option is that the config that are still recorded are for the most recent run."
Answer: 59223.0

User story: "In order to validate Docker setup on CC-IN2P3 cluster, it is required to launch some test on consistent data. S15 LargeScaleTest data doesn't seems to be compliant with latest Qserv version so running multi-node test would be interesting. Nevertheless the multi-node setup doesn't seems to be documented and, hence, is difficult to reproduce."
Answer: 37627.0