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: "We need a way to get back the noise-replaced Exposure as it was when a particular source was measurement, after the measurement has been run, without having to run noise-replacement on all the previous objects again.  There is already code in afw::math::Random to output its state as a string; I think we should probably just save this string in the output catalog.  This will require some API changes to allow the NoiseReplacer to modify the schema and set a field in the output records."
Answer: 440532.0

User story: "Add a Reader object to handle messages in HTCondor logs.    This would require having the Reader translate multiple message types (see ctrl_stats).  This would also require interfacing the mechanism HTCondor uses to read these files, since HTCondor logs roll over from one file to the next.  We really shouldn't try to roll our own code to read those logs ourselves."
Answer: 1058401.0

User story: Messages trapped by Conditionals are automatically assigned the name "$msg", and can be referred to as "$msg[1]" or "$msg[2]", depending on which Conditional in the chain trapped the message.   This is an artifact of the way the declarative objects were named in the Chain sequence.  One suggestion might be to have an Assignment object and allows messages to be signed whatever name we want.     A better solution would be to see if they can be just assigned directly to variables, but this only would work if there's a re-write in Python.
Answer: 1058407.0

User story: "Add FunctorKeys for simple, common, calculated fields, including:  - Magnitudes from fluxes  - Coords from Points, Points from Coords  - Ellipse conversions and radius/ellipticity extraction"
Answer: 2551563.0

User story: "Add more FunctorKeys to replace the functionality in all current compound field types and meas_base result objects.  May involve moving some meas_base definitions to afw."
Answer: 382038.0

User story: "Add the basic FunctorKeys mechanism, and enough implementations to support Slots."
Answer: 19112.0

User story: "Add the ability to take events from multiple sources simultaneously. Those sources could be from the same source type (DM Events/Messages, but different topics), or completely different sources, working together"
Answer: 1058423.0

User story: "This issue picks up the partially-completed Trac Ticket #2351, which adds a string-substitution-based alias mechanism to afw::table::Schema. There are still some issues to sort out w.r.t. constness - in other respects, a Table or Catalog's schema cannot be changed once the Table has been constructed, but we do need to be able to change aliases after table construction."
Answer: 135594.0

User story: "Currently written in Java with the API exposed in a Jython interface. It would be better to re-write this in Python in order to take advantage of Python packages that Jython doesn’t support.   Moving to pure Python would also allow for the interfaces to be simplified, which would make scripts easier to write."
Answer: 1058426.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: "Simulate jobs which do alert processing.  Produce VOEvents based on those results."
Answer: 211539.0

User story: "Qserv services init.d scripts have to rely on LSB, in order to work on multiple systems.  Remark : xrootd has to be launched as a background process (i.e. with a & at the end). But this always send of return code equal to 0, even if xrootd fails to start, a shell function wait_for_pid will be implemented in xrootd init.d scritps to solve that (inspired from mysqld init.d script)."
Answer: 24449.0

User story: "The HTCondor local configuration files are only on the systems they operate on.  They should be in a git repository so we can track changes. "
Answer: 3090808.0

User story: "The ActiveMQ configuration files which are changed from the standard ActiveMQ download are only on the system itself.  They should be in a git repository so we can track changes.   "
Answer: 1568162.0

User story: "It would be worth while to investigate the best way to check on status of running jobs during HTCondor processing.  There are some tools to do this within Pegasus, and if we intend to use it, they would be useful, but it still needs to be investigated.  During a previous Data Challenge, we were able to tap into the job office by observing the DM Messages (ctrl_events) that were being sent while it operated.  We were able to use this to build a web page display of processing while it happened.  This was very useful because were able to observe jobs and submissions directly, and see that things were either working, failing, or taking to long to process.   Without this, we had to go through the log/output files by hand before realizing things were going sideways. "
Answer: 2634914.0

User story: "This is described in LDM-230, section 2.3.3.  Includes: preloading the template image, master calibration images, DIAObjects DIASources, and SSObjects;  retrieving both sets of crosstalk-corrected pixels and associated telemetry/metadata. "
Answer: 217248.0

User story: "This is described in LDM-230, sections 2.3.2 and 2.3.3, including accepting distributor publications of which rafts/CCDs it owns, and replying to worker requests for CCDs."
Answer: 27210.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: "Distributor  On boot:  * Checks the network, archive raw image cache and the tape archive.  After all have tested successfully, the distributor waits for a connection from its associated replicator.  In operation:  * On receipt of a visit id, exposure sequence number and raft id from its associated replicator, the distributor publishes them along with its network address to the Archive DMCS.  On receipt of crosstalk-corrected image and associated telemetry from its associated replicator:  * Verifies integrity using a hash or checksum * Writes to the raw image cache using the Data Access Client Framework * Decompresses (if necessary) * Separates into individual CCD-sized portions * Sends portions to the appropriate connected Workers  Note: Workers can connect to request a CCD-sized crosstalk-corrected image.  On receipt of raw image:  * Writes it to the tape system. * All images are tagged with the Archive mode.   Should include heartbeat monitoring of the replicator/distributor connection."
Answer: 197285.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: "Replicator  On boot:  * Establishes connection with single, pre-configured distributor. * Checks connection with the network outage buffer, the Base raw image cache, and the tape archive.  On success, the replicator registers itself with the Orchestration Manager in the fully-operational pool.  From K-T: Note that what to check should eventually be dependent on what was specified in the configuration.   That way, if the tape library is down, we could still run using the network outage buffer or raw image cache as the redundancy source.  In operation:  * Receives a job with visit id, exposure sequence number within the visit and raft id. * Queries the Base EFD replica for information needed to process the image. * Subscribes to the Camera Data System (CDS) “startReadout” event and to the OCS telemetry topics. * Waits for a startReadout event * Request the cross-talk corrected exposure for the raft using the CDS client interface and block until it is available.  On receipt of crosstalk-corrected image:  * Verify integrity of image (hash or checksum) * Send image with telemetry to the distributor, compressing it if the configuration says to do so.  At the same time, the image is written to the network outage buffer and the raw image cache using the Data Access Client Framework, retrying until successful for a configured number of tries. All images that are written are tagged with the Archiver mode (by the replicator job).  * Request the raw image using the CDS client interface and block until it is available.  On receipt of the raw image:  * Verify integrity of image (hash or checksum) * Send image to the distributor and simultaneously write to the network outage buffer and the tape archive.  ALL image transmission statuses (successful and unsuccessful) are recorded to the Alert Production Database.  NOTE:  Image some calibration or engineering modes, there may only be raw-image data, not crosstalk-corrected image data.  The replicator job configuration will provide for this).  NOTE: Replicator jobs will need to detect they are not completing in the expected amount of time.  NOTE: Something (the Base DMCS?  The Event/Message Monitor?) needs to pay attention to the number of replicator re-registering themselves with the local-only pool and notify NetOps to investigate and resolve the issue.  On errors sending or keeping connected to the distributor, the replicator: * unregisters from the “fully-operational” pool * registers with the “local-only” pool  The replicator will continue to try and connect to the distributor, and if it is able to reestablish the connection: * unregisters from the “local-only” pool * registers with the “fully-operational” pool  Heartbeat messages between replicators and distributors will indicate when the replicators will be able to re-register with the fully-operational pool."
Answer: 197286.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 library to be used by each commandable entity and the Base DMCS.   Methods in this library receiving commands from the simulated OCS. Specific command actions will be handled by each entity, and events are handled by the Base DMCS.  This will initially be developed using DM messages, and later switched to use the DDS.  The library will include:  * An object with methods for blocking receives, blocking receives with timeouts, and non-blocking receives.  Any commands received by these methods are given to another class to call appropriate action methods. * An abstract class implementing each of the following methods for commands: init, configure, enable, disable, release, stop, abort, reset. * An abstract class with methods for implementing the following methods for events:  startIntegration and nextVisit"
Answer: 197283.0

User story: "Simulate the OCS and CCS (via the OCS) sending message to the Base DMCS.  Write a library to send commands via method calls, which will be used by commandable  entities and by the Base DMCS.  The method calls in this library will be used to simulate sending commands from the OCS.  This will initially be developed using DM messages, and later switched to use DDS.  Write a command line tool to send these messages.  Commands with no arguments: init, enable, disable, release, stop, abort, reset.  Commands with arguments: configure - arguments are: Set of computers, software and versions to be executed, parameters used to control that software.  Events with arguments: startIntegration, nextVisit.  Definition of done:  * A library that has method calls to each of these commands/events.  Each method call sends one message to the given Topic. * Command line tool that can send any of these commands/events to a commandable entity subscribed to a Topic. * Unit tests for each of the commands/events"
Answer: 197285.0

User story: "Add version to afw::table::SourceTable.  Persist that version number to fits file when the table is saved, and restore when the table is restored.  Tables created and saved to disk prior to this modification will have the version number 0, by default.  Tables created with the S14 version will have the version number 1.    This change is to enable a new version of slots and field naming conventions as needed by the Measurement Framework overhaul, at the same time allowing current clients of SourceTable to continue to function.  The work to define and persist the slots depending on the version will be on a separate issue.  Should not appear as an alterable member of the metadata, but should be saved with the metadata and reloaded when the file is reloaded.  getVersion and setVersion methods will be used to allow clients to alter this number."
Answer: 15672.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 ActiveMQ broker doesn't automatically expire topics once they're created.  When running the ctrl_events tests, topics are created that are guaranteed to be only used once, so that simultaneous tests don't send messages to each other's topics.  This doesn't really have an impact in most cases, but if the ActiveMQ broker is up for a very long time, the number of topics will continue to increase.  In recent versions of ActiveMQ, this is a configurable.   Topics that haven't been used (meaning, no clients for that topic) for a certain length of time can automatically be deleted."
Answer: 261641.0

User story: "I wonder if we could catch more exceptions in czar to simplify debugging. For example, if I change: {code} --- a/core/modules/czar/lsst/qserv/master/app.py +++ b/core/modules/czar/lsst/qserv/master/app.py @@ -418,7 +418,7 @@ class InbandQueryAction:                     self.constraints.size())          dominantDb = getDominantDb(self.sessionId)          dbStriping = getDbStriping(self.sessionId) -        if (dbStriping.stripes < 1) or (dbStriping.subStripes < 1): +        if (dbStriping.x < 1) or (dbStriping.y < 1): {code}  It will return to client a very cryptic error: {code} Qserv error: Unexpected error: (<type 'exceptions.AttributeError'>, AttributeError('x',), <traceback object at 0x969a02c>) {code}  with no other clues, traceback or information in the log. "
Answer: 936317.0

User story: "5 tests fail in the testCppParser."
Answer: 62245.0

User story: "Need to improve how defaults are handled in qserv_admin. There seems to be some desire to warn when values are not set--how about setting defaults and just printing what configuration is being used? If this is something human-created, we should have reasonable defaults and not bother the user, unless no default is viable. I think we should only be strict on machine-generated input, where we would like to catch bugs as soon as possible.   (This came up in the review of DM-56, the review comments are captured in DM-225)"
Answer: 415511.0

User story: "CSS has one class for all exceptions. The model adopted by Daniel (each type as a separate exception) is better, as we can catch individual exceptions  instead of (a) having to catch all css exceptions, (b) checking type and (c) rethrowing if it is not the type we want. To be able to catch all CSS exceptions, we can just introduce a new base class (that is new comparing to Daniel's version)."
Answer: 34089.0

User story: " Here's <USER>remark, during #3100 review : https://dev.lsstcorp.org/trac/ticket/3100#comment:18"
Answer: 179188.0

User story: "A qserv-integration-tests package should be created : - it would allow to manage easily, in ups/qserv.table, tests version for a given Qserv version. - it would allow to install Qserv dependencies related to testing, like partition (and other data ingest code which may arrive."
Answer: 68714.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "With the transition to the new distserver, we've stopped building the GPU-accelerated code, because we don't package the cuda_toolkit and cuda_sdk dependencies. Those should be turned into EupsPkg packages (and git repositories!), and re-enabled (by removing them from exclusions.txt in lsstsw.git)."
Answer: 1587303.0

User story: "hubot: http://hubot.github.com errbot: http://gbin.github.io/err/  Others: http://help.hipchat.com/knowledgebase/articles/64359-running-a-hipchat-bot"
Answer: 472626.0

User story: "The latest LSST Software User Guide contains installation instructions for both v7.3 of the stack, and also v8.0 (just released). The instructions for v7.3 should be made less prominent, although they are still useful until:  1) the binaries are published for v8.0 2) all supported cameras have been updated to use the new CameraGeom (to be released in v8.1)  The eventual procedure will be to publish new versions of the SwUG for each release of the LSST Stack. "
Answer: 1404440.0

User story: "The current example in the LSST Software User Guide for co-addition reflects the processes necessary to perform a DR production. While thorough, it only really works on the lsst cluster. The example should be simplified to work on a smaller subset of data, and on single-user machines.  Definition of Done: * Following the documentation, it will be possible for users to identify the SDSS data they need (the subset of files) * There will be instructions on how to download the necessary files to their local machine * There will be instructions on how to build the necessary repositories * There will be instructions on how to run the Co-Add+forced photometry tasks.  * Any issues requiring access rights to LSST machines or databases will be identified and issues created for later."
Answer: 41509.0

User story: "As DECam data will be one of the precursor data sets used to assess the quality of LSST code, we need this module in LSST-controlled repositories."
Answer: 858201.0

User story: "It should be easy for an end-user to use obs_file to perform photometry and astrometry on an image that's had its signature removed."
Answer: 1019571.0

User story: "Done in DM-366"
Answer: 60179.0

User story: A regular expression bug in afw::table FITS reading gets in the way of loading FITS binary tables with columns that do not include the optional "repeat count" in the TFORM keyword.  In other words, we can't read fields that have FITS headers with e.g.: {code} TFORM: "K       " {code} instead of  {code} TFORM: "1K      " {code}  CFITSIO apparently always does the latter, which is why we've never seen this bug before, but both are valid FITS.
Answer: 31672.0

User story: "Remove obsolete strToDoubleFunc (and more) in util/stringUtil.h."
Answer: 50924.0

User story: Reported by Andy when reviewing DM-296. Discussed at Qserv mtg 3/27.   boost::shared_ptr =(new T())" --> boost::make_shared()
Answer: 377159.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: Suggested by Andy when reviewing DM-296, discussed at Qserv mtg 3/27.  std::list --> std::vector  * why? Default now is vector, iterating over vector is much more efficient than over list  * revisit on case by case bases, do not blindly replace  * preferred solution: typedef, and name it in a way that conveys the intent (e.g., might call it a "container"), underneath use vector
Answer: 473928.0

User story: "It'd be very useful to have fully functioning Qserv release with the latest set of changes (build, packaging, CSS, Daniel's fixes etc) during the Hackathon week."
Answer: 50718.0

User story: "<USER>reported he's had to switch off hyperthreading and manually override NCORES, MAKEFLAGS and SCONFLAGS because his 8-core machine had too little RAM to build afw with -j 8.  To fix this, eupspkg default build routines should take RAM into account when computing the level of build parallelism.  In the meantime, we should document the workaround (contact <EMAIL>)."
Answer: 2580332.0

User story: "Clean up the way modules are imported in qserv master, use relative import when appropriate instead of lsst.qserv.master.<package>   (migrated from Trac #2369)"
Answer: 486861.0

User story: "The mess of thread.cc and dispatcher.cc need to be re-thought and re-designed so that the interface is smaller and more obvious.  "
Answer: 225102.0

User story: "I tried compiling a list of everyone who works or has worked on the DM code -- it was nearly impossible. We should have a (public) list both of current staff and our alumni (and where they are now)."
Answer: 1161251.0

User story: "CSS should gracefully recover from failures such as lost connection to mysqld or zookeeper. It is not clear if it would survive such glitches right now -- this needs to be tested and the code improved as necessary."
Answer: 314244.0

User story: "Includes need cleanup: group into standard lib, boots and local, sort as appropriate etc. Also, unify forward declarations."
Answer: 70594.0

User story: "Currently CSS is using one class and relies on different error codes to differentiate between different type of exceptions, while other parts of Qserv core define an exception for each different error. It'd be good to standardize and use the same approach. "
Answer: 12044.0

User story: "Jira setup for Qserv, includes things like adding new tasks, transferring tasks from trac, epic/story/task division, assigning story points, setting scrum board, just learning things and more..."
Answer: 46229.0

User story: "{{lsst.daf.base.DateTime}} has a Python {{\_\_eq__()}} method, but it doesn't have a C++ {{operator==()}} method.  There doesn't seem to be a good reason for this."
Answer: 614.0

User story: "Ingest code may be useful for LSST Stack users but shouldn't require things like the orchestration software.  Package it by itself, and perhaps push it (and its dependencies, likely including {{cat}}), down from {{datarel}} and {{lsst_distrib}} into {{lsst_apps}}."
Answer: 890720.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: All classes in sql module start with sql. All classes in mysql module starts with mysql... except the sqlConfig class. I find it very confusing, and I'm going to add "missing" "my" in front, unless someone (Daniel?) has strong objections.
Answer: 47003.0

User story: "Restaring mysqld results in unusable qserv (even if the restart happens when qserv is completely idle). The error message is:  ERROR 2013 (HY000): Lost connection to MySQL server during query This happens most likely because qserv caches the connection, which becomes invalid when server is restarted. I am guessing the same will happen when there is a long period of inactivity (the connection times out).  (transferred from trac 2853)"
Answer: 23533.0

User story: "This was suggested by the code review for ticket 1945 (https://dev.lsstcorp.org/trac/wiki/SAT/CodeReviews/1945), pasted below:  common/src/*:  While it's not required by the coding standards, I'm a big proponent of using namespace scopes in .cc files, which usually save you from needing namespace aliases and will certainly save you from having prefix every declaration with qserv::.  At some point I'd recommend changing the header file extension from .hh to .h to match the rest of the LSST DM code, unless it's a big backwards compatibility issue.  (transferred from trac ticket 2528)"
Answer: 48809.0

User story: "I would like to write and compile query analyzer code completely independently of the parser and ANTLR (transitively). This doesn't seem to work right now. This is not currently possible.  This might take any where from a day to a week. (I'm not sure if we can finish anything in half a day, if you include the testing, review, feedback, and revision process, but perhaps unit testing will make that faster).  Updates to follow after the scope is estimated.  Dependencies to be broken: query --> parser, antlr (due to predicate depending on antlr nodes) qana --> parser, antlr "
Answer: 87761.0

User story: "I don't know where to file this.  Can someone point me in the right direction?  When I get auto logged out of Jira or Confluence, I click the login button to log back in.  As expected, a username/password box come up in that window.  When I type in my username and password, a brand new window (not tab) is opened with my authenticated session.  This is pretty annoying as it leave the username/password window open in the other tab.  I'm using Chrome (33.0.1750.117) on Scientific Linux 6."
Answer: 17701.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've been doing some minor work on the HSC-side ApertureFlux algorithm, and I wanted to record some concerns here (from both me and RHL) that should be addressed in the new meas_base version:  - We should consider merging ApertureFlux and EllipticalApertureFlux into the same algorithm (with a config field to choose whether to use elliptical apertures).  We could still register it twice, with a different default config value, and this should eliminate a lot of code duplication.  We could also consider having them inherit from a common base class (instead of having EllipticalApertureFlux inherit from ApertureFlux, as is done now).  - We should test that the threshold at which we switch from Sinc to naive apertures is obeyed exactly.  - We should create a flag for the failure mode in which an aperture cannot be measured because we go off the edge of the image, and test that it appears at the right point.  If possible, we should set this flag and measure what area we can within that aperture, instead of just bailing out.  - (Somewhat off-topic) We should consider having utility functions on SourceSlotConfig to set all slots to None for use in unit tests."
Answer: 447911.0

User story: "AsyncQueryManager is initialized based on configuration file, if the configuration is invalid, an exception should be thrown (eg in _readConfig()) and gracefully handled upstream."
Answer: 94635.0

User story: "Before we start populating the DM Confluence space with active pages, we should define an overall organizational structure/taxonomy."
Answer: 63335.0

User story: "Setup the Buildbot 0.8.8 testbed for the DM environment.  This includes: (1) setting up slaves on the set of common OS on which the DM stack runs; (2) creating a new continuous integration slave using the new eupsPkg-based build and distribution support,  Definition of done: * Every git change of master should trigger a build of master * If a build failed, an e-mail will be sent to lsst-data (if the build succeeds, nothing happens) * Failures due to internal buildbot issues (e.g., config problems, transient system availability issues, timeouts, etc.) should go to the buildbot owner. * Allow user-triggered builds via web page (with specified refs to be built), with a common user (until we get LSSTC LDAP directory hooked up). It's understood that locking may not be fully implemented/fleshed out in this story. * It should be possible for a user on lsst-dev to easily setup the stack for either a failed or a successful build. "
Answer: 224194.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: "Eups package astrometry_net_data co-opted the individual versions  to hold different unique datasets (i.e. not just different versions of the same dataset).  Currently the different datasets are not backed-up nor are they installed in git repositories so the loss of a dataset  thru misadventure or other failure requires the recreation of the dataset from whence it came.  This Issue should deal with setting up a failsafe archival mechanism.  Edit (by <USER>: As K-T points out in the first comment, this is true of all other test data sets. This issue is intended to cover the needed work for all of them."
Answer: 1604566.0

User story: We desperately need Python code highlighting.  "diff" highlighting would also be useful.  https://marketplace.atlassian.com/plugins/jira.plugin.syntaxhighlighter.macro.syntaxplugin
Answer: 18167.0

User story: On DM Software Development board, I propose we:  * Change "Ready to Merge" to "Review Complete". Per K-T:  {quote} That's what I thought "Review Complete" would be -- most of the work is done, but some fixups are needed before merging, and a re-review is not necessary.  {quote}  * Remove "Ready for Review". Instead, the developer should just drag the issue to "In Review" and assign it to a reviewer. If/when we re-instate the "review master", we may re-introduce "Ready for Review"
Answer: 19068.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: "-------- Original Message -------- Subject: [LSST-data] Swig 3.0 is out (with C++11 support) Date: Mon, 17 Mar 2014 08:26:05 -0400 From: <USER>the Good <<EMAIL>> To: LSST Data <<EMAIL>>  I tried a pre-release on os/x 10.7.5 and it failed some tests, but I haven't tried this version.  I had some discussion about this with William, but haven't had time to follow through.         R   > Date: Sun, 16 Mar 2014 22:44:42 +0000 > From: William S Fulton <<EMAIL>> >  > *** ANNOUNCE: SWIG 3.0.0 (16 Mar 2014) *** >  > http://www.swig.org >  > We're pleased to announce SWIG-3.0.0, the latest SWIG release. >  > What is SWIG? > ============= >  > SWIG is a software development tool that reads C/C++ header files and > generates the wrapper code needed to make C and C++ code accessible > from other programming languages including Perl, Python, Tcl, Ruby, > PHP, C#, Go, Java, Lua, Scheme (Guile, MzScheme, CHICKEN), D, Ocaml, > Pike, Modula-3, Octave, R, Common Lisp (CLISP, Allegro CL, CFFI, UFFI). > SWIG can also export its parse tree in the form of XML and Lisp > s-expressions.  Major applications of SWIG include generation of > scripting language extension modules, rapid prototyping, testing, > and user interface development for large C/C++ systems. >  > Availability > ============ > The release is available for download on Sourceforge at >  >      http://prdownloads.sourceforge.net/swig/swig-3.0.0.tar.gz >  > A Windows version is also available at >  >      http://prdownloads.sourceforge.net/swig/swigwin-3.0.0.zip >  > Please report problems with this release to the swig-devel mailing list, > details at http://www.swig.org/mail.html. >  > Release Notes > ============= > SWIG-3.0.0 summary: > - This is a major new release focusing primarily on C++ improvements. > - C++11 support added. Please see documentation for details of supported >   features: http://www.swig.org/Doc3.0/CPlusPlus11.html > - Nested class support added. This has been taken full advantage of in >   Java and C#. Other languages can use the nested classes, but require >   further work for a more natural integration into the target language. >   We urge folk knowledgeable in the other target languages to step >   forward and help with this effort. > - Lua: improved metatables and support for %nspace. > - Go 1.3 support added. > - Python import improvements including relative imports. > - Python 3.3 support completed. > - Perl director support added. > - C# .NET 2 support is now the minimum. Generated using statements are >   replaced by fully qualified names. > - Bug fixes and improvements to the following languages: >   C#, Go, Guile, Java, Lua, Perl, PHP, Python, Octave, R, Ruby, Tcl > - Various other bug fixes and improvements affecting all languages. > - Note that this release contains some backwards incompatible changes >   in some languages. > - Full detailed release notes are in the changes file. "
Answer: 301598.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: "It should be possible to reply to JIRA issue e-mail messages, and have those replies added as comments to the relevant issue."
Answer: 49100.0

User story: On 3/17/14, 10:07 , <USER>the Good wrote:> I don't seem to be able to change a status (e.g. to Ready to Merge) and change the assignee simultaneously in JA plan (i.e. by dragging).  The Atlassian docs imply that this is possible;  is this something about our workflow? >   A "Screen" needs to be defined, that would pop up whenever the issue is moved to a column. I'll open an issue and we'll get to it. 
Answer: 15209.0

User story: "Creation of a Dcr-aware ImageDifferencingTask.  This may include more edits to the image warping than to the image differencing itself, depending on the implementation of Dcr compensation.   This may also end up forking off into other storylines if we decide we want to test multiple approaches to the problem."
Answer: 1542291.0

User story: "Subclassing of coaddition that use Dcr during the coadd process.  Likely will involve edits to the warping process more than to the coadd process."
Answer: 1542292.0

User story: "Subclassing of Psf to create a Dcr-aware version of Psf modeling.  There will likely be testing that extends beyond the scope of this task."
Answer: 1542296.0

User story: "Subclassing of Wcs to include the effects of Dcr in the astrometric representation."
Answer: 1542299.0

User story: "The HSC camera needs to be put in the new camera geometry.  I will implement is like we did lsstSim and sdss.  That is I will generate a repository with the camera config and ampInfo FITS files that can be unpersisted by the butler.  These changes should only require modifying obs_subaru.  My plan is to just use the policy file to populate the new geometry, but if there is more up to date information, I'll happily use that."
Answer: 498535.0

User story: "We've been mapping '.' to '_' in afw::table I/O, which unnecessarily complicates lots of things.  We'd like to switch to using '_' in the field names themselves, which requires ending this mapping in I/O, but we need to be backwards compatible.  So we'll add a version to the FITS headers, and continue the mapping if the version is not present or is less than some value.  Until we do this, the new field names being used in meas_base won't round-trip."
Answer: 52451.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "After looking at it a bit more, I think we should refactor the current meas_base forced photometry task to separate the CmdLineTask from the Measurement task.  This will allow the forced measurement task to share a common base class with SingleFrameMeasurementTask (allowing us to move the callPlugin free functions into that base class), and give us better parallels with existing tasks:  - ProcesImageForcedTask (my proposed name for the base command-line task) will be more similar to ProcessImageTask.  We'll also have ProcessForcedCcdTask and ProcessForcedCoaddTask.  - ForcedMeasurementTask will be more similar to SingleFrameMeasurementTask.  In short, I think this will both clean up the ugliness in callPlugin and make the whole hierarchy easier for newcomers to understand."
Answer: 1187050.0

User story: "Create meas_base Plugins for single-frame and forced measurement that uses the model-fitting primitives in meas_multifit to implement SDSS-style CModel magnitudes, in which we fit an exp and dev model separately and then fit the linear combination with ellipse parameters held fixed.  An old-style plugin has already been implemented on the HSC fork, and should be used as a guide; this issue involves adapting that implementation to meas_base and potentially cleaning it up a bit.  Note that the HSC implementation cannot be transferred directly to the LSST side because the meas_algorithms APIs are slightly different on the two forks."
Answer: 307025.0

User story: "Refurbish existing configuration scripts to make them work with the new packaging/build system."
Answer: 24072.0

User story: "Setup whole Qserv environment, including installing data set, and validate it by running some simple queries. Suggest changes/improvements as appropriate."
Answer: 78887.0

User story: "We should switch Qserv to the MariaDB Foundation based MySQL."
Answer: 955403.0

User story: "Tune database performance and assist people running production as needed with all database related issues."
Answer: 288131.0

User story: "(oops, earlier description was meant for DM-878. Sorry for the confusion. -<USER> (I also made a mess with the assignees. I'm sorry. -<USER>"
Answer: 70282.0

User story: "The qserv worker scheduler code is a bit ugly.  The actual composable scheduler classes (FifoScheduler, ScanScheduler, GroupScheduler, BlendScheduler) might be pretty clean, but the interactions with the rest (wdb, wcontrol) may be harder to understand.  There should be a small amount of low-hanging fruit of code to clean up, but to make things more sensible and understandable may require some new abstractions and shuffling of logic to new/different classes.  Since this issue was opened, some refactoring work has been done as part of the new xrdssi port, so the organization may be somewhat cleaner now. Still, it's worth it to take a fresh look to evaluate the design/interactions to see how much can/should be reorganized."
Answer: 541330.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: "It'd be useful to test Qserv using Winter2014 or Summer2014 data set on a multi-node cluster, just to exercise all pieces of the software and double check we are not missing anything."
Answer: 538331.0

User story: "Revisit the architecture. This includes proxy, down to XRootD client (mysqld, python, zookeeper). Capture all findings in new stories, add these stories to DM-1707"
Answer: 491127.0

User story: "This includes switching Qserv to the new logging. Fine-tuning (what messages are printed deciding on error level) is covered in DM-685."
Answer: 287130.0

User story: "The database technology has been selected (described in LDM-135), need to get it captured in the official documents."
Answer: 216263.0

User story: "Finish implementing the mysql wrappers for python. Most is already implemented, but it can't be deployed because of logging. This is related to DMTF-16570-28"
Answer: 67590.0

User story: "Once the hardware is available, setup the environment where we could easily run integration testing of different Qserv releases, including testing/comparing performance.  Integrate changes implemented in DM-1078  Add install script that exposes individual steps and allows modifications to the config file: newinstall, qserv-configure --prepare, then edit config file (or copy from somewhere), qserv-configure"
Answer: 353068.0

User story: "Design and build toy prototype of a test framework for testing query execution module. This might require a mock framework, as we want to be able to test things in isolation, without testing everything around the query execution module at the same time. This is related to DMTF-16570-21."
Answer: 541619.0

User story: "Reimplement how results are returned from worker to the czar. Currently it relies on mysqldump, which is fairly inefficient. This is related to DMTF-1650-045"
Answer: 288203.0

User story: "Add support to the Ref*Match tables. The relevant code in Qserv core (supporting joins) has already been written. This task is related to DMTF-1640-20"
Answer: 269619.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "This is continuation of DMTF-16570-16. Initial work (v1) was done in branch u/<USER>protolog. V2 will include comments sent by K-T and issues discussed at the Qserv meeting March 13  + Free functions vs. a log object need to be discussed more.  In particular, when metadata key/value pairs need to be attached, an object might make more sense.  Avoiding the getLogger() call when no logging is needed (due to threshold) can be significant.   + It's a security breach to use vsprintf() with any user-provided arguments.  Use vsnprintf() instead so that you can check for overflow. (Or use stringstream or boost::format.)   + In my prototype, I used a combination of a set of static log4cxx::LevelPtr variables with isEnabledFor(level) and a set of cpp macros to avoid the switch.   + The return value from getLogger() shouldn't need to be cast.  ----   + play with hierarchical names  + don't execute code for formatting if debug level is off  + use shorter threadId  + experiment with defining special python handler, intercept and redirect     to our log4cxx-based logging  "
Answer: 109033.0

User story: "Deal with reference catalogues that are in a range of formats.  N.b. this includes doing the matching. "
Answer: 421664.0

User story: Right now, lsst.ci.build has a function:  {code} def declareEupsTag(tag, eupsObj):     """ Declare a new EUPS tag         FIXME: Not sure if this is the right way to programmatically                define and persist a new tag. Ask RHL.     """     tags = eupsObj.tags     if tag not in tags.getTagNames():         tags.registerTag(tag)         tags.saveGlobalTags(eupsObj.path[0]) {code}  Is this the right way to define a tag?
Answer: 22068.0

User story: "Unit tests need to be written for lsst-build; they should've been written together with the code, but due to Winter'14 release fire drill they had to be postponed."
Answer: 681538.0

User story: "All built packages are EUPS-tagged with build IDs (the bNNN EUPS tags). Without this change, new EUPS tags are declared even when nothing changed since the previous build (and EUPS' tags code doesn't scale well at this time).  This will be implemented by comparing the newly built manifest against ones stored in versiondb, and reusing the build IDs if a matching one is found."
Answer: 249.0

User story: "Whenever an issue is transitioned on JIRA Agile board to 'Ready for Review', a screen should pop up to ask for a reviewer.  Whenever it's moved out of that state, another screen should ask for a new assignee."
Answer: 39830.0

User story: "As an I&T person, I want to be able to git-clone lsstsw_home, run a bootstrap script, and have everything ready to run stack builds/publishings on my machine.  This script should: * Download and set up Python (Anaconda) * Download and build git, git manpages * Download and build EUPS * symlink manifest.remap from etc to stack/site * git-clone lsst_build tools * git-clone versiondb "
Answer: 28223.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: "Move buildbot repos to final locations in LSST/DMS, and give permissions to lsstsw user to write versiondb."
Answer: 28235.0

User story: "The Winter2014 cycle did not leave enough time to refactor pipeQA to use the new cameraGeom.  This will be taken as a task for Summer2014. "
Answer: 1264205.0

User story: "In refactoring cameraGeom, it has become very clear that the coverage of pipe_tasks is very poor.  I attribute this to the difficulty of creating an appropriate butler and data repository to feed to the tasks.  I propose that we generate a data repository in obs_test that contains: * An example camera ** This will include example code to generate the test camera ** An initial try at this exists in cameraGeom.testUtils and could be moved over * A set of example data including defects and calibrations ** I imagine this would be a set of a few simulated images * Astrometry.net indexes and any other ancillary data needed for reduction.  If this is too big to go in a git repository, we could use the [git-fat|https://github.com/jedbrown/git-fat] extension to git."
Answer: 2804013.0

User story: "The versions auto-generated by the new EUPS+buildbot look like this:  {code} ========== $ eups list .... pipe_tasks            7.3.2.0_5_g455c355d0f+070b2c1b35  b61 pyfits                3.1.2+9ef17db9b7  b61 b60 python                0.0.1             b61 b60 scisql                0.3+2b5a2f1b52    b61 b60 scons                 2.1.0+2b5a2f1b52  b61 b60 sconsUtils            6.2.0.0_11_gf38997df3e+759c3944a1         b61 sconsUtils            6.2.0.0_19_g755151c0a5+759c3944a1         b60 shapelet              7.3.1.0_1_g9331ee763c+0c72f294dd  b61 shapelet              7.3.1.0_1_g9331ee763c+e56ee84a68  b60 skymap                7.3.1.0_1_g64b750c066+db36490146  b60 skymap                7.3.1.0_1_ga6cd540cd3+493a438aa2  b61 skypix                6.1.0.0_1_g1157bf09ae+65137c93cd  b61 skypix                6.1.0.0_1_gea33592463+6039c04989  b60 .... ========== {code}  where the part before the plus sign is the output of git describe (slightly mangled), and the part after is the SHA1 of the sorted names+sha1s of the dependencies.  While this has the benefit that any two causally disconnected buildbots with the same inputs will build the same versions, many people have complained that they're plain ugly.  So here's an alternative proposal:  * If a tag exist on a commit, use <tag> as the version. * If there's no tag, use branchname-gSHA1ABBREV, where any illegal characters in branchname get turned into dots * If the package has dependencies, and a build of this package with different dependencies already exists, append a +N to the end. Keep the mapping of +N -> (dependency name, sha1s) in a special git repository. Given the source code and this git repo, two causally disconnected buildbots will again generate the same set of versions.  Example versions: * 7.10.2.1 * 7.10.2.1+5 * master-gdeadbeef * feature.dm-1234-gdeadbeef * feature.dm-1234-gdeadbeef+3 "
Answer: 6745.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: "Portions of the report about the Summer '13 Split DRP were written by [~<USER>, [~<USER>, and <USER>  Pull them all into a single coherent report."
Answer: 1087709.0

User story: "Need to come up with detailed design covering how we will deal with data distribution: managing multiple replicas, recovering from faults, adding new nodes to the cluster, registering new data from L2 ingest and user data (L3)."
Answer: 246255.0

User story: "This task is related to DMTF-16570-09. It involves plugin in the new XRootD client (which has different interfaces, it is all async etc). We expect to also do a major cleanup on the code that is talking to XRootD while plugging in the new XRootD."
Answer: 250512.0

User story: "Detailed design covering how all Qserv components will be configured for runtime. "
Answer: 97317.0

User story: "Use issue/DM-NNNN branches for issues tracked in JIRA, to differentiate them from tickets/NNNN branches that are still in Trac."
Answer: 5516.0

User story: "Update Confluence instructions on how to install the Winter'14 stack.  The instructions are at: https://confluence.lsstcorp.org/display/LSWUG/LSST+Software+User+Guide"
Answer: 149669.0

User story: "Run lsst-build scripts and 'eups distrib create' to build the Winter'14 release."
Answer: 24499.0

User story: "Need to know where W'14 stack files are going to be housed."
Answer: 5777.0

User story: "Release EUPS 1.3.0 in RHL's github repository."
Answer: 8423.0

User story: "See https://dev.lsstcorp.org/trac/ticket/3146  Story points estimate is for remaining work only (just the code review, which is still substantial)."
Answer: 107707.0

User story: "Open the Confluence Questions site, for interaction with the community (and to enable community self-help).  "
Answer: 1067298.0

User story: "We all benefit from making LSST software development as open as possible and conducive to outside volunteer contributions (*). One way to increase community involvement is to open up our development mailing lists to the public, analogous to the way other open source projects do. For example, we could have:  * <EMAIL>: the development mailing list, equivalent to current lsst-data * <EMAIL>: the users mailing list, equivalent to current lsst-dm-stack-users mailing list (but it could possibly be replaced by StackOverflow/Confluence Questions) * <EMAIL>: internal, DM-staff only mailing list, for the *rare* discussions/notices that should go out to staff only.  (*) Though we don't rely on them for meeting the project specs (legally required disclaimer :) )."
Answer: 413535.0