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: "The background matcher is one area where the approximate/interpolate class will be used.  This story will find all places (including examples and unit tests) where the old approximate/interpolate mechanisms are used and update them to use the new interface."
Answer: 2740534.0

User story: "Make fixes to background class to use new approximate/interpolate class."
Answer: 2740536.0

User story: "Use the HSC implementation of the base class as a point of reference for designing an integrated Approximate and Interpolate class.  The design take into account Chebyshev, spline, and Gaussian process mechanisms.  Want to take into consideration client code.  I.e. it shouldn't make current consumers more complicated (background and aperture correction to name two).  RFC the designed API."
Answer: 87513.0

User story: "See https://confluence.lsstcorp.org/display/DM/Qserv+Release+Procedure for recipe."
Answer: 41766.0

User story: "* Find region that returns multiple tractPatchLists for testing.  * Request region via central point (RA, Dec) with width and height definable in arcseconds and pixels.  * May be extend web interface to other data sets, and/or good seeing SkyMaps. "
Answer: 100583.0

User story: "I  cloned lsstsw into ~/Desktop/templsstsw and cd'd into it and typed ./bin/deploy and was shocked to find it installed everything into ~/lsstsw, leaving an unsable mess: some files were in templsstsw and some in ~/lsstsw.  The short-term workaround is to manually set LSSTSW before running ./bin/deploy, but this should not be necessary; bin/deploy should either set LSSTSW or not rely on it. I don't recall this problem with earlier versions of lsstsw; I think this is a regression.  For now I updated the instructions at https://confluence.lsstcorp.org/display/LDMDG/The+LSST+Software+Build+Tool but I look forward to being able to revert that change."
Answer: 1388.0

User story: "Despite the discussion & supposed fix at DM-2347, the same confusion still occurs. Although we agreed to {{%useValueEquality}} for {{Coord}}, that code was never committed."
Answer: 20.0

User story: The Doxygen documentation for {{lsst::afw::image::wcs}} contains a number of minor mistakes and typos. Perhaps most egregiously, it [repeatedly|https://lsst-web.ncsa.illinois.edu/doxygen/xlink_master_2015_04_01_07.01.48/classlsst_1_1afw_1_1image_1_1_wcs.html#a0af8218e58db172c39f8e7a6004c81a0] [claims|https://lsst-web.ncsa.illinois.edu/doxygen/xlink_master_2015_04_01_07.01.48/classlsst_1_1afw_1_1image_1_1_wcs.html#a58c33b803b01a091621c59a3d46166f8] that functions called {{pixelToSky}} "convert from celestial coordinates to pixel coordinates". Further, a lot of documentation is duplicated, because it's included in both the header and the implementation (often in somewhat contradictory ways).  "Minor" doc fixes don't normally need tickets or review; since I'm changing quite a few lines at once here, I think it's worth filing and getting a second pair of eyes to check the changes.
Answer: 566.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: "Most work here was with designing firefly tools API related details."
Answer: 42733.0

User story: "We need a means of authenticating and authorizing users to interact with the CI system.  The current seem of using an htpasswd file with buildbot is a hassel both for end user and administratively.  Jenkin's has support for ldap and there is a plugin available for github oauth.  Administratively, and it terms of reliability, it may make more sense to be coupled with github than a a new DM or the exist LSST LDAP instance."
Answer: 10149.0

User story: See [~<USER> comment:    Fabrice, anything is possible in C++, if you can define toString() for vectors it should also be possible to define some other construct to format vector into a stream :)  My objection to toString() is based on couple of of observations:      most of the time in our code converting complex objects to string is done to push them to streams or to logging system (logging is also usually based of streams)     methods like toString() are usually implemented using temporary streams.  So if you write code like cout << toString(vector) or LOGF_DEBUG("vector: %1%" % toString(vector)) it is very inefficient because it creates temporary stream and temporary string(s).  To make it more efficient you have to define operator<<() which is implemented without using toString(). Then you could implement toString() based on operator<<() but I'd argue that you should avoid it. In case you really need to convert to string there semi-standard tools which already do the same for types that have operator<< defined (like boost::lexical_cast), but again most of the time you only need operator<< as you don't want to mess with strings.  If you want to know how to implement operator<< for vector (or any container) here is the sketch of what I would do (there might be simpler ways):  {code:c++} namespace detail {     template <typename Cont> struct _ContInserterHelper {         const Cont& cont;     };     template <typename Cont> std::ostream& operator<<(std::ostream& out, const _ContInserterHelper<Cont>& cins) {         out << "[";         const Cont& cont = cins.cont;   // this is container itself         // print container elements with separators         return out << "]";     } } template <typename Cont> detail::_ContInserterHelper<Cont> ContInserter(const Cont& cont) {     return detail::_ContInserterHelper<Cont>{cont}; } {code}  And after that you can do:  {code:c++} std::vector<int> v; std::cout << ContInserter(v); {code}  And this has no overhead or any temporary objects created. 
Answer: 423193.0

User story: "The eupspkg.cfg.sh for the tmv package forces the build to only use one process.  Relax that condition to speed up the build."
Answer: 171.0

User story: "Read up on current IRODS usage and development track. "
Answer: 50449.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: In our first tests of iRODS, we have used "iput" to load data into iRODS cache spaces (the iRODS Vault).  For large collections already in a well known location on a server, one may want to leave the data in place but still manage it with iRODS. To do this one can use "ireg" to register the data with IRODS without the upload process.
Answer: 10140.0

User story: "iROD manages data as a 'virtual collection', that is, one can have a single logical/virtual view of a collection of files (the appearance of a single file system/tree) while the data with the collection is stored on separate physical servers. We demonstrate this by creating a collection with data targeted/uploaded to different physical resources."
Answer: 10145.0

User story: "A fundamental feature of using iRODS would be to prevent file loss/corruption incidents by replicating data to different physical servers, possibly in geographically disparate locations. We verify that we can replicate data within out test zone/grid."
Answer: 30215.0

User story: "Image stitching is currently using coadd_utils.Coadd.addExposure (which in turn calls lsst::coadd::utils::addToCoadd) to copy pixels from source images to a destination image. This is not the intended purpose of Coadd and there are significant short comings, notably pixels marked as edge are not copied, and pixels from the source image are added to existing pixels in the destination image.  New code needs to be written to copy valid pixels from a source image to the destination image only if the destination pixels is blank. This should probably not be part of the Coadd module as addToCoadd needs to be very efficient and this is something different than coadding. There is some question of whether this should go in imgserv or afw.  "
Answer: 2798.0

User story: "One of the things that exists on the HSC side of things but not LSST is the ability to use showCamera to create full-focal-plane mosaics.  Please convert the code to run with the new cameraGeom    Not only is this generically useful, but it's part of the effort required to make the DM-side visualisation work for the Camera group  "
Answer: 237927.0

User story: "HSC-1196 includes fixes and test cases for {{afw}}. After review on HSC, they should be checked/merged to LSST."
Answer: 207.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: "Attempting to read an Exposure (in this case via the butler) fails if the PSF class isn't available.  An exception would be reasonable, but an assertion failure is not.  Running the attached script on tiger-sumire with bq. setup python anaconda; setup -T v10_1_rc2 lsst_apps; setup -j distEst -t HSC; setup -j -r ~/LSST/obs/subaru  {code}  WARNING: Could not read PSF; setting to null: PersistableFactory with name 'PsfexPsf' not found, and import of module 'lsst.meas.extensions.psfex' failed (possibly because Python calls were not available from C++). {0}; loading object with id=4, name='PsfexPsf' {1}; loading object with id=28, name='CoaddPsf' {2} python: src/table/io/InputArchive.cc:109: boost::shared_ptr<lsst::afw::table::io::Persistable> lsst::afw::table::io::InputArchive::Impl::get(int, const lsst::afw::table::io::InputArchive&): Assertion `r.first->second' failed. Aborted {code}"
Answer: 45247.0

User story: "Modify the simulation code to draw PSFs at random from a library of on-disk files (whose format and on-disk layout should be specified here).  The PSFs chosen should be deterministic via a random number generator seed specified via config.  This is one of several issues that together will replace DM-1132 (which was just a planning stand-in for these more detailed issues)."
Answer: 46984.0

User story: "Modify the GREAT3 simulation scripts to create a branch in which each galaxy gets a different constant PSF, rather than one constant PSF per subfield or a spatially-varying PSF that spans multiple subfields.  This could be done by modifying the control/ground/constant branch or the variable-psf/ground/constant branch, or creating an entirely new branch, or anything else (since we don't actually need multiple branches in our simulations).  At this point, the source of the PSFs doesn't really matter - as long as we have a class that can provide a different one to every image.  This is one of several issues that together will replace DM-1132 (which was just a planning stand-in for these more detailed issues)."
Answer: 46971.0

User story: "The GREAT3 simulations have a fixed postage stamp size (though this may differ between branches).  A first step at modifying the simulation scripts to meet our needs would be to try to change the postage stamp.  This is one of several issues that together will replace DM-1132 (which was just a planning stand-in for these more detailed issues)."
Answer: 45975.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 the GREAT3 simulation code running with LSST-provided third-party packages of Python, GalSim, etc, and figure out where we're going to put our modified scripts on GitHub:  - Do we just put things in a fork of the great3 repo, or do we have other repos layered on top of a fork of the great3 repo?  (I think probably the latter, but we should determine how many repos, and for what purposes.)  - Where in GitHub space do we put them (lsst?  lsst-dm? user spaces?)  This is one of several issues that together will replace DM-1132 (which was just a planning stand-in for these more detailed issues)."
Answer: 46040.0

User story: Qserv server-side Python logging appears to mostly use a common format: "{{%(asctime)s %(name)s %(levelname)s: %(message)s}}".  It also mostly uses a common date format: "{{%m/%d/%Y %I:%M:%S}}".  But I see instances of: * "{{%(asctime)s %(levelname)s %(message)s}}" * "{{%(asctime)s - %(name)s - %(levelname)s - %(message)s}}" *  "{{%(asctime)s \{%(pathname)s:%(lineno)d\} %(levelname)s %(message)s}}" * and now, after DM-2176, "{{%(asctime)s \[PID:%(process)d\] \[%(levelname)s\] (%(funcName)s() at %(filename)s:%(lineno)d) %(name)s: %(message)s}}"  Unless these are used in very different contexts, it will aid automated log processing for them to be more standardized.  In addition, the date format is unacceptable as it does not use RFC 3339 (ISO8601) format and does not include a timezone indicator (which means the default {{datefmt}} is insufficient).  This must be fixed.  See also DM-1203.
Answer: 103543.0

User story: Implement methods that apply arbitrary functors to pixels within a SpanSet, as described on RFC-37.    The only tricky part of this implementation will be the "traits" classes that allow different target objects to interpreted differently.  I'd be happy to consult on this; I have a rough idea in my head, but it needs to be fleshed out.
Answer: 872453.0

User story: "Implement the following SpanSet operations:   - Construct from an ellipse - note geom::ellipses::PixelRegion; this should do most of the work.   - Compute centroid - see old Footprint implementation   - Compute shape (quadrupole moments) - see old Footprint implementation    One complication here is that this will introduce a circular dependency between afw::geom and afw::geom::ellipses.  That's easy to address at the C++ level, but it's tricky in Python (which package imports the other?)  I'll be emailing dm-devel shortly to start a discussion on how to address this problem."
Answer: 872456.0

User story: "Implement the core of the SpanSet class, as prototyped in RFC-37.  This includes the following:   - All STL container methods and typedefs, and their Pythonic counterparts.   - All constructors and assignment operators, except for SpanSetBuilder.  This includes the ability to detect and fix overlapping Spans.   - All simple accessors.   - {{isContiguous()}}   - The shift and clip methods."
Answer: 872462.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: "One challenge in switching from {{PTR(Span)}} to {{Span}} in {{Footprint}} is that Swig won't generate wrappers for {{std::vector<Span>}} (or any other container) if {{%shared_ptr(Span)}} is used anywhere else in the codebase.  So, to allow both the old {{Footprint}} class and the new {{SpanRegion}} to coexist (temporily), we need to have two {{Span}} classes, one wrapped with {{%shared_ptr}} and one wrapped without it.  Since we don't want to disrupt the old {{Footprint}} class yet, we should call the new Span something else, and make it the one that's wrapped without {{%shared_ptr}}.  This ticket can be considered complete once we have a unit test demostrating a usable Swig-wrapped {{std::vector<NewSpan>}} while all old {{Footprint}} tests continue to pass."
Answer: 721108.0

User story: "it seems we have two tools to manage python modules:  - site_scons/pytarget.py and - site_scons/site_tools/pymod.py (grep for InstallPythonModule) used by admin tools. We could unify this, isn't it?"
Answer: 443994.0

User story: New worker management service exposes its API as an interface to RESTful web service. Many or all "methods" will be wrapped into some sort of Python API, but it would still be useful to document every web service "methods" independently. There is basic documentation in the design document (https://dev.lsstcorp.org/trac/wiki/db/Qserv/WMGRDesign), this needs to be extended with detailed description of what those methods do and what kind of data they accept and return.  This story involves selecting the right tool.
Answer: 161618.0

User story: "We need some reasonable security for access to new worker management service. It should be lightweight and not depend on complex things that require infrastructure. Something based on a shared secret should be adequate for our immediate needs and likely for the long term."
Answer: 44944.0

User story: "Qserv contains lots of classes related to Error management. Would it be possible to unify these ones. For example having unique error code and error messages source files would be convenient for support and maintenance, (and in the possible long-term, internationalization)."
Answer: 2274306.0

User story: "The most popular Puppet module for managing Jenkin's {code}jenkinsci/puppet-jenkins{code} is able to create a master and build slaves but is missing the functionality to manage several master configuration options that otherwise require manual setup.  We need to investigate the difficulty of managing a Jenkin's master configuration values in an idempotent manner."
Answer: 7057.0

User story: "Currently integration tests use root account as default user - this should be changed to qsmaster for the future."
Answer: 123565.0

User story: "Qserv uses the osslib API in the cmsd (of XRootD) to report db/chunk availability. With the new XrdSsi async interface, there was an attempt to unify this API with the RPC API, but it does not seem to make sense to unify two separate APIs in a single place. "
Answer: 96734.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 place to capture changes related to Data Access and Database work that might require Kevin's attention and changes to our PMCS plan."
Answer: 234540.0

User story: "The Simulation throughputs repository has been moved from gitolite to Github. The repos.yaml file needs to be update to reflect the change. "
Answer: 7316.0

User story: "To familiarize myself with React and to prepare the ground for moving to React-based user interfaces, we need to create React components for the form. This story includes CheckboxGroup, RadioGroup, and Listbox input fields."
Answer: 2.0

User story: "To use JavaScript Interop functionality, we need to migrate to GWT 2.7"
Answer: 4.0

User story: "UserQueryFactory doesn't check its QuerySession object for errors after setQuery. Thus it continues setting things up after the QuerySession knows the state is invalid."
Answer: 8653.0

User story: "utils p_lsstSwig.i contains a special typemap which forces python arguments to be truly bools (True or False) when calling C++ functions with bool arguments. That code is no longer required by SWIG 3.0, according to this release note:  {quote}  2014-03-06: wsfulton              [Python] Change in default behaviour wrapping C++ bool. Only a Python True or False              will now work for C++ bool parameters. This fixes overloading bool with other types.              Python 2.3 minimum is now required for wrapping bool.  ...  {quote}"
Answer: 262058.0

User story: "testQDisp.cc needs flags -lpthread -lboost_regex to build on ubuntu."
Answer: 144.0

User story: "This is a separate ticket for implementation of the data loading part of the worker management service (started in DM-2176). Some ideas and thoughts are outlined in that ticket."
Answer: 41776.0

User story: "There is a growing list of known package dependencies in the sandbox-stackbuild repo and a need to use this information for independent environments (such as CI).  This list of packages should be lifted out into an independent puppet module that can be reused."
Answer: 24364.0

User story: "A user recently got confused when calling parseAndRun didn't call the task's run method. It turns out there was no data matching the specified data ID. Make sure this generates a loud and clear warning."
Answer: 92074.0

User story: "HSC data becomes public 18 months after it was taken, so data taken during commissioning are now available.  We would like to use this data for testing the LSST pipeline.  It needs to be downloaded from Japan."
Answer: 231917.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: Qserv logger must be easily configurable. Next technique, based on log4cxx documentation allows to do it easily.  Example:  In QuerySession.cc, initialize a static logger: {code:c++} namespace lsst { namespace qserv { namespace qproc {  LOG_LOGGER QuerySession::_logger = LOG_GET("lsst.qserv.qproc.QuerySession"); {code}  then use it in Query session member functions:  {code:c++}         if (LOG_CHECK_LVL(_logger, LOG_LVL_DEBUG)) {             std::ostringstream stream;             _showFinal(stream);             LOGF(_logger, LOG_LVL_DEBUG, "Query Plugins applied:\n %1%" % stream.str());         } {code}  And use log4cxx.property to easily configure, AT RUNTIME, logging for each Qserv module class:  {code} # logger for all module will inherit this one log4j.logger.lsst.qserv=ERROR # this could be generalized to all Qserv modules: log4j.logger.lsst.qserv.qproc=INFO # can also be done at the class level for advanced debugging #log4j.logger.lsst.qserv.qproc.QuerySession=DEBUG {code}  And then in the log: {code} /home/qserv/qserv-run/2015_03/var/log/qserv-czar.log:0319 17:08:48.786 [0x7f208da93740] DEBUG lsst.qserv.qproc.QuerySession (build/qproc/QuerySession.cc:118) - Query Plugins applied: {code}  This proposal is a draft and should be improved before implementing it.
Answer: 485200.0

User story: "* Demonstrate lsstswBuild.sh being invoked by jenkins on EL6 (same OS as lsst-dev). * Experiment with a single build slave attached to a jenkins master * Investigate configuration management of jenkins builds."
Answer: 17483.0

User story: "QuerySession::_stmtParallel is a vector but it seems only it's first element is used, so storing it in a vector doesn't seem necessary.  Code can be easily simplified here. This should lead to mode understandable code.  QuerySession public members and method comments could also be improved here."
Answer: 20.0

User story: The "driver" script, lsstswBuild.sh, used by the buildbot slave on lsst-dev to initiate a "CI run" has a number of environment assumptions (binaries in the $PATH, paths to various components, hostnames, etc.).  This prevents it from [easily] being invoked on any other host.  As lsstswBuild.sh builds a number of packages that are not in the lsst_distrib product, the os level dependencies for these other products need to be determined.  In addition, the current version of lsstswBuild.sh and related scripts on lsst-dev are not version controlled.
Answer: 1415.0

User story: On the main page for the JIRA DM project, there is a sidebar, and on that sidebar the "Agile" link (which a naive outsider might easily click on):  https://jira.lsstcorp.org/browse/DM?selectedTab=com.pyxis.greenhopper.jira:greenhopper-project-panel-tab  points to something very outdated and potentially misleading.  Suggest removing the link, or redefining it to point to a reasonable default Agile board.
Answer: 510582.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 stray component in the DM JIRA project, with the name "start to outline an expandable Python framework for advanced users".  Presumably this was created when someone typed an issue title into the component field, perhaps when DM-1906 was created.  Can it be removed from the components list?
Answer: 26.0

User story: "We should quickly revisit if flask is the right choice for us.  Related: reportedly, our simple flask-based webserver is using more CPU in an idle state than expected. It might be useful to profile things, and look into that. "
Answer: 17561.0

User story: "While the new RGB code looks like it's just calling NumPy, NumPy is actually delegating to matplotlib under the hood when it writes RGB(A) arrays.  It also turns out that code is broken in matplotlib prior to 1.3.1 (though that shouldn't be a problem for anyone but those who - like me - are trying to use slightly older system Python packages).  I think think this means we should add an optional dependency on matplotlib to the afw table file, and condition the running of the test code on matplotlib's presence (and, ideally, having the right version).  I'm happy to do this myself (since I'm probably the only one affected by it right now)."
Answer: 5704.0

User story: "It currently takes already created Db object, it should take **kwargs and create it when needed."
Answer: 101.0

User story: "Supply the hardware resources needed at NCSA for short term development. It is captured in DM-2327  "
Answer: 8.0

User story: "Participate in the design discussions three times weekly for two to three months. "
Answer: 69252.0

User story: "Participate in the design discussions three times weekly for two to three months. "
Answer: 69252.0

User story: "Participate  in the design discussions three times weekly for two to three months. "
Answer: 69253.0

User story: "Add unit tests, also improve variable names as suggested by K-T in comments in DM-2139"
Answer: 1925.0

User story: "These SWIG macros return a class instead of raising an exception instance when the equality operation fails."
Answer: 11047.0

User story: "See RFC-32 "
Answer: 3350.0

User story: "IN2P3 sysadmin won't manage Qserv through puppet. So Qserv team has to provide ssh scripts to do this.  "
Answer: 55627.0

User story: "In support of an SDRP-based science talk of <USER> we spent some cycles gathering/summarizing processing middleware results and metrics from the US side of processing of the Split DRP.  This information from notes, logs, databases, etc provided contextual information on the processing campaign that produced the SDRP science results. "
Answer: 110917.0

User story: "We install and configure iRODS servers (an ICAT server, a resource server, a client host) in docker and make images, pushing the results to a docker hub repository. "
Answer: 141268.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: "We begin an examination of iRODS for managing data collections. We perform initial testing using resources available on NCSA's ISL OpenStack.  To mock up a zone or 'data grid' managed by iRODS, we set up an ICAT server, a resource server (this is a data storage resource that does not run the central database), and a client host. "
Answer: 50438.0

User story: "The qserv code is still using the old ssi scheme for the cmsd, this needs to be rewritten. For  details, see  https://listserv.slac.stanford.edu/cgi-bin/wa?A1=ind1503&L=QSERV-L#3"
Answer: 325748.0

User story: This file is long obsolete; marked as "remove this once ticket branch #1642 is done". [The corresponding ticket|https://dev.lsstcorp.org/trac/ticket/1642] predates JIRA and was marked as done 3 years ago.
Answer: 443.0

User story: "finalize job descriptions. Meet with kantor additional hour of  orientation for the ISO. group meeting  Misc."
Answer: 6153.0

User story: "reviewed the data center in a  box, recovered consultant's name prior to drafting a SOW."
Answer: 6149.0

User story: Xiuqin's 'short term' version: 1 VM - SUI build server 4GB memory and 200GB hard disk should be good enough. 1 VM - Apache server as a proxy and web front end 4GB memory and 100GB hard disk should be enough port 80 accessible from outside 2 VMs - Tomcat servers each has 16GB memory, access to 1TB of shared hard disk Port 8080 should be open for Apache server to access Port 8009 should be open to each other so they can replicate cache. (First 2 VMs are not absolutely needed. We can always use one of the hosts in number 3 to do build and host Apache server.)  The 2 Tomcat servers are larger than we can currently support as VMs.   We've discussed repurposing 2 of the older LSST "cluster/condor" nodes (e.g. lsst14 & lsst15) for this purpose.  But, ideally these could be implemented with the new vSphere hardware if the timeframe works.
Answer: 136748.0

User story: "Why needed? For SUI. To gain experience with running continuously. What is needed?    1/2 year: 4 VM, 8 cores, 16 GB RAM, 2 TB local storage, sudo to serve DC_W13_Stripe82 or equivalent   ~2 year time frame: 8-16 VMs, each: 8 cores, 16 GB RAM, 2 TB local storage, sudo    could go to much higher numbers (even like 50-100 VMs) if we have funding and if SUI would really find it useful. When needed soon Typical usage: 24x7 Qserv service for SUI"
Answer: 542925.0

User story: "Webserv as a service Why needed? For SUI. To gain experience with running continuously. What is needed? 1 VM: 4 cores, 8 GB RAM, small local storage, access to ncsa /nfs When needed: ASAP Typical usage: running webserv and DataCat as a service, continuously"
Answer: 542927.0

User story: "Revisit db/python/lsst/db/exception.py. Perhaps get rid of the numbers."
Answer: 279241.0

User story: "rproc::TableMerger seems to be replaced with rproc::InfileMerger, so this class could certainly be removed easily. "
Answer: 531398.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: h4. Short version:  Clarify what existing community practices, notably including VO interfaces, appear to rely on the availability of unauthenticated access to information in astronomical archives.  h4. Details:  At the February DM All Hands, [~<USER> raised an objection when it was mentioned that there is a presumption that all user access to LSST data through the DM interfaces (as opposed to through EPO) will be authenticated.  We don't appear to have ever documented an explicit requirement that all access be authenticated.  The basic controlling requirement is OSS-REQ-0176, "The LSST Data Management System shall provide open access to all LSST Level 1 and Level 2 Data Products, as defined in the LSST System Requirements and herein, in accordance with LSSTC Board approved policies. ...", which was a carefully crafted indirection at a time when the policy for non-US/Chile access was still being developed.  However, this presumption has been around for a long time.  It is inherent to the project policy that access to the non-Alert data will be limited to individuals who are entitled to it.  No matter what we think the final policy might be, we do have to design a system that can be consistent with this policy.  [~<USER> stated that the astronomical community relies on certain types of data and metadata - she mentioned coverage maps, among others - being available through unauthenticated interfaces.  This ticket is to ask her (and others) to collect documentation of those existing practices, so that we can figure out what the expectations may be and how to respond to them in our design.
Answer: 1157592.0

User story: "This would allow Qserv no to send the first protobuf header as a xrootd in-band message, and save some resources (network and CPU due to xrootd/TCP/IP encapsulation)"
Answer: 298518.0

User story: "The quick-start documentation for developers still points to the old git repositories. The RST document needs to be updated to the GitHub repos."
Answer: 16978.0

User story: The metaserv should be able to support databases for which we don't have the ascii schema with descriptions and special tokens (ucd, units etc). This story involves implementing it. In practice, the metaserv/bin/metaBackend will need to be extended to implement "ADD DB"
Answer: 1553691.0

User story: "Revisit whether we need something better than a very basic db connection pool.    It may be worth looking at http://docs.sqlalchemy.org/en/rel_0_9/core/pooling.html (or even sqlalchemy in general). Note the Pooling Plain DB-API Connections section - one can use sqlalchemy pooling independently of the other library features.    Separate utilities like createDb(), dbExists() and such from core part that deals with connections / sqalchemy."
Answer: 283409.0

User story: "begin orientation of LSST ISO ALEX Withers. "
Answer: 9704.0

User story: "Begin  comprehensive review of the WBS.   Forced on overall framework and begin  workflow systems  "
Answer: 57.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: "arrage for presentations next week w.r.t commercial object store.  The vendor in question is know to NCSA and has claims to have produced a commercial object store having both NFS,  GPFS  and swift interfaces. "
Answer: 61.0

User story: "Participate and guide the SUI design process, generate charts and documents as appropriate"
Answer: 33353.0

User story: "Switch to using the db connection pool. Note, in addition to getting auto-reconnect, in metaserv that would handy if we need to talk to multiple database servers simultaneously."
Answer: 18949.0

User story: "Implement a class that manages a connection pool, and optionally, if configured, restarts connection as needed in case of timeout."
Answer: 5890.0

User story: "Form is here: https://www.jetbrains.com/eforms/openSourceRequest.action?licenseRequest=PCP05NS  LSST release info is here: https://www.jetbrains.com/eforms/openSourceRequest.action?licenseRequest=PCP05NS"
Answer: 2085025.0

User story: "Work with the OCS DDS software so that we can get it integrated with the DM stack applications.    The OCS team will be here sometime over summer 2015 to help us understand the requirements for the DDS software so we can do this."
Answer: 1038584.0

User story: "Write white paper on the evaluation of complex event processing packages."
Answer: 1090067.0

User story: "We need to do a survey of complex event processing software packages including Esper, our own ctrl_evmon package, and other CEP packages we can find."
Answer: 1090068.0

User story: RFC-27 is an example that was posted to both "DM" and "LSST" as components.
Answer: 2317259.0

User story: "We anticipate being able to move from the VMs that we currently use to using docker.  This will require some coordination with <USER>to see how HTCondor is configured.  "
Answer: 555668.0

User story: "Create file transfer API so we can easily test different types of file transfer mechanisms to/from the AP."
Answer: 123668.0

User story: "Currently this is generated by the replicator and sent to the distributor.  The idea where is to put the API in place so that the data will be transferred from outside of the replicator to it, and then passed on."
Answer: 119459.0

User story: "Implement the mechanisms to send DDS messages back to the OCS from the AP system. "
Answer: 988837.0

User story: "The OCS software will be arriving sometime over the summer,and we need to integrate it with the simulator."
Answer: 233033.0

User story: "The initial prototype of the AP simulator needs to be refactored to improve how tasks are handled by the components for further development."
Answer: 81799.0

User story: "AP requires that jobs are handed off to different worker job clusters as the previous set of images is being worked on."
Answer: 282132.0

User story: "Create long-running jobs to reduce the startup time for new HTCondor jobs.   This can be implemented as a parent/child, or as a on_exit_remove=false directive in HTCondor.  I suspect it will be a combination of the two."
Answer: 258778.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 accounts - update umask on stack  to each account - provide easy ssh config if possible - setup up build procedure (each developer can build Qserv using tag git and 'git' version is set up by default on all the Qserv if ti exists)"
Answer: 91927.0

User story: "xrootd lib/ directory should be s relative symlink to lib64, no a full path link."
Answer: 12810.0

User story: "We want to have a out of box build for users of Firefly package. It will include a simple Firefly viewer. "
Answer: 60155.0

User story: In addition to numpy and scipy, ngmix depends on the emcee and statsmodel packages.  While it can build without them, we probably want the full functionality.  I also see some undeclared dependencies on the "esutil" and "fitsio" packages (all from esheldon's GitHub), and there may be a few more dependencies on some of his own packages.    This issue includes creating a third-party build for ngmix itself.
Answer: 605188.0

User story: "We need some common fields for star/galaxy classifiers so they can participate in a slots-like mechanism once we have several of them.  Most of these can produce a floating point number between 0 and 1 (but sometimes it's not limited to that range), and it's rarely a true probability.  We may want to make a boolean that results from a threshold on these be the common interface, but we don't necessarily want to hard-code such a threshold into the processing either - especially when we could also use a FunctorKey to get a boolean from the floating point value."
Answer: 2086848.0

User story: "The new SExtractor star/galaxy classifier, SPREAD_MODEL, is popular with everyone who has tried it, and should be simple to implement by building on code in meas_modelfit.  See definition and discussion here: http://arxiv.org/abs/1306.4446"
Answer: 2086850.0

User story: " Prototype an environment that allows automatic   - Provisioning of a VM for a certain OS - Install the Stack prerequisites for that OS - Build the stack via newinstall.sh from the production server - Run integration tests (in the curent case the sdss test  https://github.com/lsst-sqre/sandbox-stackbuild"
Answer: 4.0

User story: "New wokflow for Sims Merge of Opsim and CATsim New workflow for PST "
Answer: 1757166.0

User story: "DM's transition for code repositories to Github is complete.  Outstanding are data repositories; a cleanup of contrib/externals; and supporting the Stash move. "
Answer: 1.0

User story: " We have  1. Obtain a dedicated colo OSX server  2. Have done some testing using the SQuaRE vagrant-sandbox harness  It is therefore a plausible avenue forward to do at least a nightly build/deploy/intgeration-test on OSX pending more extensive arrangements requiring purchase of hardware.  "
Answer: 244432.0

User story: "Extend API to expose cursor. This was brought up by Andy in DM-2137. "
Answer: 22610.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: "SUI needs to serve raw data to the user community. We want to understand the use cases and definition of raw data. More specifically, what meta data will be available in the FITS file that we call raw image? "
Answer: 1172186.0

User story: "- Researched how to monitor network drops, errors, etc <https://jira.ncsa.illinois.edu/browse/LSST-641> - Opened up SUI ports on lsst-dev <https://jira.ncsa.illinois.edu/browse/LSST-651> - Moved /nfs/admin/ to /condo/admin/ - Review of EL 6.x kernel security patch - Fixed jumbo frame issues, primarily with old VMs that needed new version of NIC <https://jira.ncsa.illinois.edu/browse/LSST-652>"
Answer: 80483.0

User story: "- researched buildbot slowness on lsst-dev <https://jira.lsstcorp.org/browse/DM-2388> - researched buildbot slowness on lsst-dev <https://jira.ncsa.illinois.edu/browse/LSST-638>"
Answer: 50249.0

User story: "- lsst-dbdev2 drive failure (https://jira.ncsa.illinois.edu/browse/LSST-636) - account for <USER>(https://jira.ncsa.illinois.edu/browse/LSST-634) - disable Robyn Allsman's accounts (https://jira.ncsa.illinois.edu/browse/LSST-623)"
Answer: 40221.0

User story: "- crashplan issue with lsst-netem (https://jira.ncsa.illinois.edu/browse/LSST-633) - yum/glibc issue with lsst-dbdev1 (https://jira.ncsa.illinois.edu/browse/LSST-631) - account for Jacques Sebag (https://jira.ncsa.illinois.edu/browse/LSST-624)"
Answer: 40225.0

User story: "- backup issues with lsst-stor141 (https://jira.ncsa.illinois.edu/browse/LSST-632) - setup jumbo frames on lsst-xfer (https://jira.ncsa.illinois.edu/browse/LSST-628) - crashplan reconfig on lsst-xfer (https://jira.ncsa.illinois.edu/browse/LSST-629)"
Answer: 40229.0

User story: "In order to allow for on-the-fly Task creation of dataset types, the essentials of each type need to be encapsulated in code.  That code should be reused across all similar dataset types, and there are opportunities for inheritance and specialization, particularly in cases like simple file-oriented mappers.  Investigate this by prototyping a number of possibilities."
Answer: 2.0

User story: "[~<USER> -- After finishing the measurement work, your next priority is to get started on DM-1108. However, the stories you have been assigned there are currently too big for useful scheduling (20-30 SPs is a mini-epic; we're looking for less than 10 SPs per story). The first task therefore is to work with [~<USER>, and others if required, to break them down and come up with a set of stories which usefully reflect the work which needs to be done."
Answer: 86670.0

User story: "This will require a new task, so will require a new interface and associated RFCs.  The interface should take an arbitrarily large stack of catalogs with or without a reference catalog.  It should return a stack ow WCSs that map from the individual coordinate systems to the reference."
Answer: 489913.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: "We'll need a reference set of data to work against.  This could be SDSS, CFHT, or simulated.  Should be 10? epochs with realistic atmospheric conditions taken at similar airmass and hour angle.  Single band is fine for now."
Answer: 489916.0

User story: "Add typemaps so that we can use numpy scalars to call C++ functions that take plain old scalar types (e.g. float, double or int). At present attempting to pass numpy scalars will fail unless the type is one of a restricted subset, e.g. float and numpy.float64 succeed but numpy.float32 is rejected as being an incompatible type, and similarly for integer types."
Answer: 58633.0

User story: (Original problem discovered by [~<USER>)  Now that the packages for external products are on GitHub, it would be nice for them to contain files like the near-standard "README.md".  Unfortunately, {{eupspkg.sh}}'s {{default_prep}} command explicitly inspects tarball-and-patch (TaP) packages to make sure there are no other files in the package root directory.  I think this is a little excessive.  There's a bypass if the environment variable {{TAP_PACKAGE}} is set, but the package's table file has not yet been setup, so it's not possible to set this variable there.  (The comments for the {{default_prep}} command suggest that the dependencies have been setup, but it's not clear that this is necessarily the case if invoked by {{lsst-build}}.)  I suggest that we check instead for a {{./.tap_package}} file to indicate definitively that this is a TaP package.
Answer: 3683.0

User story: "See https://confluence.lsstcorp.org/display/DM/Qserv+Release+Procedure for recipe. "
Answer: 48591.0

User story: "we are adding sncosmo as an external package in the stack.  We need to edit lsstsw/etc/repos.yaml to point to the correct repository"
Answer: 2092309.0

User story: "We want to create a new frame work for entering data for forms and dialogs. This is in javascript based on React.js.  This is the first step in our javascript conversion."
Answer: 13235.0

User story: "There may be some discrepancy between the pixel units being passed to distest.cc compared to what it is expecting (units of pixels).  This needs to be investigated further and remedied in such a way that all other representations (e.g. in camera.py) are consistent with the other obs_XXX representations."
Answer: 197567.0

User story: "We often want to compare two WCS for approximate equality. afw/image/testUtils has similar functions to compare images and masks and I would like to add one for WCS    This ended up being expanded to adding functions for many afw classes (not yet including image-like classes, though existing functions in image/testUtils for that purpose should probably be wrapped or rewritten on a different ticket)"
Answer: 152420.0

User story: "Provide standard calibration transformations for each of shape, flux and centroid and make sure they are returned as the default transformation for all algorithms measuring those quantities."
Answer: 63289.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "DM-1903 provided a command line task which would transform a {{src}} catalogue into calibrated form. Here, we build on that to provide command line tasks for all source catalogues which will need to be ingested; will include at least {{deepCoadd_src}}, {{goodSeeingCoadd_src}}, {{chiSquaredCoadd_src}}."
Answer: 138382.0

User story: Vaikunth had some "expected" troubles playing with data loader options for his DM-1570 ticket. Main issue I believe is the absence of the documented use cases and their corresponding data loader options. I'll try to add a bunch of common use cases to RST documentation and also verify that all options behave as expected.
Answer: 11503.0

User story: "Need to come up with a plan which data set we will use for large scale tests, and how we will produce it."
Answer: 89177.0

User story: "DM-1576 provides a new astrometry solver and a new schema for reference objects. However, the old astrometry.net astrometry solver still uses the old schema. It would be wise to convert the old solver to the new schema so that the match list returned by it is in standard format."
Answer: 70807.0

User story: "Remove all astrometry.net wrapper code from {{meas_astrom}} and put it in a new package named {{meas_extensions_astrometryNet}}.  "
Answer: 1140231.0

User story: "DM-1576 changes the default astrometry task, which changes some config overrides for astrometry. Examine the config overrides in the obs_ packages for outdated fields."
Answer: 20069.0

User story: "Database access should use lsst/Db for all database access."
Answer: 303897.0

User story: "Migrating qserv to the new c++ geometry API required porting a fair amount of code from the python layer and updating the plumbing in the czar. During implementation, the sphgeom was in the process of finding a home, so the sg code was temporarily placed under core/modules.  This ticket covers: * removing core/modules/sg * updating code to point at the external sphgeom * updating build-logic to properly depend on and link with external sphgeom."
Answer: 460813.0

User story: "In the port to the new Xrootd Ssi API, worker-side squashing was lost in the shuffle. The plumbing is different, and re-implementing squash functionality is not entirely straightforward, especially because the new API is still missing documentation and examples for implementing cancellation.  The consequences of not implementing this are minor--some extra work may be done by the worker, but not a whole lot, because user-level cancellation has not been implemented."
Answer: 51637.0

User story: "We need to replace direct worker-mysql communication and other administrative channels with a special service which will control all worker communication. Some light-weight service running alongside other worker  servers, probably HTTP-based. Data loading, start/stop should be handled by this service."
Answer: 45042.0