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: "Following DM-595 we can start qserv in multi-node configuration. Next step is to be able to run integration tests in that setup. This needs a bit of understanding how to distribute chunks between all workers in a cluster and how to load data in remote mysql server."
Answer: 132374.0

User story: "Implement JSON results for Metadata Service (see all M* in https://confluence.lsstcorp.org/display/DM/API),  and Database Service (see all D*) as defined in DM-1868"
Answer: 136367.0

User story: Whenever lsstsw builds a package from a version that doesn't have a git tag, the eups version number is set to something like "master-a235b31", which doesn't provide any indication about its ordering relative to tagged versions.  This is helpful when the version is not on master, and the version instead includes some indication of the branch name, but for versions on master, it'd be more helpful to use the output of "git describe" directly, as that will provide a number that is derived from the most recent tag, sorts properly almost all the time, and is still traceable back to the original git commit.  I'm not sure where this version generation code actually exists - I'm pretty sure it's not sconsUtils, but it could be lsstsw or eupspkg.  It might even be something one of these makes configurable externally.
Answer: 92779.0

User story: "process email discussion about the need to liaison with the putative Chilean design contractor.    Kantor suggests a contractor to support requirements may be apropos. "
Answer: 259520.0

User story: "receive edits from Jeff Barr,  accept the formatting and mechanical l edits. Compose separate email list issues related to non LSST tenants in the  room.  "
Answer: 1.0

User story: "1) Have one basic definition of racks and other components in the specifications.  2) Fully write up first full draft  specification for the supporting material  handing area."
Answer: 3.0

User story: "The Geom class was ported from C code 20 years ago.  It needs to refactor to comply with Java OO design.  "
Answer: 2753711.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 need to setup a service (eg on lsst-dev) that can be used by the IPAC team to play with our webserv/metaserv/dbserv/imgserv.  The server runs on lsst-dev machine, port 5000. To ssh-tunnel, try: {code} ssh -L 5000:localhost:5000 lsst-dev.ncsa.illinois.edu {code}  An example usage:  {code}   curl 'http://localhost:5000/db/v0/query?sql=SHOW+DATABASES+LIKE+"%Stripe%"'   curl 'http://localhost:5000/db/v0/query?sql=SHOW+TABLES+IN+DC_W13_Stripe82'   curl 'http://localhost:5000/db/v0/query?sql=DESCRIBE+DC_W13_Stripe82.DeepForcedSource'   curl 'http://localhost:5000/db/v0/query?sql=DESCRIBE+DC_W13_Stripe82.Science_Ccd_Exposure'   curl 'http://localhost:5000/db/v0/query?sql=SELECT+deepForcedSourceId,scienceCcdExposureId+FROM+DC_W13_Stripe82.DeepForcedSource+LIMIT+10'   curl 'http://localhost:5000/db/v0/query?sql=SELECT+ra,decl,filterName+FROM+DC_W13_Stripe82.Science_Ccd_Exposure+WHERE+scienceCcdExposureId=125230127'   curl 'http://localhost:5000/image/v0/raw/cutout?ra=7.90481567257&dec=-0.299951669961&filter=r&width=30.0&height=45.0' {code} 
Answer: 51531.0

User story: "This story covers implementing proper response, and the header metadata for the fits image response."
Answer: 194141.0

User story: "As discussed at [Data Access Hangout 2015-02-23|https://confluence.lsstcorp.org/display/DM/Data+Access+Hangout+2015-02-23], we should support json format. This includes defining the exact format, and implementing it. This story covers defining the format."
Answer: 1546.0

User story: "* Consider each cell as a list of milestones to be achieved by a certain date * Disregard UML use cases for now * WBS change disallowed "
Answer: 453730.0

User story: "* Find upscopes, prefer those that come as late as possible. Focus on optimizations within DM. * Upscope ideas:   - Special programs?   - Restore alert production at base? "
Answer: 14714.0

User story: "meas_extensions_shapeHSM has just been resurrected from bitrot, and should be included in our distribution.    Contrary to DM-2140, it should probably not be included in lsst_apps, as it's not clear we want to add a dependency on tmv and GalSim there."
Answer: 636111.0

User story: "I've updated, tagged, and built (via buildbot) new versions of two packages:  - tmv 0.72.lsst1  - GalSim 1.2.lsst2 Eups tag b748 includes both of these.  Please publish eups distrib packages of these (they're dependencies of meas_extensions_shapeHSM, which I've just resurrected from bitrot, and would now like to include with the rest of the stack).  Alternatively, feel free to reassign to me if you also give me lsstsw privileges."
Answer: 620219.0

User story: DDL information is embedded as comments in the master version of the schema (in "cat" repo). Currently we are only using it for schema browser. This story involves building tools that will load the DDL schema into MetaServ. Design aspects are covered in DM-1770.
Answer: 33006.0

User story: "Need to validate query (from security standpoint that user enters through rest api."
Answer: 55964.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: "When building {{meas_base}}, or any other measurement plugins which follow the same interface, with clang, I see a bunch of warnings along the lines of:  {code} In file included from src/ApertureFlux.cc:34: include/lsst/meas/base/ApertureFlux.h:197:18: warning: 'lsst::meas::base::ApertureFluxAlgorithm::measure' hides overloaded virtual function       [-Woverloaded-virtual]     virtual void measure(                  ^ include/lsst/meas/base/Algorithm.h:183:18: note: hidden overloaded virtual function 'lsst::meas::base::SimpleAlgorithm::measure' declared here:       different number of parameters (4 vs 2)     virtual void measure( {code}  This is an artefact of a [workaround for SWIG issues|https://confluence.lsstcorp.org/pages/viewpage.action?pageId=20284390]; the warnings aren't indicative of a fundamental problem, but if we can avoid them we should.  While we're at it, we should also fix:  {code} include/lsst/meas/base/ApertureFlux.h:233:1: warning: 'ApertureFluxResult' defined as a struct here but previously declared as a class       [-Wmismatched-tags] struct ApertureFluxResult : public FluxResult { ^ include/lsst/meas/base/ApertureFlux.h:65:1: note: did you mean struct here? class ApertureFluxResult; ^~~~~ struct {code}"
Answer: 13897.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: "See DM-1847 - Andy made a patch, it'd be good to the xrootd we use for our stack."
Answer: 29631.0

User story: "Long term planning (updating LDM-240)."
Answer: 57104.0

User story: "dbREST_v0.py in dbserv is currently using MySQLdb instead of going through the db API, because we need to use parameter binding for security reasons. We should switch to using db, once the db interfaces will support it. "
Answer: 18209.0

User story: "metaREST_v0.py in metaserv is currently using MySQLdb instead of going through the db API, because we need to use parameter binding for security reasons. We should switch to using db, once the db interfaces will support it. "
Answer: 18261.0

User story: "Once the data has been loaded, this tool has to its check correct state  Non exahustive list: - empty chunk file, - xrootd exported DB, - data  tables - overlap tables, - data_0123456789 tables - chunkId, subChunkId columns existence ..."
Answer: 13.0

User story: "Rename TaskMsgFactory2 to TaskMsgFactory.    Please see DM-211 for more information."
Answer: 482206.0

User story: "Attend database talks, in particular the MaxScale proxy talk (http://www.socallinuxexpo.org/scale/13x/presentations/advanced-query-routing-and-proxying-maxscale?utm_campaign=north-american-trade-shows&utm_source=hs_email&utm_medium=email&utm_content=16099082&_hsenc=p2ANqtz-_MFjfxvpCdmV_Ax2RKDdOGypHPQ85UL-UMuy0eRs_MrlJ2qJVp-MXx-g7_-dAQsq0trpA61hkZrzO-3gp6bKVkpK52fQ&_hsmi=16099082).  If anyone has questions they would like me to ask, please post them here as well.  I will post notes to this issue. "
Answer: 13033.0

User story: "- Create a React JavaScript component, which takes the data and renders histogram.  - Make it possible to call this component from GWT code, using experimental JsInterop technology in GWT 2.7"
Answer: 103747.0

User story: "Convert necessary code to make it possible for a JavaScript component to place a JSON request to the server and to parse the resulting RawDataSet.  "
Answer: 292519.0

User story: "For longer term planning purposes it'd be useful to have in Jira cycles up to 2020 (LDM-240 covers up to 2020). In jira, we currently have up to Winter 2016"
Answer: 26104.0

User story: "I have an idea for how to improve Swig build times that we should get vetted (and possibly improved upon) by a true Swig expert (even if that costs a bit of $$).  This issue includes vetting that idea (splitting up classes into multiple per-package module builds), getting it through the RFC process, and implementing it in afw."
Answer: 1068527.0

User story: "e.g. develop script to handle bulk namespace changes."
Answer: 1069386.0

User story: "Discuss and decide how to deploy and upgrade Qserv software"
Answer: 286822.0

User story: "Some tables, like Exposure, provenance, will not be partitioned, and the current plan is to either replicate them on each node, or store on shared file system. Need to decide how it will be dealt with."
Answer: 153725.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: "Research implications of having to deal with updatable Level 3 data."
Answer: 287878.0

User story: "This should split all content in pipe_tasks into two packages (aside from what may have been removed in previous issues)."
Answer: 1069489.0

User story: "Create detailed RFCs and implement splitting measurement plugins into separate package.  May want one package for extremely basic plugins, always-used plugins (PixelFlags, TransformedCentroid, etc).  See also https://confluence.lsstcorp.org/display/DM/Summer2015+Package+Reorganization+Planning"
Answer: 1069493.0

User story: "meas_deblender, ip_isr, meas_astrom, meas_modelfit, and ip_diffim do not require major refactoring to fit into the new package reorganization, but they should be renamed (with sci_prefixes).  See also https://confluence.lsstcorp.org/display/DM/Summer2015+Package+Reorganization+Planning"
Answer: 1069500.0

User story: "Create detailed RFC and implement move of concrete PSF estimation code and Psf subclasses from meas_algorithms to separate package.  See also https://confluence.lsstcorp.org/display/DM/Summer2015+Package+Reorganization+Planning"
Answer: 1069505.0

User story: "Create detailed RFC and implement move of interface and utility code from multiple existing packages to new package.  See also https://confluence.lsstcorp.org/display/DM/Summer2015+Package+Reorganization+Planning"
Answer: 1069513.0

User story: "This story involves implementing code that stitches images, simple case that does not involve tract boundaries. More advanced case in covered in separate ticket. We will need to determine WCS information for the target images."
Answer: 66109.0

User story: "Create detailed RFC and implement package split, to separate basic Tasks (to be used as e.g. subtasks) from CmdLineTask and ArgumentParser.  See also https://confluence.lsstcorp.org/display/DM/Summer2015+Package+Reorganization+Planning"
Answer: 1069511.0

User story: "Create detailed RFC and implement move for these packages.  See also https://confluence.lsstcorp.org/display/DM/Summer2015+Package+Reorganization+Planning"
Answer: 1069516.0

User story: "Create RFC and remove Jarvis/shapelet package from meas_algorithms, into new legacy sci package.  See also https://confluence.lsstcorp.org/display/DM/Summer2015+Package+Reorganization+Planning"
Answer: 1069516.0

User story: "Create RFC and implement move of Wcs from afw::image to afw::coord.  See https://confluence.lsstcorp.org/display/DM/Summer2015+Package+Reorganization+Planning"
Answer: 1069522.0

User story: Remove dependency on base from pex_exceptions and rename to just "exceptions" (after RFC).  See also https://confluence.lsstcorp.org/display/DM/Summer2015+Package+Reorganization+Planning
Answer: 1069523.0

User story: "Create detailed RFC and implement merge of base, utils, and daf_base.  See also https://confluence.lsstcorp.org/display/DM/Summer2015+Package+Reorganization+Planning"
Answer: 1069520.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 already an external ndarray project on GitHub (we've been using a fork of that).  We should merge the forks and switch to using the external package. "
Answer: 834962.0

User story: "Remove pex_harness from lsst_distrib so we can retire pex_harness. One package that may still rely on pex_harness is datarel"
Answer: 313584.0

User story: "Once we decide on a design for data distribution / replication, we should come up with a test plan."
Answer: 155103.0

User story: "Define a strategy (push/pull distributed/decentralized) for recognizing incoming data and cleaning up/removing stale/deleted data. Is data ingest just another form of failure recovery?"
Answer: 113077.0

User story: "Produce an overview document that explains our definitions, architecture and strategies for dealing with data distribution and replication. "
Answer: 155124.0

User story: "Peruse the distributed systems literature for prior approaches to this problem, and examine existing system implementations for components/ideas we could reuse."
Answer: 155133.0

User story: "Come up with an architecture for detecting failure or non-nominal conditions (e.g. under replication). The core question to resolve is whether we go with a distributed approach, or with centralized control."
Answer: 113099.0

User story: "Decide on a transport mechanism for data (bit torrent, scp, or ?). We must take into consideration whether the data source matters in this choice (e.g. tape vs known good node), as well as how to identify that a data source is the correct one (e.g. via checksums and sequence numbers)."
Answer: 113104.0

User story: "Whiteboard session(s) to gather a list of invariants / principles that define a consistent state, a list of fault conditions, and the steps in failure recovery."
Answer: 113107.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: "(by Daniel) qserv_areaspec_box asks qserv to choose chunk/row coverage according to the director table. Generally, it detects the director table from the query, computes the region against the index, and then substitutes the right directive. But in this case, there is no director table, only a child table. Hence, even if we know what the director table is, its columns are not available to use in the query, unless we rewrite to add an equi-join with the director table. The best we can do in this case (without adding a join), is to use the parameters for determining chunk coverage, and then covering all rows in those chunks. The user could specify additional conditions to apply spatial filtering based on other (non-partitioning) columns.  Another thing we could do is to detect scisql region directives in the WHERE clause, but this expands the detection and dependence on scisql name/syntax (the first is in the angle distance condition when determining spatial join evaluability).  Anyway, what I'm trying to say is that the right thing to do isn't completely clear, and the possible options are not that simple to implement (though the ones I've listed are certainly possible, and should be much easier than refmatch support). "
Answer: 2711832.0

User story: When error conditions are detected in SsiSession (unowned chunk, garbage request), all we do is "return false;". The right thing to do bundle up and send back a well-formed error message. The code to change is in SsiSession::ProcessRequest().   Estimated work: 4 sp, but does not include crafting tests, which may be tricky and perhaps not worth it.
Answer: 491591.0

User story: "Add basic error handling for the RESTful flask-based API"
Answer: 162137.0

User story: Add unit tests for the RESTful flask based API. I think it'd be most useful if we could  a) load some test data into underlying metaserv  b) run programmatically things like "curl -H accept:text/html http://127.0.0.1:5000/meta/v0/db/L2/DC_W13_Stripe82/tables" etc (more examples in dax_*serv/README.txt) and verify that we got what we expected. Do it for both json and html.
Answer: 479097.0

User story: "Research and document versioning of the RESTful API (through flask blueprints). In particular, need to understand how to avoid code duplication between different versions of API."
Answer: 251410.0

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

User story: "SWIG 3.0.5 is now out and has several useful fixes w.r.t. 3.0.2 (which we are presently using) including:  - A bug we've had to work around involving templated methods of classes  - improved handling of new-style enums (they are no longer hoisted into the global namespace, which was a serious misfeature of SWIG 3.0.2)    I propose we try it out using buildbot (when we have some time), and if it works, we adopt it. Adopting it will help us relax the restrictions on what C++11 features can be used in C++ header files."
Answer: 781978.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 ISR task should write a DistortedTanWcs to the assembled exposure, instead of the pure TAN WCS that it starts with. (DistortedTanWcs is a plane TAN WCS plus a distortion model; the necessary distortion model can be directly read from the detector information in the camera geometry).  Warning: DistortedTanWcs cannot presently be persisted (DM-1970 is a ticket to fix this). Hence it is risky to put a DistortedTanWcs into a WCS. If the task then attempts to persist the exposure with that WCS (very likely if it persists the snaps) that will fail. Thus I am very nervous about doing this before at least a simplified version of DM-1970 has been implemented (e.g. persisting the WCS as a TAN-SIP WCS). However, others have recommended doing it now so I am not listing DM-1970 as a blocker."
Answer: 2325958.0

User story: "We can simplify the astrometry solver if we have a Wcs that encapsulates a pure tangent-plane WCS and a distortion model that takes converts between PIXELS and TAN_PIXELS. This is useful because at the early stages of processing raw data we have a TAN WCS from the telescope control system and a pretty good estimate of distortion from the optical model (represented in the camera geometry).  The result will be a Wcs whose sky<->pixel transformation is a reasonable approximation of reality (and a much better approximation than the tangent-plane WCS that is currently available. This will potentially eliminate a significant amount of confusing code that attempts to correct for distortion by manually applying the optical distortion model."
Answer: 7197.0

User story: "eupspkg was used for parallel build, but it involves a dependency on git 1.8.4.x, so nproc, which is even bundled with minimalist Docker system will be used instead."
Answer: 2415393.0

User story: "Create a command-line task that makes use of the new PSF estimation interface, duplicating as much of ProcessCcdTask's functionality as necessary to provide the inputs to PSF estimation (I expect this new task to ultimately replace ProcessCcdTask).  This may have to include workarounds or temporary implementations for parallelization features that are not yet available.  Create a simple PSF estimation placeholder that simply uses existing single-CCD PSF-determiners."
Answer: 1167554.0

User story: "Create a Python interface for a pluggable PSF estimation system that supports algorithms that will operate over full images.  This should include a sketch of how a calling command-line task, and placeholders for parallelization interfaces that may not yet be finalized.  The output of this issue is a completed RFC on the design."
Answer: 1167556.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 need to gather algorithmic ideas for how full focal plane PSF estimation will work from a parallelization and data flow standpoint, and discuss with the middleware team how these should be handled from an interface standpoint.  Questions include:  - Will we need to do significant cross-CCD image processing or require significant memory for these tasks?  If so, should we structure this via message passing between CCD-level processes, or scatter-gather?  - Assuming a scatter-gather approach, will we need multiple scatter/gather iterations when processing a single visit?  - How much data will be passed between threads/processes?  Would this include complex serializable objects, or just POD arrays?  - Will different PSF estimation plugins will have different parallelization requirements?  Or, can we define the plugin interfaces at a low-enough level that parallelization can be handled by the framework?  If plugins do need to control their own parallelization, how do we make parallelization interfaces accessible to the plugins?"
Answer: 1167616.0

User story: "Coordinate running large scale tests"
Answer: 162928.0

User story: "Load data set for large scale tests (duplicate, partition, load)"
Answer: 121600.0

User story: "This is a transfer for changesets for [HSC-1062|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1062].    Unlike most of the HSC backport issues for multiband deblending, these changes will require significant modification the LSST side, because we need to apply them to the new forced measurement framework in meas_base rather than the old, HSC-only one in meas_algorithms and pipe_tasks.    Also include [HSC-1256|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1256], [HSC-1218|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1218], [HSC-1235|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1235], [HSC-1216|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1216]."
Answer: 274396.0

User story: "These are to note leftovers from DM-982.  They could be done in a single issue. 1.  I commented code out referring to correctfluxes, but it will need to be restored once it is available in the new framework.  2.  Jim asked me to replace the computeSincFlux which is currently in PsfImage.cc in meas_algorithms with a similar call in meas_base/ApertureFlux.cc.  I did not do this because it became rather complicated, and can just as easily be done when the meas_algorithms routine is moved or removed.  Basically, the templating in ApertureFlux is on Pixel type, whereas in meas_algorithms it is on ImageT (where ImageT is not necessarily a single class hierarchy -- e.g., Image and MaskedImage).  So I left this for now."
Answer: 74513.0

User story: "Next message should be logged with ERROR priority:  {code} 0204 15:08:03.748 [0x7f1f4b4f4700] INFO  Foreman (build/wdb/QueryAction.cc:250) - [1054] Unknown column 'whatever' in 'field list'   {code}"
Answer: 41.0

User story: "Add hooks in czar that will let us build unit tests."
Answer: 335361.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 a transfer of changesets from the follow epics:  - [HSC-1020|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1020]  - [HSC-1075|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1075]: only the afw changes  Because this is purely an addition to the interface, and we're planning to redesign that interface in DM-1904, I don't think we need an RFC here."
Answer: 114117.0

User story: "This issue includes transferring changesets from many HSC issues:  - HSC-1060  - HSC-1064  - HSC-1065  - HSC-1061  Most of this is in multiBand.py in pipe_tasks, but there are scattered changes elsewhere (including updates to camera mappers to include the new datasets, for which we'll need to modify more than just obs_subaru).  However, before we make these changes, we'll need to open an RFC to gather comments on the design of this task.  We should qualify there that this is not a long-term plan for consistent multiband processing (which we'll be starting to design on DM-1908), but a step towards better processing in the interim.  Note: while I've assigned this to [~<USER>, as I think it will be very helpful for her to get familiar with this code by doing the transfers, the RFC will have to involve a collaboration with [~<USER>, [~price], and <USER> as we can't expect someone who wasn't involved in the design to be able to write a document justifying it."
Answer: 198972.0

User story: "This issue covers transferring changesets from:  - [HSC-134|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-134]  - [HSC-1109|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1109]  - [HSC-1083|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1083]  "
Answer: 110649.0

User story: "This issue covers transferring all changesets from [HSC-1074|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1074] and its subtasks, as well as:  - An RFC to propose the API change, and any requested modifications generated by the RFC.  - Additional fixes to downstream code that's broken by this change (HSC-side changesets should be present for most of downstream fixes, but perhaps not all)."
Answer: 109751.0

User story: "Organize the SUI team for web UI discussions to capture as much functions and components as possible.  A draft design document should be produced out of those discussions. "
Answer: 123029.0

User story: "Following the requirements-gathering in DM-1939, come up with classes that can be used to pass the needed inputs to the PSF estimation code, and at least sketch out roughly how they will need to be managed by the butler and loaded by the framework code.  The output of this ticket should be an API design in confluence (possibly on the same page used for DM-1939), and an associated RFC."
Answer: 1169182.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: "Define inputs needed to build physically-motivated PSF models beyond what's contained in the image data and the current CameraGeom.  This includes:  - static engineering data from lab tests  - slowly-varying engineering data (measured daily, weekly, etc.)  - per-visit auxiliary data from telescope and camera (including, but not limited to wavefront sensor data).  The focus here should be on APIs, not the technical details of the data; we want to define class hierarchies (perhaps some polymorphic ones) that can be used to pass this data around in the future.  We also want to identify and characterize any preprocessing that needs to be done before they can be used for PSF estimation.  Experts who should be consulted include [~<USER> (who is in charge of making sure the camera and telescope interfaces to DM are well-defined), camera/telescope people he recommends, and people from the LSST DESC who have worked on physical PSF estimation and know something about the things they'll want (e.g. Michael Schneider, <USER>.  This is essentially a requirements-gathering task, so the output should be a confluence page, not code."
Answer: 1169189.0

User story: "Test to confirm servers are configured optimally"
Answer: 28793.0

User story: "install and configure OS"
Answer: 28780.0

User story: "Many (all?) unit tests are currently built as static executables which include all needed object files. This has several issues associated with it: - many files are compiled twice, once as *.os files for shared libraries, second time as *.o file for unit tests - unit tests do not test actual code in the shared libraries but instead separately-built copy of the same code  We should change our procedure and make unit test to link against shared libraries to avoid these problems."
Answer: 2118209.0

User story: "The HSM shape code has undergone many improvements and bug fixes as part of being included in the GalSim package, and we've recently included those in the HSC fork of meas_extensions_shapeHSM (HSC-129, HSC-1093).  We should transfer those changes to the LSST side before tackling DM-981 (or at least before finishing it).  The story point estimate here is for the work already done on the HSC side (with the usual 50% factor for shared work).  The transfer to the LSST side should be essentially no effort.  To the extent that EVM cares about this, the credit should go to [~price], even though I ([~<USER>) am doing the transfer."
Answer: 25477.0

User story: Fix places where compiler is warning about some things we are doing on purpose and which we don't intend to change.  This helps keep compiler noise down so its easier to notice "real" warnings.
Answer: 186.0

User story: "The compiler is warning about some derived class hierarchies that are lacking virtual destructors.  We should add at least empty implementations to the base classes of these hierarchies."
Answer: 60.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: Brought up by Gregory via comments on the API page.  Data release selection in queries: I see that the /db/... queries take a "?" query parameter "db" with an example value of "DR1", i.e., a data release selector.  A couple of remarks: * Will this query parameter be provided for all the Level 2 image data products, e.g., for retrievals of coadded images? **If so, then it needs an equivalent to the M4 "GET /meta/v0/db/<type>" query. * I assume the "db" query parameter defaults to the most recent data release. * Will the M4 query return an indication of which "?db=" value is the current default? * I assume that the numeric-identifier components of the various paths are unique only within a single data release.  That means that eventually, in user documentation, we should make sure that they understand that they can't scan through different releases' versions of the same image (for example) just by varying the "?db=" parameter.   * Are the identifiers also unique within a particular type (i.e., "raw", "template", "coadd", "calexp", etc.)?  -----  Distinguishing L1 and L2 versions of reprocessed data products  Since most or all of the L1 data products will be regenerated in each data release, the catalog and image APIs should presumably allow the user to distinguish between the two.  I see how this could be done for catalogs - the "?db=" parameter presumably allows selecting something like "L1" (for the actively updated Level 1 database) in addition to the above-documented "DR1", "DR2", etc.  Will the L2 table names for the reprocessed L1 data products be generally expected to be the same as for L1?  (Barring the discovery of a serious issue that requires revision of the schema for the reprocessing.) How will the L1 and reprocessed-L1 image data products be distinguished?
Answer: 81996.0

User story: "With Firefly being open-source, we should provide a simple all-in-one installation package so a user can quickly setup and deploy an instance the Firefly Tools web application."
Answer: 36148.0

User story: "Outline an expandable Python framework for use by advanced users in interactive or batch mode. Many users should be able to contribute software to the framework following simple API guidelines. Also look at configuration and delivery systems for the software. Start by looking for existing Python software that could be used in the areas of: - Database & file access - Data analysis frameworks - Display of data,, especially in an Astronomical context. - Reading and writing data in different formats - Graphing data locally or over the web - Science and astronomy data analysis - Event interfaces - VO functionality and connecting with existing software like DS9,, Aladin, Topcat, etc. - Ways to integrate modules with an LSST focus like  AGN  Large Scale Structures  Galaxies  Local Volume  Solar System  Astrostatistics  Stellar Pops  Strong Lensing  Supernova  Transients  Weak Lensing  Camera - Configuration and delivery system  "
Answer: 36150.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: "Following DM-1598 there will be a detailed design and prototype implementation for the calibration & ingest system. This issue covers cleaning up that code, documenting it, having it reviewed, and merging to master."
Answer: 34552.0

User story: "plotChunksCopies.tcl, while dependent on output from obsolete code, is still the only way we have of visualizing the chunk layout. It should be ported to the current infrastructure."
Answer: 2123917.0

User story: "Once we have new service that controls worker communication we'll need to reimplement WorkerAdmin class based on that."
Answer: 171151.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: 67614.0

User story: "CSS information tree may become large and it would be nice to have a tool to examine that tree or parts of it. Something that dumps the tree in user-friendly way and allows filtering or summarizing.    Another area of improvement is CSS use in unit tests, right now we have a cumbersome procedure: qserv-admin dumps data in TSV format, that data is transformed by scons into header file which is included into C\+\+ code. Would be better to avoid intermediate steps and dump data in a format which can be used by tests directly (as a chunk of C++ code)."
Answer: 1512503.0

User story: "Modify CSS structures to support DROP TABLE, as defined in DM-1896."
Answer: 390190.0

User story: "Table/chunk deletion can be an extended process as some worker nodes may be temporarily down. We need to define a process and its supporting structures in CSS to allow gradual deletion of individual chunks and full tables.  Deliverable: a design of a system capable of deleting a distributed table (all chunks, all replicas). It should be possible to create a table with the same name after deletion."
Answer: 128137.0

User story: "Research producing cutout from images with overlaps."
Answer: 261339.0

User story: "Implement support for result formatting in IPAC table format."
Answer: 35810.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 include past experience, collection of use cases. "
Answer: 41903.0

User story: "WEBDAV could be a candidate for managing the user workspace.  summarize its capabilities and past experience, collect some use cases will help us to make a better decision."
Answer: 42010.0

User story: "SUI team had several discussions and Xiuqin presented the results at the DM AHM at SLAC. The slides and the discussion notes are here: https://confluence.lsstcorp.org/display/DM/Workspace+discussion"
Answer: 42097.0

User story: Implement RESTful interfaces for Database (see all D* in https://confluence.lsstcorp.org/display/DM/API), based on the first prototype developed through DM-1695. The work includes adding support for returning appropriately formatted results (support the most common formats). This covers "GET" type requests only, "POST" will be handled separately.
Answer: 260640.0

User story: "This is an on-going effort. The collected use cases will be posted at confluence page https://confluence.lsstcorp.org/pages/viewpage.action?pageId=41784036. "
Answer: 314337.0

User story: "As discussed at [Data Access Hangout 2015-02-23|https://confluence.lsstcorp.org/display/DM/Data+Access+Hangout+2015-02-23], we should support json format. This story covers defining structure of JSON results for Data Access Services (dbserv, imgserv, metaserv) "
Answer: 89568.0

User story: "Produce a single jumping-off point for documentation on all aspects of Level 3, on Confluence.  Ensure that flowdown for existing Level 3 requirements in SysML is modeled.  Describe the high-level conceptual design."
Answer: 2218068.0

User story: "Review existing requirements in this area.  Find all relevant existing project-controlled and other key documents."
Answer: 2218216.0

User story: "All done bar obtaining some release notes. "
Answer: 49119.0

User story: "This ticket covers code in sqre-codekit to do migrate as much of the process of special machines, and git tag repos on the basis of eupspkg manifests."
Answer: 276431.0

User story: "GetResponseData needs to handle data sets beyond 2 MB. The problem is discussed in more details in story DM-1841"
Answer: 33560.0

User story: "The form is being implemented by the DataCat team. Need to coordinate (including with the NCSA team which parts are covered by which team), test, fine tune etc."
Answer: 43536.0

User story: "Needed to run Qserv on CC-IN2P3 cluster."
Answer: 10237.0

User story: "In the old marshalling code, property sets were representable within the payload of the event.   This was removed in the new marshalling scheme.   There are things (ctrl_orca) that still used this, so this needs to be added to the new marshaling code.  At the same time, new new filtering code can not allow this to be added, because the JMS headers only take simple data types."
Answer: 1.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Per [~price] at DM-1545:  {code} /**  * Shrink a footprint isotropically by nGrow pixels, returning a FootprintSet.  */ PTR(Footprint) shrinkFootprint(Footprint const& foot, int nGrow, bool isotropic); {code}"
Answer: 5.0

User story: "<USER>
Answer: 14328.0

User story: "Lee LeClair, <USER>
Answer: 1512.0

User story: "Don Petravick, Richard Dubois"
Answer: 1513.0

User story: "Don Petravick, <USER>
Answer: 1514.0

User story: "Lee LeClair, <USER>
Answer: 1515.0

User story: "Don Petravick, <USER>
Answer: 1514.0

User story: "Don Petravick, Lee LeClair"
Answer: 1517.0

User story: "Don Petravick, Lee LeClair"
Answer: 1519.0

User story: "Don Petravick and Lee LeClair"
Answer: 1520.0

User story: "Produce a draft of LSE-75 with the following agreed revisions: * remove reference to advance notice of pointing, now in LSE-72 * add reference to PSF reporting"
Answer: 312554.0

User story: "Work with TCS contacts (Jacques Sebag, Paul Lotz, etc.) to define the principal issues"
Answer: 2.0

User story: "Clarify in LSE-140 that the DM data quality analysis referred to is primarily that of the Level 1 data products."
Answer: 316541.0

User story: "Complete any review-driven revisions of LSE-140 and support the CCB meeting and following final document preparation."
Answer: 14.0

User story: "Based on CCB approval of LSE-72 on 10 October, support the completion of the final copy of the document for posting on Docushare."
Answer: 2.0

User story: "To support discussions with the Camera, post a provisional docgen of LSE-68 to the appropriate Confluence page.  Use knowledge from EA training to improve template."
Answer: 311358.0

User story: "Following CCB recommendation of approval of LSE-130 draft, convert Word draft to SysML and provide a docgen to <USER>for final posting. "
Answer: 316481.0

User story: "Respond to comments, perform revisions to LSE-130 as necessary based on feedback from CCB review of the document"
Answer: 7094.0

User story: "Provide slides and other information needed for CD-2, mainly relative to the open questions around LSE-130"
Answer: 7093.0

User story: "Produce a reviewable draft of LSE-130 based on decisions on calibration operations"
Answer: 7094.0

User story: "During a working meeting with <USER>and Chris Stubbs, determine the impact on LSE-130 of the introduction of the collimated projector for calibration."
Answer: 7095.0

User story: "Prepare LSE-130 content as far as possible without input from the new collimated-projector calibration plan."
Answer: 7098.0

User story: "I'm seeing test segfaults in ip_diffim on gcc 4.8, similar to those resolved on DM-1725, but with no similar smoking gun yet.  Preliminary indication is that the problem is actually in meas_algorithms."
Answer: 147.0

User story: "Study the current requirement carefully to make sure they all make sense and we can do it."
Answer: 5.0

User story: "gcc 4.8 now warns about locally-defined typedefs that aren't used.  We have a few of these in ndarray and afw::gpu that should be removed."
Answer: 1103.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: "Do some test runs using Orca to make sure Orca still works after the the changes to ctrl_events."
Answer: 8618.0

User story: "Run the AP simulator to make sure that none of the changes to the ctrl_events package break anything."
Answer: 8447.0

User story: DM-1755 has been done before this feature was available. It uses rsync over ssh which require use to have an ssh-key on lsst-dev.  NSCA rsync server can now be accessed with next syntax: {code:bash} rsync -av lsst-rsync.ncsa.illinois.edu::qserv/qserv_testdata/datasets/case04/data/DeepSource.csv.gz . # LIST FILES AVAILABLE IN THE MODULE NAMED "qserv" rsync lsst-rsync.ncsa.illinois.edu::qserv  # To add content to this module/group, you can copy files into the following path:   /lsst/rsync/qserv/ {code}  rsync over ssh feature should be kept, in order to distribute private data are distributed.
Answer: 2137337.0

User story: "Reducing HSC data requires an estimate of the distortion, which is provided by the HSC package distEst.  This can be pulled into obs_subaru to consolidate code and reduce dependencies.  I propose to treat distEst as legacy code, which means I will pull it into obs_subaru without major changes to the code style."
Answer: 282537.0

User story: "The set of packages that will enable us to write against the native Python APIs of the OpenStack services is  {code} python-keystoneclient python-glanceclient python-novaclient python-quantumclient python-cinderclient python-swiftclient {code}  We begin testing these in DM-1787  on the NCSA OpenStack head node, but eventual use within LSST orchestrating workflow would entail these being installed on LSST nodes in the LSST stack.  In this issue we perform a basic installation of these packages into the system space on an LSST node/VM for testing.  These are managed in github, and we install these via 'pip install' onto an LSST VM for initial tests."
Answer: 196000.0

User story: "In our introductory work with OpenStack we have been utilizing the Horizon GUI interface for first steps, followed by the use of command line tools (the 'CLI') (e.g., nova, cinder, etc) as shown in DM-1334  DM-1700 , DM-1701. While it is possible to write automation scripts that utilize the CLI, an approach based on 'pure' Python scripting would fit more seamlessly into the LSST software development process. Enabling OpenStack automation via Python offers the opportunity to integrate provisioning of resources into the overall flow of LSST workflow & processing (e.g., DRP.)  The OpenStack services expose native Python APIs that expose the same feature set as the command-line tools.  The required python packages (python-keystoneclient, python-novaclient, ..) are installed on the head node 'vlad-mgmt' of the NCSA ISL OpenStack, and so initial Python scripting can be executed/tested there.  A first Python script will perform required authentication and launch an instance. "
Answer: 196010.0

User story: Add "rotAngle DOUBLE" to every table that has image ra/decl.  
Answer: 753413.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 has errors rendering nested expressions in predicates of the WHERE clause. It is unclear whether the problem is in constructing the predicate representation or in rendering the representation (or both).  Example: {code} SELECT  o1.objectId FROM Object o1  WHERE ABS( (scisql_fluxToAbMag(o1.gFlux_PS)-scisql_fluxToAbMag(o1.rFlux_PS)) -              (scisql_fluxToAbMag(o1.gFlux_PS)-scisql_fluxToAbMag(o1.rFlux_PS)) ) < 1 {code} Yields: {code} SELECT o1.objectId FROM LSST.Object_100 AS o1 WHERE ABS((VALUE_EXP FACTOR FUNCTION_SPEC scisql_fluxToAbMag(VALUE_EXP FACTOR COLUMN_REF o1.gFlux_PS)-FACTOR FUNCTION_SPEC scisql_fluxToAbMag(VALUE_EXP FACTOR COLUMN_REF o1.rFlux_PS)))<1 {code}  I probably left out a more general implementation one/both of those parts of query parsing/analysis."
Answer: 58848.0

User story: "This transfers some improvements to the Kron photometry from the HSC side:  - HSC-983: address failures on faint sources  - HSC-989: fix the minimum radius  - HSC-865: switch to determinant radius instead of semimajor axis  - HSC-962: bad radius flag was not being used  - HSC-121: fix scaling in forced photometry  The story points estimate here is 50% of the actual effort, as the work (already done) also benefited HSC."
Answer: 14067.0

User story: "- FITS reader class refactoring, improve readability - validation of the new code against the old one - unit test - performance improvement recording if possible"
Answer: 26908.0

User story: "For efficiency, XYPlotter is designed to create up to 4 cards. When the card limit is exceeded, a previously created card is reused to plot catalog data for the current catalog. When card is reused the previous plot metadata (like column selections, grid option, etc.) are lost."
Answer: 64685.0

User story: "Get catalog metadata, which should include column description, units, and type. Use it in tool tips and possibly to create flexible constraints.  A temporary solution is to get metadata from an internal lsst_schema_browser_S12_lsstsim database on lsst-db.ncsa.illinois.edu  A permanent solution would be querying catalog metadata from metadata store."
Answer: 23013.0

User story: "After the repository was split into firefly and new-ife, it was necessary to understand the changes, check for inconsistencies, test builds, set up new IDEA project, etc. "
Answer: 1.0

User story: "Read the requirements document on Archive Browser and Query Tools, make a record of unclear items, send questions to our scientist (D. <USER> "
Answer: 1.0

User story: "Create a search processor which accepts cone and box spatial constraints, queries a catalog, stored on QSERV (DeepSource), and returns the relevant rows as an IPAC table or RawDataSet.  The implementation is querying DeepSource catalog using qserv_areaspec_circle and qserv_areaspec_box spatial restrictors. "
Answer: 3971.0