udaykiran19491/user-stories-from-tawos-for-llm-fine-tuning huggingface dataset:
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "We should move the code in the algorithms subdirectory (and namespace) into the .cc files that correspond to individual algorithms.  They should generally go into anonymous namespaces there.  After doing so, we should do one more test to compare the meas_base and meas_algorithms implementations."
Answer: 43367.0

User story: "The meas_base version of SdssShape produces slightly different outputs from the original version in meas_algorithms, but these should be identical.  We should understand this difference rather than assume its benign just because it's small."
Answer: 46137.0

User story: SubSchema didn't get included in the rest of the switch from "." to "_" as a field name separator.  As part of fixing this, we should also be able to simplify the code in the slot definers in SourceTable.
Answer: 11336.0

User story: "DS9 is being used in examples illustrating the use of DM Releases.  DS9 was formerly considered a developer-only 3rd party tool and not bundled in a release. Nor was it included in the DM Copyright statement listing the 3rd Party Tools required.  Dick raises the question whether it needs to be promoted in status  or just mentioned as a potentially useful user-supplied tool."
Answer: 171198.0

User story: "The config file for the qserv czar has some items that are no longer relevant, and in this issue, we focus on the ones that are clearly the responsibility of our qserv css.  This ticket includes: -- removing these items from the installation/configuration templates -- removing these items from sample configuration files -- removing these items from the code that reads in the configuration file and sets defaults for these items -- fixing things that seem to break as a result of this cleanup.  <USER>volunteers to assist on the last item, as needed.  "
Answer: 51765.0

User story: "With the addition of log we now need to find some shared libraries from stack. Current version of qserv-czar init.d script does not capture LD_LIBRARY_PATH, so we should add it there. "
Answer: 23.0

User story: LSST C++ components are being built without optimisation because of a bug in eupspkg which is triggered by an existing {{SCONSFLAGS}} environment variable that doesn't activate optimisation (e.g., no {{opt=3}}).  Specifically, eupspkg contains the line:  {code:sh} export SCONSFLAGS=${SCONSFLAGS:-"opt=3"}        # Default scons flags {code}  My {{SCONSFLAGS}} is already set (to {{-j 2 cc=clang}}, as I believe we recommend, or used to recommend, for Mac builds).  So the result of this line is that {{SCONSFLAGS}} is unchanged, which means optimisation isn't activated for the build.  An expression that always activates optimisation (which is what one wants for a production build) would be something like:  {code:sh} export SCONSFLAGS+=" opt=3" {code}  Once this is fixed, a new release should be made.
Answer: 775572.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: "CalibrateTask does some unexpected things differently if you configure it certain ways, because it perceives certain processing as only being necessary to feed other steps.  In particular, if you disable astrometry and photometric calibration, it only runs measurement once, because it assumes the only purpose of the post-PSF measurement is to feed those algorithms.  This (as well as poor test coverage) made it easy to break CalibrateTask in the case where those options are disabled a few branches back.  After conferring with Simon and Andy, we think the best solution is to remove this sort of conditional processing from CalibrateTask, which should also make it much easier to read.  Instead, we'll always do both the initial and final phase of measurement, even if one of those phases is not explicitly being used within CalibrateTask itself."
Answer: 81443.0

User story: "We started adding a system to allow algorithms to declare what kind of data they can run on, but never really put it in place.  To do this, we should:  - Add more flags (at least NO_CALIB).  - Pass these flags in pipe_tasks and other places with tasks that use measurement tasks as subtasks (for instance, we should set NO_WCS and NO_CALIB during calibrate.initialMeasurement, and COADD in processCoadd).  - Add checks for these flags in appropriate algorithms.  For instance, PsfFlux should fail in construction if NO_PSF is set, and PeakLikelihoodFlux should fail if PRECONVOLVED is not set."
Answer: 153883.0

User story: "This came up during migrating qserv to the new logging system, and it can be reproduced by taking log4cxx, see DM-983, essentially:  {code} eups distrib install -c log4cxx 0.10.0.lsst1 -r http://lsst-web.ncsa.illinois.edu/~becla/distrib -r http://sw.lsstcorp.org/eupspkg {code}  cloning log package (contrib/log.git), building it and installing in your stack, and finally taking the branch u/<USER>DM-207 of qserv and building it.  The warnings looks like:  {code}/usr/bin/ld: warning: libutils.so, needed by /usr/local/home/becla/qservDev/Linux64/log/1.0.0/lib/liblog.so, not found (try using -rpath or -rpath-link) /usr/bin/ld: warning: libpex_exceptions.so, needed by /usr/local/home/becla/qservDev/Linux64/log/1.0.0/lib/liblog.so, not found (try using -rpath or -rpath-link) /usr/bin/ld: warning: libbase.so, needed by /usr/local/home/becla/qservDev/Linux64/log/1.0.0/lib/liblog.so, not found (try using -rpath or -rpath-link) {code}  and they show up when I build qserv package, and are triggered by the liblog. I suspect sconsUtils deal with that sort of issues, but since we have our own scons system for qserv it is not handled. Fabrice, can you try to find a reasonable solution for that? Thanks!"
Answer: 8353.0

User story: "The use of random numbers in unit tests without seeding the RNG means the tests may not be deterministic."
Answer: 50525.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 should cleanup and simplify the GaussianFlux algorithm to simply use the shape and centroid slot values instead of either computing its own or having configurable field names for where to look these up."
Answer: 72285.0

User story: We need more detailed documentation for the GaussianCentroid algorithm, in terms of how it actually computes the centroid.  We (Jim and Perry) have done what we can, but we need help from whoever actually wrote it (RHL, we think) to provide the rest.  In particular:  - Additional detail should be filled in in the class Doxygen for GaussianCentroidAlgorithm, in GaussianCentroid.h  - The "noPeak" flag field description and name should be compared to what the algorithm actually does with it.  It looks to me like it's a bit misnamed (and maybe shouldn't be considered an error condition at all, if we want to run this on difference images), but I'm not sure.
Answer: 2440733.0

User story: "The classification algorithm claims it can never fail.  It can, and should report this."
Answer: 242269.0

User story: "SingleFrameSkyCoordPlugin is using the Footprint Peak, not the centroid slot.  According to comments in the code, this is a workaround for some problem with centroids.  This needs to be fixed."
Answer: 67658.0

User story: If we want to ultimately remove compound fields, we need to remove the "coord" field from the SimpleTable/SourceTable minimal schema, and provide a different way to get ra,dec from a source.
Answer: 528233.0

User story: "Some meas_base plugins still have old-style algorithm names."
Answer: 44970.0

User story: "See Description (it's currently called PsfMatch) "
Answer: 18721.0

User story: "It'd be good to check out Apache Mesos and Google Kubernetes and see how relevant they are for Qserv / LSST Database "
Answer: 851301.0

User story: "Rename local.qserv.cnf to qserv-czar.cnf. It is quite likely there are some other config files that would make sense to rename. If you see some candidates, let's discussion on qserv-l and do the renames."
Answer: 24720.0

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: 355405.0

User story: Testing workaround in meas_base which may be the cause for asemi-random failure in one of the unit tests.  Note: I wanted to test in a private u/rallsman/<xx> space but was unable to "git push origin u/rallsman/<xx>"  due to hook reject.  Note: I wanted to attach this Issue to the upcoming version 9.0 but was rejected since it wasn't pre-defined.
Answer: 103340.0

User story: I think the API for NoiseReplacer could be made more idiomatic (and possibly safer) by turning it into a "context manager" (i.e. so it can be used with the "with" statement).
Answer: 90801.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: "Slot config validation currently assumes that field names match plugin names, which is not always a safe assumption.  This can prevent certain algorithms from being used in slots.  We probably can't do this validation in Config.validate(); we need to check in the measurement Task constructor after the schema has already been constructed."
Answer: 239103.0

User story: "Currently, when I try to run qserv-benchmark but qserv_testdata was not setup, I am getting  {code} CRITICAL Unable to find tests datasets. -- FOR EUPS USERS : Please run :    eups distrib install qserv_testdata    setup qserv_testdata FOR NON-EUPS USERS : Please fill 'testdata_dir' value in ~/.lsst/qserv.conf with the path of the directory containing tests datasets or use --testdata-dir option. {code}  It is important to note in the section for eups users that this has to be called BEFORE qserv is setup, otherwise it has no effect. "
Answer: 186630.0

User story: "We need to add a query (or more?) to the qserv_testdata that involve blobs. Blobs are interesting because they might break some parts of the qserv if we failed to escape things properly etc. "
Answer: 857428.0

User story: "Not sure this is a problem. Can we determine anything from the stack trace? {code} Thread 1 (Thread 0x7fe5d332e700 (LWP 27021)): #0  0x00007fe5d223c3b9 in syscall () from /lib64/libc.so.6 #1  0x00007fe5c7647a7b in XrdSys::LinuxSemaphore::Wait() () from /u1/lsst/xrdNew-inst/lib64/libXrdCl.so.2 #2  0x00007fe5c7666608 in XrdCl::SyncResponseHandler::WaitForResponse() () from /u1/lsst/xrdNew-inst/lib64/libXrdCl.so.2 #3  0x00007fe5c76666bc in XrdCl::MessageUtils::WaitForStatus(XrdCl::SyncResponseHandler*) () from /u1/lsst/xrdNew-inst/lib64/libXrdCl.so.2 #4  0x00007fe5c767aaa6 in XrdCl::File::Truncate(unsigned long, unsigned short) () from /u1/lsst/xrdNew-inst/lib64/libXrdCl.so.2 #5  0x00007fe5c9bb99a6 in XrdSsiTaskReal::Kill() () from /u1/lsst/xrdNew-inst/lib64/libXrdSsi.so.1 {code} The process trapped a Ctrl-C, and issued XrdSsiRequest::Finished(true), but the XrdCl code seems to be waiting a message (from the server?). In this case, the server process has already been killed, so no message will be received. It seems strange that the client could be waiting for a message when the connection is already dead. Perhaps the condition variable missed waking up the appropriate waiters?  I will attach the full pstack. Sorry, it wasn't a debug build(?) so there are no line numbers.  Would you have a look at the code around the stack trace? If you can't determine anything, that's okay. We can close/defer this until we get more information."
Answer: 240282.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: "Presence of {{.my.cnf}} file in the user HOME directory crashes {{qserv-configure.py}} script if parameters in {{.my.cnf}} conflict with parameters in {{qserv.conf}}.  How to reproduce: * create .my.cnf file in the home directory: {code} [client] user     = anything # host/port and/or socket host     = 127.0.0.1 port     = 3306 socket   = /tmp/mysql.sock {code} * try to run {{qserv-configure}}, it fails with error: {code} /usr/local/home/<USER>qserv-run/u.<USER>DM-595/tmp/configure/mysql.sh: connect: Connection refused /usr/local/home/<USER>qserv-run/u.<USER>DM-595/tmp/configure/mysql.sh: line 13: /dev/tcp/127.0.0.1/23306: Connection refused ERROR 2003 (HY000): Can't connect to MySQL server on '127.0.0.1' (111) {code}  It looks like {{~/.my.cnf}} may be a left-over from some earlier qserv installation. If I remove it and re-run {{qserv-configure.py}} now it's not created anymore. Maybe worth adding some kind of protection to {{qserv-configure.py}} in case other users have this file in their home directory."
Answer: 30615.0

User story: "There is an unused instantiation of doMeasureCentroidImpl in an anon namespace in SdssCentroid.cc.  Please remove it. "
Answer: 11635.0

User story: "We need to be able to return values at the same time that an error flag is set.  The easiest way to do this is to have Algorithms take a Result object as an output argument rather than return it.  We'll revisit this design later. "
Answer: 45862.0

User story: "Finish the work started by Bill (DM-778)"
Answer: 16931.0

User story: "This is a low-priority ticket to replace the old-style plugins in meas_extensions_photometryKron with new ones compatible with meas_base.  As this isn't a part of the main-line stack, we should delay it until other the meas_base conversion is nearly (or perhaps fully) complete."
Answer: 325638.0

User story: "This is a low-priority ticket to replace the old-style plugins in meas_extensions_shapeHSM with new ones compatible with meas_base.  As this isn't a part of the main-line stack, we should delay it until other the meas_base conversion is nearly (or perhaps fully) complete."
Answer: 325910.0

User story: "ip_diffim includes a few measurement algorithms which need to be converted to the new framework."
Answer: 325649.0

User story: "Unlike previous FunctorKey replacements, Coord compound Keys are used in the minimal schema for SimpleTable and SourceTable, which makes removing them problematic."
Answer: 554359.0

User story: "We should consider adding a base class for measurement tasks (SingleFrameMeasurementTask, ForcedMeasuremedTask) that includes the callMeasure methods.  I'm hoping this will help cleanup callMeasure and improve code reuse."
Answer: 33316.0

User story: "Many meas_base Plugins and Algorithms have poor documentation, including several whose documentation is a copy/paste relic from some other algorithm.  These need to be fixed."
Answer: 29337.0

User story: "We should follow RHL's example for detailed task documentation and document all meas_base tasks."
Answer: 69237.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: "Frequently-used measurement fields such as classification and pixel flags should have shortened aliases that can be used instead of their full, package-qualified versions.  In some cases, these may serve as a sort of slot (e.g. we may have multiple classifications algorithms someday).  In this issue, we should audit all current measurement algorithm fields that don't already have a slot that works for them and consider whether there should be a standard alias.  We also need to work out a system for defining these aliases, probably in the config for SingleFrameMeasurementTask."
Answer: 275202.0

User story: "Config validation and freezing is currently carried out by the argument parser.   This ticket requests that the config freezing (also?) be carried out by the task constructors.  This should be an essentially free operation, which may require caching the status in the Config object.  N.b.  It is not clear that we are quite ready to implement this ticket as the per-dataset behaviour of at least some tasks can only be modified by changing the config.  This is not desirable (and Jim thinks that it may not always work), but it may require changing the run API before we work on this issue. "
Answer: 2949677.0

User story: "Config validation and freezing is currently carried out by the argument parser.   This ticket requests that the config validation (also?) be carried out by the task constructors.  This should be an essentially free operation, which may require caching the status in the Config object. "
Answer: 2949679.0

User story: Create a "tutorials" package with helper scripts, configurations, and data files, and place under version control (git). Upload the package to the LSST cgit repository (in /contrib). Update the tutorials to instruct users how to download and use this package, and remove references to scripts attached directly to the tutorials pages. 
Answer: 2380418.0

User story: "Schema stringification and iteration should include aliases somehow.  Likewise the extract() Python methods."
Answer: 297263.0

User story: "We've added a version number to afw::table::BaseTable to help with the transition to a new approach with different naming conventions and FunctorKeys instead of compound keys.  However, it looks like Schema objects need to know about this version number as well, in order to change Subschema objects to split/join using underscores instead of periods.  That means we'll have to move the version down into the schema object, which may affect a lot of downstream code.  Other than touching a lot of code, the changes should be trivial."
Answer: 62473.0

User story: "The addition of schema aliases on DM-417 should allow us to clean up some of the transitional code added on DM-545, as we can now alias new versions of fields to the old ones and vice versa."
Answer: 56322.0

User story: "Buildbot build status report currently doesn't state if the build was only for master or included other branches requested by the user."
Answer: 56119.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: "Currently the on-source-change cron trigger of buildbot processing only checks the gitolite-fronted repositories. It also needs to check the stash-fronted repositories.  This becomes urgent when DM's git repos  moves over to stash management."
Answer: 181308.0

User story: "Andy S. suggests this during DM-622 review, but this needs to be studied deeply, as qserv_testdata goal is to store large datafile, difficult to version in git."
Answer: 96336.0

User story: Update and refactor the "Packages & Tasks" chapter of the SWUG to give a better overview of the Stack, and to incorporate a recent presentation by K-T to the DES-LSST workshop (see attached). Also update the Package Index, which should also include links to the task-level documentation, which is now being written. 
Answer: 4215.0

User story: "Master-branch doxygen documentation should be rebuild on every full master build."
Answer: 59411.0

User story: "Provide the eups-tag assigned to a build within the email response.  Currently it needs to be deduced from the BB stdio log."
Answer: 61446.0

User story: "qserv-start.sh by default tries again to use /usr/local/home/<USER>qserv-run/2014_05.0 directory. There may be a confusion if we have multiple run directories. Would it be better to install qserv start/stop scripts into run directory itself so that they don't need to guess anything?"
Answer: 2570088.0

User story: "I almost always use --show config as e.g. {code} processCcd.py ...  --show config | grep threshold {code}  Please support {code} --show glob=*threshold* {code} (N.b.  any csh users out there will need to quote the *s)  (I already have an implementation for my lightweight process-this-fits-file-for-me script) "
Answer: 125.0

User story: "Make any changes in the Functor Key capabilities necessary to support getXXXKey, getXXXErrKey, and getXXXFlagKey for the 3 different types of slots.   Change these routines in Source.h.m4 to return FunctorKeys for both version 0 and version 1 tables.  Then fixup any compilation breaks on the C++ size which this causes.  Remove the version 1 specific accessors.   I am assigning this to Jim to confirm that the first part is done, then he can assign the remainder to Perry either by reassigning, or as a subtask."
Answer: 31589.0

User story: "For security reasons, we should switch to using the https:// versions of the URLs (once appropriate certificates are installed to sw.lsstcorp.org)."
Answer: 2796379.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 photometric calibration code uses a field "flux" in the reference catalog to impose a magnitude limit.  If a colour term is specified, it uses the primary and secondary filters to calculate the reference magnitude, but if there is no colour term it uses the column labelled "flux" and ignores the filtername.    Please change the code so that "flux" is ignored, and the flux associated with filterName is used.
Answer: 1009094.0

User story: This ticket propose to migrate README and README-devel to reST format (see http://sphinx-doc.org/rest.html). The output is located here : http://lsst-web.ncsa.illinois.edu/~fjammes/qserv-doc/  Furthermore this ticket wil integrate Andy S. DM-622 value-added remarks about Qserv embedded documentation. {quote} README.txt needs a bit of formatting, whole "NOTE FOR DEVELOPERS" is one long line which may need scrolling depending on what do you use to read the file, same applies to README-devel.txt The install procedure in README.txt implies that the whole stack has to be installed including eups. If people have some part of it installed already the it would probably be better to reuse existing stack. Shall we spit install instructions into "Install eups (if not installed already)" and "Install qserv"? README-devel.txt says "Once Qserv is installed...", I don't think that we need or want to install whole qserv before we start development (what if qserv is not available yet for the platform I'm trying to test). What probably needed is installed dependencies, and this should be covered by the comments before 'setup -r .' {quote} 
Answer: 63330.0

User story: "Please provide documentation on how to write a command line task, and how to retarget tasks (e.g. reusing bits of IsrTask for a new camera)  The documentation should include a complete annotated example.  "
Answer: 38659.0

User story: "See Summary"
Answer: 60444.0

User story: "See Summary"
Answer: 58777.0

User story: "See Summary"
Answer: 3078561.0

User story: "See Summary"
Answer: 523716.0

User story: "See Summary"
Answer: 7488.0

User story: "See Summary"
Answer: 7492.0

User story: "See Summary"
Answer: 7489.0

User story: "See Summary"
Answer: 16.0

User story: "See Summary"
Answer: 17.0

User story: "See Summary"
Answer: 17.0

User story: "See Summary"
Answer: 17.0

User story: "See Summary"
Answer: 90412.0

User story: "See summary"
Answer: 64130.0

User story: "See summary"
Answer: 64435.0

User story: "See summary"
Answer: 64436.0

User story: "See Description (it's currently called PsfMatch) "
Answer: 64437.0

User story: "See Summary. "
Answer: 64442.0

User story: "For obs_lsstSim, the camera description is generated by a few data files and scripts. Presently the script(s) are in bin/ and the description files are at the top level of description. This makes the scripts too easy to run, and confuses users. Please put them somewhere out of the way, with a text file explaining what they are, where the raw data came from, and how to process the raw data."
Answer: 2424699.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: "Update the Process PhoSim Images tutorial (https://confluence.lsstcorp.org/display/LSWUG/Process+PhoSim+Images) to use CatSim to generate instance catalogs, once CatSim documentation is available. This will obviate the need for the helper script refCalCat.py. "
Answer: 2417576.0

User story: "Is this use-case usefull ? Maybe in the long-term in order to compare several Qserv version on different data sets ?"
Answer: 875936.0

User story: "Here's what should be added to qserv-configure.py :  - edit $QSERV_RUN_DIR/admin/qserv.conf and change Qserv instance dir to current one (which qserv-configure.sh), - check compliance of QSERV_RUN_DIR with new Qserv instance (version check ?) and/or update configuration files, - re-initialize services, if needed, without breaking already loaded data. "
Answer: 2440187.0

User story: The original scenarios utilizing job Rank in DM-653  were revisited upon the following discovery. Original results where jobs executed in "appropriate" slots were discovered to be an artifact of job submission order. A more scrambled job submission order in a base scenario with static class ads for slots showed jobs to not execute in the locations (host/slot) expected.     A base scenario demonstrating job Rank not delivering expected results was presented to the HTCondor team.  They were able to reproduce the results and traced the problem to a long existing auto clustering bug in HTCondor. They created ticket #4403  https://htcondor-wiki.cs.wisc.edu/index.cgi/tktview?tn=4403 for HTCondor, and subsequently provided a workaround for current releases, and implemented a solution in the codes base for 8.2.1+.  In this issue we test these workarounds/solutions.
Answer: 106414.0

User story: From: <USER>the Good <<EMAIL>> On: May 19 To: LSST  I continue to see code like:  > nGrow = int((self.config.nSigmaToGrow * sigma) + 0.5)  This should be         nGrow = int(self.config.nSigmaToGrow*sigma + 0.5)  That is:         No unnecessary parens -- they require the reader to think, "What do those parens mean --- Oh, nothing"         ** * / bind harder than + - and should have no whitespace (+- do need spaces).  Just the way that you write mathematics by hand:                 "1 + 2x" not "1+2 x" or "1 + 2 x"  Maybe we should use         nGrow = round(self.config.nSigmaToGrow*sigma) or         nGrow = np.rint(self.config.nSigmaToGrow*sigma) but I'm not excited (especially as round(0.5) changes from 1 to 0 in python3)  
Answer: 150212.0

User story: string.Template and string interpolation are quite weak, some additional feature would be welcomed :  - interpolation interprets wrongly "%d" in template files as template - string.template doesn't manage correctly non referenced template parameters present in template files.
Answer: 2599734.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: "mocks/simpleMapper/makeSimpleCamera returns a camera whose transformMap is a dict instead of a CameraTransformMap.  I propose to fix this as part of DM-764 so I can commit that with a full suite of working unit tests. I'd do it on trunk, but I'm not sure what versions of packages are required to make the current trunk work. In any case, the fix is very simple."
Answer: 11392.0

User story: tests/subtractExposures.py always fails on MacOS X: a value is slightly wrong.  {code} FAIL: testXY0 (__main__.DiffimTestCases) ---------------------------------------------------------------------- Traceback (most recent call last):   File "tests/subtractExposures.py", line 182, in testXY0     self.runXY0('polynomial')   File "tests/subtractExposures.py", line 263, in runXY0     self.assertAlmostEqual(skp1[nk][np], skp2[nk][np], 4) AssertionError: -0.0004418029210029317 != -0.00039009266307754586 within 4 places {code} I have attached the full output as a file.
Answer: 627607.0

User story: "While a single request in a single session seems to work fine, multiple sessions with their own in-flight requests seem broken.  In the stack trace, you can see that a cancelling call is in-flight (XrdSsiRequest::Finished(true) but blocked by a semaphore. An Unprovision call is also in-flight, but also blocked.  It is possible that there is a memory new/delete problem. I don't know yet. The memory management is a bit foggy for me because it's not always clear who should own these *Session or *Request objects at what points in the code.  This is going to be hard to reproduce, because I'm constantly changing the code. But it's  commit 7758b32c467 on u/<USER>kirkwood .  I am including a stack trace in the hopes that it provides enough clues."
Answer: 41897.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 I build pex_logging 8.0.0.0 I get three similar warnings:    {code}  src/Log.cc:172:16: warning: lookup of 'set' in member access expression is ambiguous; using member of 'lsst::daf::base::PropertySet' [-Wambiguous-member-template]      _preamble->set<string>("LOG", _name);                 ^  /Users/<USER>LSST/lsst_home2/DarwinX86/daf_base/8.0.0.0+1/include/lsst/daf/base/PropertySet.h:139:32: note: lookup in the object type 'lsst::daf::base::PropertySet' refers here      template <typename T> void set(std::string const& name, T const& value);                                 ^  /usr/include/c++/4.2.1/bits/stl_set.h:93:11: note: lookup from the current scope refers here      class set            ^  …  tests/testLogRecord.cc:95:14: warning: lookup of 'set' in member access expression is ambiguous; using member of 'lsst::daf::base::PropertySet' [-Wambiguous-member-template]      preamble.set<int>("dpint", 2);               ^  /Users/<USER>LSST/lsst_home2/DarwinX86/daf_base/8.0.0.0+1/include/lsst/daf/base/PropertySet.h:139:32: note: lookup in the object type 'lsst::daf::base::PropertySet' refers here      template <typename T> void set(std::string const& name, T const& value);                                 ^  /usr/include/c++/4.2.1/bits/stl_set.h:93:11: note: lookup from the current scope refers here      class set            ^  tests/testLogRecord.cc:96:14: warning: lookup of 'set' in member access expression is ambiguous; using member of 'lsst::daf::base::PropertySet' [-Wambiguous-member-template]      preamble.set<float>("dpfloat", 2.5);               ^  /Users/<USER>LSST/lsst_home2/DarwinX86/daf_base/8.0.0.0+1/include/lsst/daf/base/PropertySet.h:139:32: note: lookup in the object type 'lsst::daf::base::PropertySet' refers here      template <typename T> void set(std::string const& name, T const& value);                                 ^  /usr/include/c++/4.2.1/bits/stl_set.h:93:11: note: lookup from the current scope refers here      class set            ^  tests/testLogRecord.cc:97:14: warning: lookup of 'set' in member access expression is ambiguous; using member of 'lsst::daf::base::PropertySet' [-Wambiguous-member-template]      preamble.set<long>("dplong", 5l);               ^  /Users/<USER>LSST/lsst_home2/DarwinX86/daf_base/8.0.0.0+1/include/lsst/daf/base/PropertySet.h:139:32: note: lookup in the object type 'lsst::daf::base::PropertySet' refers here      template <typename T> void set(std::string const& name, T const& value);                                 ^  /usr/include/c++/4.2.1/bits/stl_set.h:93:11: note: lookup from the current scope refers here      class set            ^  {code}
Answer: 2693395.0

User story: "Discussions with strategic partners. Improving website and adding new context (community, speakers). 1-pager document"
Answer: 50214.0

User story: "The benchmark data used to confirm correct results for demo2012's processCCD execution needs to be  updated to reflect the v8.0.0 DM stack."
Answer: 98289.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: Compiling qserv on ubuntu 14.04 (comes with gcc 4.8.2) results in huge number of warnings coming from boost. We should use the flag "-Wno-unused-local-typedefs".
Answer: 101059.0

User story: "<USER>reports problems running v8 on OSX Mavericks due to the build being made against an LSST-provided cfitsio, but attempting to run against a system-installed cfitiso.  This appears to be due to some LSST packages being appended to his {{DYLD_LIBRARY_PATH}} instead of prepended:  {code:sh} $ echo $DYLD_LIBRARY_PATH  /Users/timj/work/lsst/DarwinX86/shapelet/8.0.0.0+3/lib:/Users/timj/work/lsst/DarwinX86/meas_extensions_multiShapelet/8.0.0.0+3/lib:/Users/timj/work/lsst/DarwinX86/skymap/8.0.0.0+3/lib:/Users/timj/work/lsst/DarwinX86/coadd_chisquared/8.0.0.0+3/lib:/Users/timj/work/lsst/DarwinX86/coadd_utils/8.0.0.0+3/lib:/Users/timj/work/lsst/DarwinX86/ip_diffim/8.0.0.0+3/lib:/Users/timj/work/lsst/DarwinX86/ip_isr/8.0.0.0+3/lib:/Users/timj/work/lsst/DarwinX86/astrometry_net/0.30+3/lib:/Users/timj/work/lsst/DarwinX86/meas_astrom/8.0.0.0+3/lib:/Users/timj/work/lsst/DarwinX86/meas_algorithms/8.0.0.0+3/lib:/Users/timj/work/lsst/DarwinX86/minuit2/5.22.00+2/lib:/Users/timj/work/lsst/DarwinX86/wcslib/4.14+3/lib:/Users/timj/work/lsst/DarwinX86/fftw/3.3.2+2/lib:/Users/timj/work/lsst/DarwinX86/pex_config/8.0.0.0+1/lib:/Users/timj/work/lsst/DarwinX86/afw/8.0.0.3/lib:/Users/timj/work/lsst/DarwinX86/base/8.0.0.0+1/lib:/Users/timj/work/lsst/DarwinX86/pex_policy/8.0.0.0+1/lib:/star/lib:/star/starjava/lib/i386:/star/starjava/lib/x86_64:/Users/timj/work/lsst/DarwinX86/daf_base/8.0.0.0+1/lib:/Users/timj/work/lsst/DarwinX86/utils/8.0.0.0+1/lib:/Users/timj/work/lsst/DarwinX86/boost/1.55.0.1/lib:/Users/timj/work/lsst/DarwinX86/pex_exceptions/8.0.0.0+1/lib:/Users/timj/work/lsst/DarwinX86/pex_logging/8.0.0.0+1/lib:/Users/timj/work/lsst/DarwinX86/daf_persistence/8.0.0.0+1/lib:/Users/timj/work/lsst/DarwinX86/mysqlclient/5.1.65+3/lib:/Users/timj/work/lsst/DarwinX86/cfitsio/3310+2/lib:/Users/timj/work/lsst/DarwinX86/xpa/2.1.14+2/lib:/Users/timj/work/lsst/DarwinX86/gsl/1.15+2/lib:/Users/timj/work/lsst/DarwinX86/meas_deblender/8.0.0.0+3/lib {code}  This suggests we need a thorough audit of ups table files, removing {{envAppend}} in favour of {{envPrepend}}."
Answer: 259208.0

User story: "As part of the resolution of DM-831, it was suggested that modern editors can be configured to automatically check syntactic aspects of the code and highlight violations of our coding standards.  Prepare such configurations for common editors."
Answer: 2630466.0

User story: "When we installed apr and apr_utils packages (as a dependency of new log4cxx package, see DM-772) we discovered that both these packages only build static libraries but no shared libs are installed. This is problematic if mixed with shared libs and we use shared libs everywhere else. We certainly need to build shared libs for these packages, this ticket is to follow up on this problem."
Answer: 47243.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: "Queries that are not instantaneous, including long running queries that should survive master failures need a global queryId. Need to implement the system generates such queryIds, and assigns them to appropriete queries"
Answer: 843842.0

User story: "Qserv needs to work in multi-master configuration.    Research how query dispatch in master (Czar) works working toward the goal of being able to work on multi-master architecture & implementation."
Answer: 2493773.0

User story: "For all code that uses the ImageOrigin argument, eliminate the use of that argument. In other words, update all code to match the changes in DM-844 and DM-845,  This affects all the code affected by DM-848, plus any code that was already using ImageOrigin=PARENT, but is a simpler change."
Answer: 135455.0

User story: "For all code that uses the ImageOrigin argument (either explicitly or using a bbox and the default value) change the code to use an explicit ImageOrigin of PARENT.  In other words, update all code to match the changes in DM-840 and DM-841.  This affects 40-ish modules in many packages. I am concerned about testing the modified code because we are missing unit tests for so many tasks. But we can do some data processing and check those results. I will want some help with that."
Answer: 161199.0

User story: "For all code changed in DM-842, change it again to use the restored names for methods that return pixel iterators and locators.  This task is much simpler than DM-842 because it is merely renaming methods. Nonetheless, it touches many files in many packages."
Answer: 197383.0

User story: "The next step after DM-840 is to change all code that uses image-like getBBox and constructors that take an image origin argument to always specify the origin (DM-840 will break any code that tries to use a default image origin).  This results in a working stack after DM-840.  Neither this nor DM-840 will be merged to master, though it can be used by HSC and other users as they transition to a default image origin of PARENT.  See DM-1176 for the final step."
Answer: 136514.0

User story: "Eliminate the image origin argument for butler get and put when dealing with image-like objects."
Answer: 135470.0

User story: "Eliminate the ImageOrigin enum and argument from image-like classes."
Answer: 135487.0

User story: "Restore the names of methods that return pixel iterators and pixel locators on image-like classes. (This is part of the final stage of eliminating LOCAL pixel indexing)."
Answer: 197020.0

User story: "Fix all code that uses pixel iterators and locators as per the changes in DM-839. This affects roughly 60 files distributed over many packages."
Answer: 197399.0

User story: "As part of making PARENT the default for image origin, change the data butler to require that imageOrigin be specified if bbox is specified when reading or writing image-like objects.  Note: this ticket turns out to be unnecessary, as all the few necessary change are done as part of DM-840."
Answer: 135487.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: "Image-like classes have a getBBox method and various constructors that use an ImageOrigin argument which in most or all cases defaults to LOCAL. As the first stage in cleaning this up, try to break code that uses the default as follows: * Remove the default from getBBox(ImageOrigin) so an origin must be specified. * Change the default origin of constructors to a temporary new value UNDEFINED  * Modify code that uses image origin to fail if origin is needed (it is ignored if bbox is empty) and is UNDEFINED.  Note: this is less safe than changing constructors to not have a default value for origin, because the error will be caught at runtime rather than compile time. However, that is messy because then the bounding box will also have to be always specified, and possibly an HDU, so it would be a much more intrusive change."
Answer: 136536.0

User story: "Image-like classes have a large number of methods that return pixel iterators and locators based on row and/or column. We wish to change these to use parent indexing (making row and column relative to XY0). As the first step in doing this, rename all these methods and modify them to parent indexing. Renaming will help identify and fix all code that uses these methods."
Answer: 197428.0

User story: "We've never figured out how to handle wrapping multiple-aperture photometry algorithms.  They can't use the existing Result objects - at least not out of the box.  We should try to write a new multiple-aperture photometry algorithm from the ground up, using the old ones on the HSC branch as a guide, but not trying to transfer the old code over.  The new one should:  - Have the option of using elliptical apertures (as defined by the shape slot) or circular apertures.  - Have a transition radius at which we switch from the sinc photometry algorithm to the naive algorithm (for performance reasons)."
Answer: 164540.0

User story: "While we're trying to eliminate the need for compound fields in afw::table, Arrays present a few problems.  We could use FunctorKeys, the way we plan to use other compound fields, but here we need to guarantee that the per-element keys are contiguous, and we also be able to support views.  We also need to determine the naming scheme.  Finally, we need to make sure these work with aliases and slots."
Answer: 154475.0

User story: We should be able to resolve issues as duplicates, not just link them.  Should probably have similar resolutions for "invalid", "wontfix", "obsoleted [by]", maybe others.
Answer: 2443966.0

User story: "The aperture correction code to be added on DM-833 will likely not be as closely integrated with CoaddPsf as it could be, because the original design of CoaddPsf didn't anticipate the addition of other, similar classes.  We should work on allowing these classes to share code."
Answer: 706935.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 be able to coadd aperture corrections in much the same way we coadd PSFs.  See the HSC-side HSC-798 and HSC-897 implementation for a prototype: https://hsc-jira.astro.princeton.edu/jira/browse/HSC-798 https://hsc-jira.astro.princeton.edu/jira/browse/HSC-897 with code here: https://github.com/HyperSuprime-Cam/meas_algorithms/compare/d2782da175c...u/<USER>DM-798 https://github.com/HyperSuprime-Cam/meas_algorithms/compare/c4fcab3251...u/price/HSC-897a https://github.com/HyperSuprime-Cam/pipe_tasks/compare/6eb48e90be12d...u/price/HSC-897a"
Answer: 619486.0

User story: "We need to create a persistable, map-like container class to hold aperture corrections, with each element of the container being an instance of the class to be added in DM-740.  A prototype has been developed on DM-797 on the HSC side: https://hsc-jira.astro.princeton.edu/jira/browse/HSC-797 and the corresponding code can be found on these changesets: https://github.com/HyperSuprime-Cam/afw/compare/32d7a8e7b75da6f5327fee65515ee59a5b09f6c7...tickets/DM-797"
Answer: 538412.0

User story: As part of the ongoing measurement overhaul, I proposed a broad change to the naming conventions for afw::table fields.  This was approved in a design review a while back, but one aspect of that has remained contentious and I'd like to reopen it and have it settled more officially by the SAT before making the change.  The question is whether to use "." or "_" as a namespace delimiter in field names.  I really do mean a *namespace* delimiter; we're already using CamelCase as a *word* delimiter, so in this case we're talking about the delimiter used to separate the abbreviated-package ("{{base}}"), algorithm name ("{{SdssShape}}"), and measurement quantity ("{{xx}}") of a name like "{{base_SdssShape_xx}}"/"{{base.SdssShape.xx}}".  Here are the main arguments, as I see them:   - Periods are what we have used so far in afw::table, and they're a far more natural-looking namespace separator, especially in Python.  Underscores are more naturally a word delimiter than a namespace delimiter, and using them as a namespace delimiter looks awkward in Python and C\+\+.   -  SQL databases don't support periods in field names, so we'd have to use underscores there regardless.  So if we use periods in afw::table, we'll the C\+\+/Python names for fields will be different from those used in SQL, while if we use underscores in afw::table they can be the same.  I'm personally ambivalent about this choice, but I'd like it to be official so I don't take the heat from whoever doesn't get their way :-)
Answer: 3690.0

User story: "In this design prototype, I'll see how much simpler things could be made by making the main algorithm interface one that sets record values directly, instead of going through an intermediate Result object.  Ideally the Result objects would still be an option, but they may not be standardized or reusable."
Answer: 207619.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've never really been happy with the new design for the C++ algorithm API, and Perry and Jim have a few ideas to fix this that need to be fleshed out.  Each of the subtasks of this issue will correspond to a different design idea.  Ideally, for each one, we'll try to do a nearly-complete conversion of the SdssShape algorithm (as a good example of a complicated algorithm) to see how these ideas work in practice."
Answer: 207623.0

User story: I'd like to reimplement our Swig bindings for C++ exceptions to replace the "LsstCppException" class with a more user-friendly mechanism.  We'd have a Python exception hierarchy that mirrors the C++ hierarchy (generated automatically with the help of a few Swig macros).  These wrapped exceptions could be thrown in Python as if they were pure-Python exceptions, and could be caught in Python in the same language regardless of where they were thrown.  We're doing this as part of a "Measurement" sprint because we'd like to define custom exceptions for different kinds of common measurement errors, and we want to be able to raise those exceptions in either language.
Answer: 86543.0

User story: Mail from Jira can get lost in hyperactive mailboxes.  Can we configure Jira to set more helpful subjects (e.g. "Review requested on DM-735") 
Answer: 237272.0

User story: "When you create a PhotoCalTask it sometimes adds a column to the schema, which it then blithely uses in its run method even if it is not actually present in the input tables.  Please add a check that the column is really there. "
Answer: 37510.0

User story: "When you create an AstrometryTask (currently in pipe_tasks but should move to meas_astrom) it adds columns to the schema, which it then blithely uses in its run method even if they are not actually present in the input tables.  Please add a check that the columns are really there. "
Answer: 4239.0

User story: "The current implementation of the AstrometryTask adds columns to the schema to hold the distorted coordinates.  This means that it cannot be used to match a pre-existing afwTable even if there is no distortion.  I don't think that this is polite behaviour.  At the very least the new columns should only be added if distortion is present (presumably controlled via a config parameter as we don't know what the data looks like when the task is created).  A better long-term solution is to change the way that the book-keeping is done."
Answer: 1431313.0