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: When building the master on pugsley.ncsa.illinois.edu, shapelet builds successfully, but two tests fail:  {code} pugsley:lsstsw <USER> cat build/shapelet/tests/.tests/*.failed tests/testMatrixBuilder.py  .F..... ====================================================================== FAIL: testConvolvedCompoundMatrixBuilder (__main__.MatrixBuilderTestCase) ---------------------------------------------------------------------- Traceback (most recent call last):   File "tests/testMatrixBuilder.py", line 310, in testConvolvedCompoundMatrixBuilder     self.assertClose(numpy.dot(matrix1D, coefficients), checkVector, rtol=1E-14)   File "/Users/<USER>test/lsstsw/stack/DarwinX86/utils/9.2+8/python/lsst/utils/tests.py", line 328, in assertClose     testCase.assertFalse(failed, msg="\n".join(msg)) AssertionError: 1/50 elements differ with rtol=1e-14, atol=2.22044604925e-16 0.175869366369 != 0.175869366369 (diff=1.99840144433e-15/0.175869366369=1.13629876856e-14)  ---------------------------------------------------------------------- Ran 7 tests in 0.323s  FAILED (failures=1) tests/testMultiShapelet.py  ...F... ====================================================================== FAIL: testConvolveGaussians (__main__.MultiShapeletTestCase) ---------------------------------------------------------------------- Traceback (most recent call last):   File "tests/testMultiShapelet.py", line 88, in testConvolveGaussians     self.compareMultiShapeletFunctions(msf3a, msf3b)   File "/Users/<USER>test/lsstsw/build/shapelet/python/lsst/shapelet/tests.py", line 107, in compareMultiShapeletFunctions     self.compareShapeletFunctions(sa, sb, rtolEllipse=rtolEllipse, rtolCoeff=rtolCoeff)   File "/Users/<USER>test/lsstsw/build/shapelet/python/lsst/shapelet/tests.py", line 86, in compareShapeletFunctions     rtol=rtolEllipse)   File "/Users/<USER>test/lsstsw/stack/DarwinX86/utils/9.2+8/python/lsst/utils/tests.py", line 328, in assertClose     testCase.assertFalse(failed, msg="\n".join(msg)) AssertionError: 1/5 elements differ with rtol=1e-14, atol=2.22044604925e-16 2.44929359829e-16 != 1.13310777953e-15 (diff=8.881784197e-16/1.13310777953e-15=0.783842839795)  ---------------------------------------------------------------------- Ran 7 tests in 0.131s  FAILED (failures=1) {code}  ===============  More info on pugsley.ncsa.illinois.edu:   pugsley:lsstsw <USER> sw_vers  ProductName: Mac OS X  ProductVersion: 10.9.5  BuildVersion: 13F34   pugsley:lsstsw <USER> clang -v  Apple LLVM version 5.1 (clang-503.0.40) (based on LLVM 3.4svn)  Target: x86_64-apple-darwin13.4.0  Thread model: posix  ============  The files are in {{/Users/<USER>test/lsstsw/build/shapelet/}}.
Answer: 3727.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: "/nfs/lsst2/lsstsw-backup contains a backup of ~lsstsw, that I made while merging and deploying DM-1062. Once it's determined the merge didn't break anything, delete this backup."
Answer: 2534678.0

User story: "Once the API is designed and signed off on, the API will need to be implemented and tested.  This will require updating all obs_* packages that use the current interface."
Answer: 298253.0

User story: "The API will have to be able to accommodate data we know about, so will need to deal with reasonable missing data.  It should also not preclude extension.  This will need to be RFC'd since it is an API change."
Answer: 214526.0

User story: "We will need to run the tool in the camera team's system to make sure the interfaces are as they expected.  It will also help to make sure that the tool addresses all of the cases."
Answer: 168335.0

User story: "Implement the tool to generate the camera object.  It should be a command line tool that will take a path to a file.  It should have an option to persist the generated camera.  It should also have the ability to plot the camera."
Answer: 207430.0

User story: "The headers will need to be vetted against known FITS standards.  The headers should be valid and should not contain any non-standard keywords.  There should also be a census of FITS standards that may be used for defining sensor layout."
Answer: 37167.0

User story: "We should first sit down with a Camera team rep (Jim C. maybe) to define the tool they need.  How dynamic are the data?  What is the layout of the data?  We should also get some example test data to work with."
Answer: 30207.0

User story: "Implement the designed tests with the installed data."
Answer: 69049.0

User story: "Design the tests that should be done: how are calibrated frames compared, how are output catalogs compared.  Insert identified data in appropriate locations (camera in obs_test for example).  Work moved into DM-1293"
Answer: 44790.0

User story: "To test processCcd we need to identify a set of data to process (possibly mocked).  This implies that there will also need to be a minimal camera to go with the minimal data.  This task is to identify the minimal data and find a location for it."
Answer: 40295.0

User story: "Re-cast SWUG as a Sphinx document to explore migration to this utility for DM documentation. Describe issues with conversion, weaknesses and strengths of Sphinx as an authoring tool for user-facing documents. Full integration with the DM Stack source documentation will require a tool such as Breathe. "
Answer: 2291296.0

User story: "Often when I create a ticket JIRA has just the component I want, I press tab to accept it and continue writing my ticket, but at the end my attempt to Create the ticket fails with a complaint that the component does not exist. It certainly does exist. I'm not sure what the problem is -- maybe JIRA is adding an extra whitespace or something. Whatever it is, it is very frustrating. I have to keep trying to enter the component until JIRA will take it."
Answer: 695753.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: "bin/rebuild uses flock, which is not available on MacOS. This prevents lsstsw from being used for a MacOS buildbot.  Presumably one can use shlock (which is available on MacOS) or python's flock implementation instead. But...  I confess I'm still not sure why this lock is useful. If the idea is to prevent different builds from colliding for a shared stack, then surely eups locks are more important that this flock, since one can build in several different ways, and this flock only prevents building by lsstsw? If only lsstsw users see a stack then flock will be reliable, but as far as I know that does not apply to buildbot at this time. Even if it did apply to buildbot, I would think buildbot would prefer not to even attempt to launch two instances of lsstsw at the same time.  On the other hand it's not worth over-thinking this because lsstsw not intended to be used long-term. So a quick fix is probably fine."
Answer: 6529.0

User story: "In-place build is available and documented."
Answer: 10106.0

User story: "Instances of worker jobs might ask the Archive DMCS which distributor to connect to, only to connect to that distributor which has recently been rebooted, so the distributor might not have that information.   At this point, the Distributor could send an “expired” notice of some kind to the Archive DMCS to clear it’s cache, and also tell the worker that it has no file of the type it’s looking for.  The worker would then go back to the Archive DMCS. "
Answer: 37169.0

User story: "Adjust configuration parameters of HTCondor config and/or submission files to improve speed at which HTCondor jobs start in both the replicator pool and worker pool."
Answer: 8333.0

User story: "Schema aliases should support more than one level (i.e. an alias may resolve to another alias)."
Answer: 18651.0

User story: Delimiters in Schema field names are version-dependent.  One can currently use {{schema["a"]["b"].getPrefix()}} to join fields using the appropriate delimiter, but this is confusing to read.
Answer: 246.0

User story: "The ResultMapper classes in meas_base should inherit from FunctorKey, and support bidirectional transfers involving the Result structs and records."
Answer: 79183.0

User story: "Deliverable: security plan Ephibian 10% "
Answer: 108463.0

User story: "Deliverable: completed governance of security plan for review Petravick D 10% "
Answer: 7474.0

User story: "Creation of qserv_distrib and distribution of Qserv via official LSST repositories have to be taken into account in Qserv documentation and automatic install script."
Answer: 12739.0

User story: "Integrate prototype v1 with Fermi's DataCat (e.g., reuse logic for reading headers using afw, store in DataCat). Experiment with foreign tables."
Answer: 162720.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 first prototype will involve capturing metadata from a small set of image files. * Create a new schema file in the cat package (lsstSchema4mysqlW15.sql) with definition of tables that will be used to capture image metadata (see Exposure tables in other schema files), and some basic structure for capturing information about the entire repository. Decide which keywords are standard, and which should go to flat key-value area * Pick a directory (or several) with images, candidates: /lsst7/dr7/runs, /lsst7/releaseW13EP, /lsst3/DC3/data/obs/ImSim/pt1_2, /lsst/DC3/data/pt1.2.3k/datarel/ImSim * create test database, load schema * extract metadata for all images in a given directory and load metadata from fits headers."
Answer: 89033.0

User story: "Research potential off-the-shelf candidates. Propose initial version of metadata design. "
Answer: 70672.0

User story: "The goal of this ticket (and DM-1250) is to try to understand what kind of per-query metadata is necessary to provide client-transparent query processing in case when czar/proxy could die or be restarted.  Some relevant info is in the Trac: https://dev.lsstcorp.org/trac/wiki/db/Qserv/CSS/RunTimeState"
Answer: 41805.0

User story: "Transient cache for CSS, populated from python, no C++ interface to zookeeper. Pack multiple keys using json. Tenative packing spec is in DM-705  The v1 implementation transitions the zk access from the c++ layer into python, with code that understands how to unpack json-encoded data. This can coexist with the existing qserv_admin zk schema. v2 applies packing/unpacking logic in the creation/manipulation code in qserv_admin. "
Answer: 44658.0

User story: lsst_build prepre.py VersionDbGit.commit sets a local variable named dirty, which is ignored. Other methods set self.dirty; is that what "commit" should also be doing? 
Answer: 2520520.0

User story: "We now have a package called qserv_distrib, which depends on qserv and qserv_testdata, (see DM-1147 for details), so buildbot should build that, instead of qserv. Thanks."
Answer: 13698.0

User story: "sciSQL plugin is currently deployed in eups stack (i.e. $MYSQL_DIR/lib/plugin) during configuration step. Nevertheless eups stack should be immutable during configuration step.  MySQL plugin-dir option may allow to deploy sciSQL plugin outside of eups stack (for example in QSERV_RUN_DIR)."
Answer: 29013.0

User story: "sciSQL plugin undeployment procedure doesn't remove scisql and scisql_test databases, and its shared lib (libscisl-*-.so) from plugin directory."
Answer: 2451459.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: Using eups makes it hard to use {{man}} command (this is on NCSA cluster machines): {code} $ source "/u2/<USER>STACK/eups/bin/setups.sh" $ setup xrootd $ man man No manual entry for man $ echo $MANPATH /u2/<USER>STACK/Linux64/xrootd/master-g2798bbf748/share/man:/u2/<USER>STACK/Linux64/git/1.8.5.2/share/man {code}  It looks like for {{man}} to find system man pages {{$MANPATH}} needs to contain empty path (meaning extra colon like {{/whatever:}}). Would it be possible for eups to always add an empty path to {{MANPATH}} when doing {{setup}}? 
Answer: 138232.0

User story: There are a number of small issues with lsstsw running on MacOS X: - It tries to deploy the Linux version of anaconda - It goes into a seemingly infinite loop running "yes" while cloning each package - It does not correctly detect that all unit tests passed  In addition, there is a known problem that only buildbot can get simulation code from stash; other users should edit settings.cfg.sh in lsstsw to remove the SBASE entry from REPOSITORY_PATTERN. I don't propose to fix that (at least on this ticket), since the workaround is about as clean as any fix would be, and this package is supposed to be temporary.  The fixes are as follows: - lsstsw: I added code to bin/deploy on tickets/DM-1219 that detects Mac and downloads the Mac version of anaconda. - eups: the "yes" problem is a bug in eups. Mario will commit a fix. - lsst_build: build.py is mis-testing that 0 unit tests failed. I committed a fix on tickets/DM-1219.
Answer: 14921.0

User story: "We should be able to use multiple-aperture flux results in slots.  While this is technically possible already by setting specific aliases, it doesn't work through the usual mechanisms for setting up slots (the define methods in SourceTable and the SourceSlotConfig in meas_base).  After addressing this, we should remove the old SincFlux and NaiveFlux algorithms, as the new CircularApertureFlux algorithm will be able to do everything they can do."
Answer: 178851.0

User story: "meas_base currently has a single Swig library (like most packages), defined within a single .i file (like some packages).  It also registers all of its plugins in a single python module, plugins.py.  Instead, it should:  - Have two Swig libraries: one for the interfaces and helper classes, and one for plugin algorithms.  Most downstream packages will only want to %import (and hence #include) the interface, and having them build against everything slows the build down unnecessarily.  The package __init__.py should import all symbols from both libraries, so the change would be transparent to the user.  - Have separate .i files for each algorithm or small group of algorithms.  Each of these could %import the interface library file and the pure-Python registry code, and then register the plugins wrapped there within a %pythoncode block.  That'd make the implementation of the algorithms a bit less scattered throughout the package, making them easier to maintain and better examples for new plugins."
Answer: 55528.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: "Calling afw.image.makeMaskedImage leaks memory when called from Python, because it returns a raw pointer without telling Swig %newobject.  To fix it, it'd be better to just have it return by value instead of by pointer, though this might involve fixing some downstream C\+\+ code (Python code should not be affected)."
Answer: 110945.0

User story: We are using anaconda 1.8.0 which doesn't ship with PyQT4 (2.0.1 does, which is, I think, the latest).  This prevents us from running ginga in an iPython notebook  This is a "minor" issue as we are not (yet?) using ginga, but the functionality is sufficiently interesting that I think we should consider it as  a consideration when deciding whether to upgrade anaconda.
Answer: 152992.0

User story: We want: * header for the class * then system * then third party * then lsst * then qserv  We currently don't have the "lsst" group (with a few exceptions), and we call the last one "local" in most places.
Answer: 161261.0

User story: The version of anaconda distributed with the stack is too outdated to be used with pip (and probably other things). The issue is an unsafe version of ssh.  A workaround is to issue this command while anaconda is setup: {code} conda update conda {code} Warning: it is unwise to try to update anaconda itself (with "conda update anaconda") because that will revert some of the changes and may result in an unusable anaconda.  I think what is required is an obvious change to ups/eupspkg.cfg.sh  The current version of anaconda is 2.0.1 based on http://repo.continuum.io/archive/  Note: there is no component for anaconda. I will submit another ticket.
Answer: 153800.0

User story: "The XrdSsi API performs some impedance-matching in buffering transfers. The current code (introduced in DM-199) doesn't leverage this because its flow model is based on the older mysqldump-based results passing. With dump files, we don't know the size of the fragments expected, so we are just passing buffers of bytes and building up a text blob to ingest. With the row-based protocol, we have sizes specified, hence the receiver can specify exactly what sizes of bytes are needed. Implementation of this ticket should simplify and reduce the code overall. "
Answer: 50396.0

User story: "sconsUtils has nominal support for C++11 but it needs some work including: - It should set CXXFLAGS not CCFLAGS when it sees --c++11 - It should check gcc version number and specify -std accordingly. In gcc 4.7 -std=c++0x triggers C++14 support, but gcc 4.4 does not support -std=c++11."
Answer: 1670.0

User story: "It would be handy to be able to specify flags to scons when triggering a buildbot build. Occasionally we want to test a variant build (e.g. C++11).  One subtlety is that all packages will have to be rebuilt if any such flags are specified (for user-triggered builds buildbot tries to reuse existing packages when it can, and that would not be acceptable in this situation)."
Answer: 1253341.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: "Migrate the Trac documents on DM Coding Style Policy (https://confluence.lsstcorp.org/display/LDMDG/DM+Coding+Style+Policy) as well as the top-level Standards and Policies page (https://confluence.lsstcorp.org/display/LDMDG/Standards+and+Policies) to to the DM Developer Guide. "
Answer: 66182.0

User story: "Migrate the content of the LSST Python Coding Standard from its location on the Trac/Wiki (https://dev.lsstcorp.org/trac/wiki/PythonCodeStandards) to the DM Developer Guide (https://confluence.lsstcorp.org/display/LDMDG/Python+Coding+Standard). The current draft version is 3.0, which was reviewed by the SAT before it can be declared official. Oddly, the Python 2->3 migration page was never incorporated into the standard; it should appear in a new subsection (Python 3 Idioms). "
Answer: 125099.0

User story: "Migrate the content of the LSST C++ Coding Standard from its location on the Trac/Wiki (https://dev.lsstcorp.org/trac/wiki/C%2B%2BStandard/References) to the DM Developer Guide (https://confluence.lsstcorp.org/pages/viewpage.action?pageId=16908666). The current draft version is 1.6, which apparently needs further review by the SAT before it can be declared official. "
Answer: 708449.0

User story: So having had the quote-unquote-fun of trying to troubleshoot something that I triggered on a known Tucson timescale, on a machine running on CDT, with a log timestamped in GMT....  May I propose that all our timestamping and machine times are set to a single timezone?  To first order I don't care what it is.  To second order, I have a mild preference for Pacific, since I already have to keep it in my head due to it being "Official Project Time" and it means it will be equivalent to local for a lot of people for half the year. But really, Zulu time is fine, just... pick one. 
Answer: 106547.0

User story: "the unit tests in ctrl_events do not use unique topics, which can lead to unpredictable failures.  Also (and I'll be happy to split this into a separate ticket, if desired), the unit tests do not use the unit test framework. The tests would be easier to read and the test results easier to understand if they did. Better yet, many unit tests could be combined into a smaller number of tests.  Finally, a minor point, but many tests import packages they don't use. I recommend running the code through a linter."
Answer: 2686.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: Once a qserv run directory is created with its templated config file, it is frozen to the qserv version currently "setup" in eups via hardcoded paths in various scripts located in the run directory.  * It is unclear whether these scripts will work if another qserv eups-version is "setup". Are they tied to the particular directory, regardless of eups state? IOW, can the run directory be used without "source loadLSST.sh", provided the files are not touched?  If so, great! But the run directory should record which versions it was frozen with.  * If use of the run directory still requires the eups environment variables, then it should not be hardcoded with paths--it should switch versions if "setup" is called to change qserv versions. Arguably, this is dangerous, but it is only as dangerous as using existing data with new software, which for development, is extremely useful.
Answer: 745714.0

User story: "https://dev.lsstcorp.org/cgit/LSST/DMS/ip_isr.git/tree/examples/exampleUtils.py#n95 Says that the read corner is in assembled coordinates.  This is not true, it is in the coordinates of the raw amp.  That is, if the raw amp is in electronic coordinates (like the lsstSim images) it is always LL, but if it is pre-assembled, it may be some other corner.  This should probably use the methods in cameraGeom.utils to do the image generation."
Answer: 59060.0

User story: "The bounding box of the prescan region in the megacam camera should have zero y extent (I think).  Instead it goes from y=-1 to y=2.  This is either a bug in the generation of the ampInfoTables or in the way the bounding boxes are interpreted."
Answer: 28649.0

User story: "There's a teleconference in October with Gregory about the visualization requirements.   This is a fact gathering meeting to decide what hardware to support these requirements.  (tiled displays, etc).  IPAC is doing the software for this."
Answer: 1974130.0

User story: "As recommended by the SAT meeting on 2014-09-16, we need this document to promote the use of GitHub by other subsystems within the project."
Answer: 1604615.0

User story: "I missed the GitHub review comments from Paul.  I have other cleanup tasks to do during this Sprint, and will do all of these fixes this week.  Will checkin to this issue when they are all done."
Answer: 96519.0

User story: The "publish" script in ~lsstsw/bin will currently happily overwrite existing eups tags, for example, by running "./bin/publish \-b b245 \-t current qserv" I managed to destroy existing "current".  It'd be good to prevent that from happening, or adding guard (--forceOverwrite flag maybe?) if we need to allow it in some special circumstances.
Answer: 2529774.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: "While trying to track down some bugs on DM-641, I've grown frustrated with the difficulty of testing the deeply-buried (i.e. interfaces I want to test are private) shapelet evaluation code there.  That sort of code really belongs in the shapelet package (not meas_multifit) anyway, where I have a lot of similar code, so on this issue I'm going to move it there and refactor the existing code so it all fits together better."
Answer: 8747.0

User story: "I propose we:  * permit rebasing of tickets/DM-NNNN branches, once a gitolite hook designed to save the old branch (developed in DM-78) is finalized and deployed.  * require that, if needed, tickets/DM-NNNN branches are rebased to comply with DM-1181 and DM-1182 guidelines on commits and commit messages AND make the assessment/enforcement of compliance a part of the code review."
Answer: 34462.0

User story: The question of what makes a "good commit message" occasionally comes up. I feel that this document:    http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html  presents a reasonable set of guidelines and I propose the SAT adopts it as a part of our software development standards.
Answer: 31887.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: Working on DM-1005 I found that initialization of log package causes me a lot of trouble. I hope we can improve that.  Currently log can be initialized in one of the following ways: - calling {{LOG_CONFIG(file_name)}} where file name has to be passed somehow to the initialization code, configures loggers according to given config file -  calling {{LOG_CONFIG()}} defines some basic configuration which kind of works but isn't usually what I want - not calling any of the above but setting environment variable {{LOG4CXX_CONFIGURATION}} to a config file name, which is equivalent to first option (this may not be intended use case but it works now) - if I don't do any of the above then log4cxx prints error messages and disables logging completely  Our use cases for log may be non-conventional but I have to implement them anyways. There are basically two cases where I have troubles: - plugins for xrootd (implemented as libraries), these do not have a simple way to pass configuration file name except through environment variable, I could use {{LOG4CXX_CONFIGURATION}} for that (without calling {{LOG_CONFIG()}} but I also want to produce reasonable output when I forget to set {{LOG4CXX_CONFIGURATION}}. Another complication is that there may be more than one plugin loaded at the same time, deciding which one has to initialize logging is complicated. - a (potentially large) number of unit tests. We could add {{LOG_CONFIG()}} to each one of them but I'd like to avoid that for a number of reasons.  So I think what I'd like to have is an option to not call {{LOG_CONFIG()}} which would still produce reasonable output even without {{LOG4CXX_CONFIGURATION}} (in other words make call to {{LOG_CONFIG()}} implicit). But I would also like to be able to change logger configuration via {{LOG4CXX_CONFIGURATION}} when {{LOG_CONFIG()}} is called (explicitly or implicitly).  I propose to modify log to do following: - any call to logger methods implicitly initializes it (via call to {{LOG_CONFIG()}}) if it has not been initialized. - if {{LOG_CONFIG()}} is called without file name and {{LOG4CXX_CONFIGURATION}} is set then it should be equivalent to {{LOG_CONFIG(getenv("LOG4CXX_CONFIGURATION"))}}   Objections, suggestions?
Answer: 7132.0

User story: "After DM-840 is finished, and code updated for it (DM-846), make the new default image origin PARENT, remove the UNDEFINED image origin enum, and update at least some of the code that explicitly specifies PARENT (there is little harm in leaving this explicit, other than it does not set an optimal example)."
Answer: 17481.0

User story: "Especially, move all DM Integration Complete trigger dates from 3/19 to 9/19."
Answer: 2325505.0

User story: "- stdout, stderr output should be colorized, whereas redirecting it into a file shouldn't."
Answer: 2558381.0

User story: "The test programs in core/modules/css/ has hardcoded zookeeper port numbers. That needs to be fixed, it needs to be configurable."
Answer: 470972.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: "Hello Mario,  DM-602 allows to install Qserv from a local distribution server. This is useful for cluster installation which is often performed on internet-free machines.  Nevertheless, one of our requirement is that anonymous user can easily download distribution data from the distribution server, in order to setup a local distribution server (for example on a cluster shared filesystem).  The current solutions don't satisfy this :  - rsync require an account on lsst-dev - wget and curl can't easily  download recursively the content of a directory, and doesn't cover synchronisation - tarball (our current solution), doesn't cover synchronisation  A proposal is to set-up a read-only anonymous rsync account on lsst-dev.ncsa.illinois.edu which would allow anonybody to synchronize easily distribution data.  Would it be possible please, ot would you have a better solution ?  Thanks,  Fabrice"
Answer: 2319347.0

User story: "While test coverage isn't complete, there are many unit tests for measurement plugin algorithms in meas_algorithms that have not yet been ported to meas_base.  We should make sure any of these tests that aren't already covered in meas_base are moved over before we remove the meas_algorithms versions of things."
Answer: 88337.0

User story: "We should do a comprehensive cleanup of the SdssShapeAlgorithm class.  This includes removing the SdssShapeImpl interface (never supposed to have been public, but it became public) from other code that uses it, and integrating this code directly into the algorithm class.  We should also ensure that the source from which the algorithm is derived is clearly cited -- that's Bernstein and Jarvis (2002, http://adsabs.harvard.edu/abs/2002AJ....123..583B); see also DM-2304."
Answer: 302613.0

User story: "Define the APIs for image query with database group.   Depend on the implementation of APIs  Exercise the image cutout service DM-1977 been developed in SLAC.     "
Answer: 1141449.0

User story: "- on lsstsw master branch tip, ./stack/Linux64/lsst/9.2/bin/newinstall.sh doesn't seems to be the last version (it still install eups-1.3.0 instead od eups-1.5.0)   - on Fedora19, flock from util-linux 2.23.1 doesn't support next options : {code:bash} $ flock -w 0 200 flock: timeout cannot be zero {code} but {code:bash} flock -w 1 200 {code} works,  - newinstall.sh : would it be possible to enable automatic answers to git and anaconda install questions. For example, in order to easily enable automatic install on 300 nodes clusters ? (cancelled : covered by DM-1078)  - loadLSST.sh appends automatically http://sw.lsstcorp.org/eupspkg to EUPS_PKGROOT, and if first url in EUPS_PKGROOT isn't available eups fails without trying next ones => this isn't compliant with offline mode and introduce a work-around in Qserv offline mode install scripts. Would it be possible to define a lightly different behaviour for loadLSST.sh ?  - In newinstall.sh, l. 167, if Python version isn't correct, then exit *with error code*. "
Answer: 772313.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 zookeeper client in C++ that the czar uses doesn't auto-reconnect. This is a capability provided in the kazoo library that qserv's python layer provides, but isn't provided in the c++ client.  The zookeeper client disconnects pretty easily: if you step through your code in gdb, the zk client will probably disconnect because its threads expect to keep running. zk sessions may expire too. Our layer should reconnect unless there is really no way to recover without assistance from the calling code (e.g. configuration is wrong, etc.).  This ticket includes only basic reconnection attempting, throwing an exception only when some "reconnection-is-impossible" condition is met.
Answer: 8925.0

User story: "Currently the example of the IsrTask takes a fake dataref.  This is hard to use with real data.  In DM-1113 we will update IsrTask to not take a dataRef.  This will make it easy to update the example script to work with real data.  This ticket will also include removing from the unit tests any fake dataRefs that have become unnecessary as a result of DM-1299.  "
Answer: 352829.0

User story: "A lot of users will search for images using some (often advanced) spatial criteria. Need to implement something similar to what we have in UDFs/SciSQL to efficiently support this class of search. Check GIS support in MariaDB"
Answer: 484301.0

User story: "qserv_distrib will be a meta-package embedding qserv, qserv_testdata and partition."
Answer: 37774.0

User story: "Run driver from DM-1133 on simulations from DM-1132 with different configuration for shapelet PSF approximation, increasing complexity until change in shear estimate drops below a TBD threshold."
Answer: 815064.0

User story: "Using simulations built on DM-1132 and driver code from DM-1133, test different pixel region sizes and shapes, and determine at what point shear bias due to finite fit region drops below a TBD threshold."
Answer: 576056.0

User story: "We'll need driver code to run the galaxy fitting algorithms on the simulations from DM-1132.  Efficiently saving all the samples could be challenging."
Answer: 484735.0

User story: "Using the PSF simulations generated in DM-1131 and the GalSim package, generate ~20k galaxies for each of 3 shear values for each input PSF.  Will need to be divided into subtasks - figure out what the outputs should look like, write the code to generate the simulations, estimate the time need to run the simulations, run the simulations at scale, etc. "
Answer: 356837.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "To determine the number and order of shapelet expansions needed to approximate the LSST PSF, we need simulations of LSST PSFs, presumably generated using PhoSim.  I think we want something like 50-100 extremely high-SNR stars, drawn from realistic distributions of anything that would affect the PSF, including position on the focal plane and center position within a pixel.  I only care about getting these out as postage stamps, so I'll leave the question of how best to run PhoSim to get these up to someone else.  While this is part of a mostly-Princeton Epic, I'm assigning this issue to Simon as he'd be able to do it much faster than I could.  I'll also let him review and update the story points estimate."
Answer: 356731.0

User story: "Using one of the prototypes of DM-828, refactor the C++ Algorithm code in meas_base and any other packages."
Answer: 139447.0

User story: "Implement span-based overlap tests and spatial union, intersection, and difference operators for Footprints.  Should be split into subtasks; first task would be to come up with the interface, and then each operation to be implemented should have one subtask each.  If complete after DM-1126 and DM-1127, these operations should be implemented in the SpanRegion class, and Footprint should delegate to that."
Answer: 1027736.0

User story: "The current grow operation for Footprints is very inefficient for isotropic grows.  A better algorithm can be found in the attached paper."
Answer: 125047.0

User story: "This issue is the implementation for DM-1126, including fixing code broken by the API changes.  This issue should be given subtasks for discrete pieces of work as part DM-1126, as it has a lot of story points.  Because it's likely all of this needs to be merged at the same time, it should probably be done on a single branch, unless some of the earlier work can be done in a backwards-compatible way.."
Answer: 525163.0

User story: This issue is for *planning* (not implementing) some changes to Footprint's interface, including the following:  - make Footprint immutable  - create a separate SpanRegion class that holds Spans and provides geometric operators does not hold Peaks or a "region" bbox (Footprint would then hold one of these).  - many operations currently implemented as free functions should be moved to methods  - we should switch the container from vector<PTR(Span)> to simply vector<Span>, as Span is nonpolymorphic and at last as cheap to copy as a shared_ptr.  The output of this issue will be a set of header files that define the new interface, signed off by an SAT design review.  Other issues will be responsible for implementing the new interface and fixing code broken by the change.
Answer: 305329.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: "At least one of the star selectors uses the old measurement framework system to measure the moments of a cloud of points.  With the new versions of all the measurement plugins, it should be much easier (and cleaner) to just call the SdssShape algorithm directly, instead of dealing with the complexity of applying the measurement framework to something that isn't really an image."
Answer: 204848.0

User story: "Using the interface defined in DM-740, implement a Chebyshev-based implementation to be used to interpolate aperture corrections across CCD-level interfaces.  A prototype is available on the HSC fork, which can be copied directly, modulo any interface changes on DM-740.  For more information, see the HSC Jira issue (which also includes the work associated with DM-740): https://hsc-jira.astro.princeton.edu/jira/browse/HSC-796 and the HSC git commits https://github.com/HyperSuprime-Cam/afw/compare/releases/S14A_0...tickets/DM-796"
Answer: 463897.0

User story: "Eups is exhibiting a slowdown due to the rapidly increasing number of eups-versioned packages being maintained by it.  It has been suggested that, for the short term, the buildbot system create a periodic purge of eups tags associated with user branches (for those would considered too old for debugging use).  A longer term solution will be having separate build structures for mainline builds and user builds."
Answer: 2863032.0

User story: "DM-70 was merged before its code documentation was completely ready, in an effort to not leave such a large amount of code un-merged.  This ticket exists as the second half of DM-70 to clean up its documentation."
Answer: 56370.0

User story: "After the new unit test data package is available, we should convert all tests that currently use afwdata or obs_test to use the new package instead, and then remove obs_test and afwdata.  Should have subtasks and a re-estimate of effort after auditing how much there is to be done."
Answer: 2620226.0

User story: "We need a custom mapper for the test data package, so we can run unit tests against it without depending on any particular obs_* package."
Answer: 2620228.0

User story: "Write scripts to generate the test data (as needed) and run them."
Answer: 2620229.0

User story: "Gather requirements for unit test datasets and determine how to organize and generate the data."
Answer: 2620229.0

User story: "Add functionality to the mapper base class to support input datasets from a database.  A prototype will be delivered in S14."
Answer: 57359.0

User story: "Add functionality to the mapper base class to support calibration rendezvous.  A prototype will be delivered in S14."
Answer: 57359.0

User story: "Add functionality to the mapper base class to support registry-based input directories.  A prototype will be delivered in S14."
Answer: 57359.0

User story: "Add functionality to the mapper base class to support input directories with path templates and without registries.  A prototype will be delivered in S14."
Answer: 57360.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: "Implement the new butler interface, including a mapper base class that supports single input files and output path templates.  A prototype will be delivered in S14."
Answer: 57359.0

User story: "Describe the interface and high-level implementation. Have the SAT review it."
Answer: 6.0

User story: "This task is to create a tutorial that shows how to generate QA plots for processed datasets. Ideally it will use existing pipeQA software, or borrow from it. The intended audience includes both scientists with real datasets, and developers who want to evaluate the quality of the algorithms. "
Answer: 3152803.0

User story: "A basic description of measurement in the LSST Stack was created for the SWUG (see DM-692). However, this chapter lacks specifics about how the measurement algorithms work and does not yet mention some of the available algoritms. This task is intended to provide the next level of detail, with references to source-level descriptions that exist or are in progress. "
Answer: 2335800.0

User story: With default settings we do not have good visibility as to whether an updated ClassAd on a compute node (e.g., CacheDataList now has ccd "S00") will be in effect on the submit node in time for a Job to be matched to an optimal HTCondor node/slot.   There are several components (negotiator, schedd, startd) and their associated activities that could impact the time that it takes for a new ClassAd on a worker node to 'propagate' back to the submit side. We investigate these configuration settings to try to determine what thresholds for configuration settings are required to meet a given time cadence of job submissions.
Answer: 33.0

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

User story: "The benchmark file for the summer2012 demo is generated on  RHEL6. When using the dataset to compare stack output generated on Mac OSX 10.8.5 (and 10.9)  there are significant deviations.   Find out where the problem arises...in the stack during processing or in the comparison."
Answer: 222577.0

User story: "The DMS and Astro Glossaries in Confluence define a set of technical terms used in their respective domains. Some of the definitions are placeholders, and other terms used in the SWUG, DM Space, and DM Developer Guide have yet to be defined in one glossary or the other. It is time to update these docs."
Answer: 38374.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: "As discussed in the SAT call 2014-08-19  The problem is alerting stack users to potentially missing assumed third party dependancies. (The example was DS9). Robert The Good said he had a config-time checker that he could ressurect to check for third-party dependancies.   Robert said:  The configure stuff is in  <EMAIL>:LSST/DMS/devenv/lsst but may be/probably is very out of date.  I'll have a look at it and (a) add DS9 check (b) check with Dick in case he needs to document any extra steps. "
Answer: 2336819.0

User story: "This example fails with an exception: {code:py} import lsst.afw.table as afwTable schema = afwTable.SourceTable.makeMinimalSchema() st = afwTable.SourceTable.make(schema) cat = afwTable.SourceCatalog(st) tmp = afwTable.SourceCatalog(cat.getTable()) cat.extend(tmp) {code}  Expected behavior is that the last line is equivalent to {{cat.extend(tmp, deep=False)}}."
Answer: 203393.0

User story: "Augment the SWUG chapter on Key LSST Data Concepts with a high-level description of the data products that are generated in production processing. The emphasis will be on data products that are produced with the current Stack, with only a lightweight summary of products that are anticipated in future releases. "
Answer: 2354673.0

User story: "The tutorial on Processing SDSS Images in the SWUG is almost self-contained, apart from access to the database server at NCSA to:   - query the SeasonFieldQuality table - ingest processing metadata and source measurements  This can be solved by providing basic instructions for users to install (or access an existing) DB server, and by providing a mechanism for users to download and import the SeasonFieldQuality table. "
Answer: 2337179.0

User story: "There are various examples of using afw for analysis tasks, many in PowerPoint slides. A select few (image display and annotation, constructing color-color plots of source catalogs) would be much more useful to users in the form of iPython notebooks. This task is to craft two examples, assemble the supporting data that would be needed, and add them to the SWUG. "
Answer: 2337186.0

User story: "The DM Developer Guide is presently a place-holder for information relevant to developers. It is time to re-organize the content, and to provide authoritative guidance to developers. This will involve contributions from various members of the DM Team, and likely some selected harvesting of the Trac/Wiki. "
Answer: 38810.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: Audit TCT recommendations to ensure that all standards updates were installed into Standards documents.  It was found that the meeting recorded in: [https://dev.lsstcorp.org/trac/wiki/Winter2012/CodingStandardsChanges] failed to include two recommendations:   * recommended: 3-30: I find the Error suffix to be usually more appropriate than Exception. ** current: 3-30. Exception classes SHOULD be suffixed with Exception.  * recommended but not specifically included: Namespaces in source files: we should use namespace blocks in source files, and prefer unqualified (or less-qualified) names within those blocks over global-namespace aliases. ** Rule 3-6 is an amalgam of namespace rules which doesn't quite have the particulars desired. FYI: The actual vote was to:  "Allow namespace blocks in source code (cc) files."  To simplify the future audit, all other recommendations in that specific meeting were verified as installed into the standards.
Answer: 122551.0

User story: "Most afw::table unit tests explicitly set version 0.  We should change these to test the new behaviors, not the deprecated ones."
Answer: 305440.0

User story: "At the end of the buildbot failed message these lines appear: {quote} *** error building product afw. *** exit code = 1 *** log is in /lsst/home/lsstsw/build/afw/_build.log *** last few lines: :::::  + echo '*** Failed unit tests.' :::::  *** Failed unit tests. {quote}  This is not true.  As Robyn points out, the correct location of these files is implied by statements at the top of the message: {quote} Failed Package Info at lsst-dev.ncsa.illinois.edu:/lsst/home/lsstsw/build/FailedLogs/328/ .......Log */_build.log {quote} by which is meant {quote} dev.ncsa.illinois.edu:/lsst/home/lsstsw/build/FailedLogs/328/afw/_build.log {quote}  It'd be nice if this were a little more explicit."
Answer: 1201522.0

User story: "After meas_base has been fully integrated, remove the old forced photometry tasks from pipe_tasks"
Answer: 299273.0

User story: "We have multiple algorithms in meas_base which could be used in forced mode but have no forced plugin.  We should go through the algorithms we have implemented and create forced plugin wrappers for these."
Answer: 47523.0

User story: "We should set the default measurement task in ProcessImageTask to SingleFrameMeasurementTask, and note that SourceMeasurementTask and the old forced photometry drivers are deprecated."
Answer: 64380.0

User story: "Now that all tasks that use catalogs explicitly set the table version, it should be relatively straightforward to set the default version to 1 in afw.  Code that cannot handle version > 0 tables should continue to explicitly set version=0."
Answer: 23236.0

User story: "Check that meas_base plugins and algorithms have appropriate config options and flags (mainly, check that there are no unused config options or flags due to copy/paste relics)."
Answer: 190419.0