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: "Firefly will get better performance when it can use local disk (SSD drives are even better) for cache.  Since in the multi server environment we only need to share a small amount of work area we need to change the system to have both a work area and a shared work area.  The shared work area will be for uploads and staging.  The work area is for everything else."
Answer: 9973.0

User story: "DM-15189 improves support for raw data by adding new Formatters that provide the adaptation logic provided by {{std_}} hooks in Gen2.  But those Formatters aren't used in {{gen2convert}} yet, because {{gen2convert}} doesn't see raw data as special.  As a result, loading {{raw}} with a Gen3 Butler pointed at a converted repo just gets you a {{DecoratedImage}}, not an {{Exposure}}.    The simplest fix is probably to have {{gen2convert}} just run raw ingest instead of transferring raws via the usual mechanism.  The tricky part of that is to provide a way for {{gen2convert}} to identify the {{RawIngestTask}} specialization for a particular camera.  We need to solve that problem anyway, but I'd hoped to get some CameraGeom and package organization problems in better shape before tackling it.  An alternative may be to just force the user to provide the task name in the {{gen2convert}} configuration for now.    Tentatively assigning this to me since I have a pretty good idea in my head of how to approach this, but [~<USER> is also a possibility.     "
Answer: 164495.0

User story: "Some headers seem to be missing, set defaults where it's safe, and do whatever else is necessary within reason."
Answer: 1449.0

User story: "Straight to the conclusion : the impact of varying Temperature and Pressure profiles on the libradtran determination of the molecular scattering is negligible.     "
Answer: 153614.0

User story: "As they're implemented in C++ and return non-polymorphic types, all of our FITS readers coerce the on-disk object to a specific type.  Gen3 Butler code could be greatly simplified by providing Image, Mask, Exposure, and Catalog readers that return infer the template specialization from what's actually in the file."
Answer: 64267.0

User story: "When transactions are nested, any raised exception that propagates through a {{with}} block will trigger a rollback on higher-level {{with}} blocks, even if that exception is caught immediately outside the innermost {{with}} block (which is generally the on added by the {{transactional}} decorator.    This gives the illusion of fully nested transactions, while in reality we only provide per-Butler transactions in which nesting is a no-op.  We should (ideally) find a better way to map the transactions we do support to Python language constructs.  Failing that, we should at least prevent {{transactional-}} decorated methods from triggering higher-level rollbacks when they don't have to (e.g. when {{Registry.addDataset}} sees a conflict before it even tries to add anything)."
Answer: 211538.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 specs that specify the yearly ramps from LDM-240 do not have associated metrics.  This means that SQuaSH cannot query for them.  Add metric names to these specs so that the spec levels can be plotted on the SQuaSH traces."
Answer: 1444.0

User story: "In order to reduce the number of packages involved in the release process, 3rd party packages available in conda can be moved into the environment definition."
Answer: 322289.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 try to run {{writeObjectTable.py}} on lsst-dev, it fails with a segfault & long backtrace, starting like:  {noformat}  [<USER>lsst-dev01 DM-14289]$ bash writeTables_test.sh  Caught signal 11, backtrace follows:  /ssd/lsstsw/stack3_20171021/stack/miniconda3-4.3.21-10a4fa6/Linux64/utils/16.0-6-g3610b4f/lib/libutils.so(+0x15214) [0x7f078a865214]  /usr/lib64/libc.so.6(+0x362f0) [0x7f080a5892f0]  /ssd/lsstsw/stack3_20171021/python/miniconda3-4.3.21/bin/../lib/libstdc++.so.6(std::basic_string<char, std::char_traits<char>, std::allocator<char> >::basic_string(std::string const&)+0xb) [0x7f08032b640b]  /ssd/lsstsw/stack3_20171021/python/miniconda3-4.3.21/lib/python3.6/site-packages/pyarrow/../../../libparquet.so.1(+0x177ddc) [0x7f071bcb6ddc]  /ssd/lsstsw/stack3_20171021/python/miniconda3-4.3.21/lib/python3.6/site-packages/pyarrow/../../../libparquet.so.1(+0x1696c3) [0x7f071bca86c3]  /ssd/lsstsw/stack3_20171021/python/miniconda3-4.3.21/lib/python3.6/site-packages/pyarrow/../../../libparquet.so.1(+0x175e8b) [0x7f071bcb4e8b]  /ssd/lsstsw/stack3_20171021/python/miniconda3-4.3.21/lib/python3.6/site-packages/pyarrow/../../../libparquet.so.1(parquet::ApplicationVersion::ApplicationVersion(std::string const&)+0x6d) [0x7f071bc4aa5d]  /ssd/lsstsw/stack3_20171021/python/miniconda3-4.3.21/lib/python3.6/site-packages/pyarrow/../../../libparquet.so.1(+0x83590) [0x7f071bbc2590]  /lib64/ld-linux-x86-64.so.2(+0xfb03) [0x7f080b964b03]  /lib64/ld-linux-x86-64.so.2(+0x146de) [0x7f080b9696de]  /lib64/ld-linux-x86-64.so.2(+0xf914) [0x7f080b964914]  /lib64/ld-linux-x86-64.so.2(+0x13ccb) [0x7f080b968ccb]  /usr/lib64/libdl.so.2(+0xfbb) [0x7f080b02dfbb]  ...etc  {noformat}    The script I am running is the following:  {noformat}  RERUN1=/datasets/hsc/repo/rerun/RC/w_2018_28/DM-14988/  OUTPUT1=/project/<USER>DM-14289/w28  RERUN2=/datasets/hsc/repo/rerun/RC/w_2018_26/DM-14689/  OUTPUT2=/project/<USER>DM-14289/w26    TRACT=9615  PATCH=4,4  FILTERS=HSC-G^HSC-R^HSC-I    writeObjectTable.py $RERUN1 --output $OUTPUT1 --id tract=$TRACT patch=$PATCH filter=$FILTERS --no-versions -j 20  writeObjectTable.py $RERUN2 --output $OUTPUT2 --id tract=$TRACT patch=$PATCH filter=$FILTERS --no-versions -j 20  writeQATable.py $OUTPUT1 --output $OUTPUT1 --id tract=$TRACT  patch=$PATCH --no-versions -j 20 --clobber-config  writeQATable.py $OUTPUT2 --output $OUTPUT2 --id tract=$TRACT  patch=$PATCH --no-versions -j 20 --clobber-config  {noformat}    I can run the identical script in the jupyterlab environment container and everything is great.    I think this is related to the fact that I can run the qa_explorer tests on the JL env but not lsst-dev, where it hangs with a segfault as well (DM-14224).  It is making testing of DM-14289 difficult, since I can't do it on lsst-dev."
Answer: 249434.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: "processCcd passed in w_2018_31 but failed in w_2018_32 for HSC RC2 data   {{visit=36118 ccd=21}} and {{visit=36240 ccd=70}}, with   {noformat}  RuntimeError: No matches to use for photocal  {noformat}      For {{--id visit=36118 ccd=21}}, it changed from   {noformat}  processCcd.calibrate.photoCal.match.sourceSelection INFO: Selected 1332/1582 sources  processCcd.calibrate.photoCal.match.referenceSelection INFO: Selected 257/2570 references  processCcd.calibrate.photoCal.match INFO: Matched 1 from 1332/1582 input and 257/2570 reference sources  {noformat}  to   {noformat}  processCcd.calibrate.photoCal.match.sourceSelection INFO: Selected 201/1582 sources  processCcd.calibrate.photoCal.match.referenceSelection INFO: Selected 257/2570 references  processCcd.calibrate.photoCal.match INFO: Matched 0 from 201/1582 input and 257/2570 reference sources  {noformat}        For {{--id visit=36240 ccd=70}}, it changed from   {noformat}  processCcd.calibrate.photoCal.match.sourceSelection INFO: Selected 2714/3727 sources  processCcd.calibrate.photoCal.match.referenceSelection INFO: Selected 330/2294 references  processCcd.calibrate.photoCal.match INFO: Matched 1 from 2714/3727 input and 330/2294 reference sources  {noformat}  to   {noformat}  processCcd.calibrate.photoCal.match.sourceSelection INFO: Selected 339/3727 sources  processCcd.calibrate.photoCal.match.referenceSelection INFO: Selected 330/2294 references  processCcd.calibrate.photoCal.match INFO: Matched 0 from 339/3727 input and 330/2294 reference sources  {noformat}  "
Answer: 1457.0

User story: *(Editing not finished, please wait before responding, etc.)*     With {{dbserv}} now converging on providing a TAP service, it's time to implement the "generic table browsing" feature that we need in the Portal so that we don't have to implement custom screens for every table.    The "generic browsing" screen should take a TAP endpoint as a parameter (this may come from a configuration parameter of the Portal in LSST's standard usage, or it may come from a "higher level" search facility that interacts with the VO Registry).    Given this parameter, it should use {{TAP_SCHEMA}} and/or the {{.../tables}} endpoint of the TAP service to obtain a list of tables, and display this list to the user.
Answer: 246069.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: In a query such as   {code:java}MariaDB [qservTest_case01_qserv]> select objectId, ra_PS from Object where objectId = 417853073271391 or objectId = 399294519599888;  +-----------------+------------------+  | objectId        | ra_PS            |  +-----------------+------------------+  | 399294519599888 | 359.337499495437 |  | 417853073271391 | 359.894210551011 |  +-----------------+------------------+  2 rows in set (0.11 sec)MariaDB [qservTest_case01_qserv]> select objectId, ra_PS from Object where ra_PS > 359.5 and (objectId = 417853073271391 or  objectId = 399294519599888);  +-----------------+------------------+  | objectId        | ra_PS            |  +-----------------+------------------+  | 399294519599888 | 359.337499495437 |  | 417853073271391 | 359.894210551011 |  +-----------------+------------------+  2 rows in set (0.11 sec) {code}  the second query should have returned only objectId 417853073271391, because the ra_PS value for objectId 399294519599888 is below the comparison value (of 359.5).    Based on initial research, it appears that the parenthesis are getting dropped from the query during processing in the Czar; the mysql-proxy-lua.log shows:  {code:java}(core/modules/qproc/QuerySession.cc:120) - Query Plugins applied:   QuerySession description:    original: select filterId,filterName from Filter where filterId > 2 and(filterName='y' or filterName='g')    has chunks: 0    chunks: []    needs merge: 0    1st parallel statement: SELECT filterId,filterName FROM qservTest_case01_qserv.Filter AS QST_1_ WHERE filterId>2 AND filterName='y' OR filterName='g' {code}  (note that in "1st parallel statement", the parens are omitted)          
Answer: 4384.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: "Produce preliminary epic list for task lead and management sign-off."
Answer: 51441.0

User story: "Hold planning/steering meetings with task leads and technical staff to scope work in each task area."
Answer: 51442.0

User story: "Prepare list of project needs, milestones, activities, and current status as input into planning process."
Answer: 11245.0

User story: "The code in {{afw.display.ds9}} sets the default backend to {{ds9}} even if a default is already set.  Please fix this.         N.b. the setting of the default to {{ds9}} is part of the backwards-compatibility effort."
Answer: 1696.0

User story: If astropy.units fails to import and a raises an exception (eg if warnings are converted to errors) when being imported via Schema.cc during import of {{lsst.afw.image}} an abort signal is received:    {code}  terminating with uncaught exception of type pybind11::error_already_set: SystemError: <built-in method __contains__ of dict object at 0x10049b900> returned a result with an error set  {code}    Stepping through schema.cc the line triggering this is:    {code}  * thread #1, queue = 'com.apple.main-thread', stop reason = breakpoint 2.1      frame #0: 0x0000000116e3d53d schema.so`void lsst::afw::table::(anonymous namespace)::declareSchemaType<unsigned char>(mod=0x00007ffeefbf33c0) at schema.cc:187 [opt]     184      std::string suffix = FieldBase<T>::getTypeString();     185      py::str pySuffix(suffix);     186    -> 187      py::object astropyUnit = py::module::import("astropy.units").attr("Unit");     188       189      // FieldBase     190      PyFieldBase<T> clsFieldBase(mod, ("FieldBase" + suffix).c_str());      * frame #0: 0x0000000116e3d53d schema.so`void lsst::afw::table::(anonymous namespace)::declareSchemaType<unsigned char>(mod=0x00007ffeefbf33c0) at schema.cc:187 [opt]      frame #1: 0x0000000116e3d143 schema.so`lsst::afw::table::(anonymous namespace)::pybind11_init_schema(mod=0x00007ffeefbf33c0) at schema.cc:398 [opt]      frame #2: 0x0000000116e3cf5d schema.so`::PyInit_schema() at schema.cc:390 [opt]    {code}    Something in the pybind11 layer is failing to catch the python exception and forward it on.    Depending on your system this can be reproduced with:  {code:python}  import warnings  warnings.simplefilter("error")  import lsst.afw.image  {code}    Given the reference to schema.cc and {{__contains__}} I initially thought this was related to DM-15406 and there is some commentary there.
Answer: 4585.0

User story: "Cleaning up the Forwarder directory before moving it."
Answer: 9678.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: "DiaSource table takes larges fraction of time when reading data, even at 1-month history depth, this will definitely get worse as we scale it to 12 months.    Couple oif things to investigate in this ticket:  * Check if region-based select can work better than ID-based select  * Look at the indexing options for DiaSource to see if current indexing can be improved (without bit redesign of the whole thing).    Potentially look also at other options:  - partitioning of DiaSource  - pre-fetching of (a part of a) DiaSource history  - in-memory database table for DiaSource history"
Answer: 103769.0

User story: "For milestone LDM-SUIT-9 (depend on LDM-503-8):  Spectral data display,  Robert does not think the support form SUIT is needed during the first period of  AuxTel commissioning.  Since we promised the data to public eventually,  DM needs to have a plan delivering the data to public. At the same time, maybe the above mentioned milestone timeline should be moved to a future date.     "
Answer: 164710.0

User story: "This is required in order to update metric definitions and specifications using the SQuaSH REST API. "
Answer: 331.0

User story: "Decide on attendees and date for a three day Camera Team Jellybean bootcamp.  This will likely require coordination with Steve R., Aaron R., Frosse E., and Adam T."
Answer: 141376.0

User story: "Create a Sphinx directive that automatically documents the configuration for a task. The directive will be included in [https://github.com/lsst-sqre/documenteer] and used as part of the task topic pages ([https://dmtn-030.lsst.io/#task-topic-type])."
Answer: 43469.0

User story: "Following discussions at LSST2018 last week, we have decided that controlling whether a composite should be disassembled or not should be a butler configuration level item and not a storage class item. This allows disassembly to be controlled by datasetType or StorageClass name. There will be a new top level butler configuration item, name TBD."
Answer: 3095.0

User story: "daf_butler shouldn't have to depend on utils. Using it in the tests is not helpful (and for file descriptor leaks we should take a look at pytest-openfiles) and the only other place utils is used is in getPackageDir which we can make optional."
Answer: 1004324.0

User story: The text "The ticket branch should not be deleted from the GitHub remote" in the Developer Guide will be replaced by "The ticket branch may be deleted from the GitHub remote if its name is in the merge commit comment (which it is by default)."
Answer: 5419.0

User story: "Additional text about the LDF and Kubernetes container deployment for LDM-542"
Answer: 57682.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "In the various places where we look up DataUnit information (joins, regions) for different sets of DataUnit [names], we are not consistent about whether dependencies should be included in those sets.  We should make sure all APIs support any amount of included dependencies (including optionals).    While I'd originally wanted to do this on DM-15034, and I still expect that to provide the best solution, some functionality is currently broken, so we can't afford to wait to do *something* about it."
Answer: 17658.0

User story: "Create a template in [https://github.com/lsst/templates] for nbreport projects (see [https://nbreport.lsst.io).|https://nbreport.lsst.io)./]    This is an LSST2018 hack project"
Answer: 8170.0

User story: "I am the co-chair or a primary contributor in four sessions at the PCW Aug 12 - Aug 17.  These are:    * Introduction to Stack Club  * DM-Camera interfaces  * Next generation visualization  * Testing the AOS with simulations    In these sessions I am either presenting information directly or I am contributing significantly to the conversation/decision making."
Answer: 8665.0

User story: "On-hand support for sessions requiring the Science Platform Notebook service. "
Answer: 8696.0

User story: "The recent changes to the deblender broke multiband source measurement on DCR coadds. This ticket is to identify and fix the breakages."
Answer: 10281.0

User story: "In running some tests involving pipe_base I got this warning:  {code}  /Volumes/ExternalSSD/Users/timj/work/lsstsw37/stack/DarwinX86/pipe_base/16.0-10-g0b41441+6/python/lsst/pipe/base/timer.py:91: DeprecationWarning: time.clock has been deprecated in Python 3.3 and will be removed from Python 3.8: use time.perf_counter or time.process_time instead  {code}    Not urgent yet but the Python developers have now given an explicit timeline for when it will become a problem."
Answer: 330941.0

User story: "Add the dataset definitions and identifications from the SST-based document by Bellm, Bosch, Ivezic, Slater, and Wood-Vasey to DMTN-091."
Answer: 632125.0

User story: "Remove python future from meas_modelfit."
Answer: 1302.0

User story: "utils no longer needs to be compatible with python2 so remove the shim layer."
Answer: 173.0

User story: "mpi4py 2 does not build with python3.7. Update to v3.0.0."
Answer: 253939.0

User story: "setMaskTransparency(100) in display_firefly makes makes mask overlays fully opaque, while the the documention (and the behavior of the same call in display_matplotlib, at least) suggest it should make them fully transparent."
Answer: 7758.0

User story: "Implement minimal TAP/Async query status functionality in existing albuquery service."
Answer: 170190.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 antlr4 generator inserts 2 semi colons at the end of lines in some cases. This makes our compiler mad with warnings.     Scons does not like to modify files in place and there is no elegant way to run sed on files being built. Instead, we make the build step 2 parts (the antlr4 step followed by the sed step inline separated by a semi colon).     "
Answer: 14271.0

User story: "We've agreed that it should not be the responsibility of the PhotoCalib to include a Jacobian derived from the WCS, because we don't always want to apply that.  Instead, SkyWcs should have the ability (given a pixel bounding box) to return a BoundedField that evaluates to the determinant of the Jacobian of the pixelToSky transform (aka the pixel area in angular units) at every point in that bounding box efficiently.  This probably involves a new BoundedField class (though it's possible there's a way to do this with TransformBoundedField).    A reference implementation can be found in meas_mosaic's {{calculateJacobian}} functions, though a different approach to vectorization may be necessary to get good performance from AST."
Answer: 122427.0

User story: "Right now {{nbrepot login}} prompts users for a GitHub password, but also allows for passwords to be written as command line arguments. To follow suggested best practices, we'll prevent users from passing the password through the command line and instead only accept the password through a prompt."
Answer: 279.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: "{{MosaicTask}} fails with an assertion error while generating diagnostic plots (if configured on the command-line).  {code}  INFO  2018-08-14T01:18:05.005 Mosaic ()(mosaicTask.py:705)- Output WCS Diagnostic Figures...  QXcbConnection: Could not connect to display localhost:11.0  Caught signal 6, backtrace follows:  /software/lsstsw/stack3_20171023/stack/miniconda3-4.3.21-10a4fa6/Linux64/utils/16.0-4-gd6aeece+1/lib/libutils.so(+0x15214) [0x7f5ac20df214]  /usr/lib64/libc.so.6(+0x362f0) [0x7f5b1f4812f0]  /usr/lib64/libc.so.6(gsignal+0x37) [0x7f5b1f481277]  /usr/lib64/libc.so.6(abort+0x148) [0x7f5b1f482968]  /software/lsstsw/stack3_20171023/python/miniconda3-4.3.21/lib/python3.6/site-packages/PyQt5/../../../libQt5Core.so.5(+0x92a8e) [0x7f5b04d61a8e]  /software/lsstsw/stack3_20171023/python/miniconda3-4.3.21/plugins/platforms/../../lib/libQt5XcbQpa.so.5(QXcbConnection::QXcbConnection(QXcbNativeInterface*, bool, unsigned int, char const*)+0x706) [0x7f5ae63a1cc6]  /software/lsstsw/stack3_20171023/python/miniconda3-4.3.21/plugins/platforms/../../lib/libQt5XcbQpa.so.5(QXcbIntegration::QXcbIntegration(QStringList const&, int&, char**)+0x30d) [0x7f5ae63a500d]  /software/lsstsw/stack3_20171023/python/miniconda3-4.3.21/plugins/platforms/libqxcb.so(+0x14db) [0x7f5ae66bc4db]  /software/lsstsw/stack3_20171023/python/miniconda3-4.3.21/lib/python3.6/site-packages/PyQt5/../../../libQt5Gui.so.5(QPlatformIntegrationFactory::create(QString const&, QStringList const&, int&, char**, QString const&)+0x10b) [0x7f5afae92a4b]  /software/lsstsw/stack3_20171023/python/miniconda3-4.3.21/lib/python3.6/site-packages/PyQt5/../../../libQt5Gui.so.5(QGuiApplicationPrivate::createPlatformIntegration()+0x45c) [0x7f5afae9f8fc]  /software/lsstsw/stack3_20171023/python/miniconda3-4.3.21/lib/python3.6/site-packages/PyQt5/../../../libQt5Gui.so.5(QGuiApplicationPrivate::createEventDispatcher()+0x2d) [0x7f5afaea048d]  /software/lsstsw/stack3_20171023/python/miniconda3-4.3.21/lib/python3.6/site-packages/PyQt5/../../../libQt5Core.so.5(QCoreApplicationPrivate::init()+0x818) [0x7f5b04f3bae8]  /software/lsstsw/stack3_20171023/python/miniconda3-4.3.21/lib/python3.6/site-packages/PyQt5/../../../libQt5Gui.so.5(QGuiApplicationPrivate::init()+0x1c) [0x7f5afaea0e3c]  /software/lsstsw/stack3_20171023/python/miniconda3-4.3.21/lib/python3.6/site-packages/PyQt5/../../../libQt5Widgets.so.5(QApplicationPrivate::init()+0x9) [0x7f5ae6c1adb9]  /software/lsstsw/stack3_20171023/python/miniconda3-4.3.21/lib/python3.6/site-packages/PyQt5/QtWidgets.so(+0x353b69) [0x7f5ae771ab69]  /software/lsstsw/stack3_20171023/python/miniconda3-4.3.21/lib/python3.6/site-packages/PyQt5/QtWidgets.so(+0x353c39) [0x7f5ae771ac39]  /software/lsstsw/stack3_20171023/python/miniconda3-4.3.21/lib/python3.6/site-packages/sip.so(+0x7f08) [0x7f5b058d4f08]  /software/lsstsw/stack3_20171023/python/miniconda3-4.3.21/bin/../lib/libpython3.6m.so.1.0(+0xda2ac) [0x7f5b2041f2ac]  {code}    This is due to the removal of the code that sets the matplotlib backend (DM-14159)."
Answer: 1558.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: "Remove future usage in {{base}} package."
Answer: 1456.0

User story: "In discussions with [~<USER> about temporary-scratch-repo use cases, we identified that it would be nice to have a Registry implementation that supports only generalized get and put (not expressions), and hence does not need DataUnit tables.  This is similar in functionality (but not implementation) to a previous LimitedRegistry concept that we envisioned not using SQL at all; the new concept would use SQLite, but would have only a subset of the full Registry schema.    Whether there are any non-DataUnit tables we could drop from LimitedRegistry is an open question; one possibility is that it could also only represent a single Collection, and hence have no need for DatasetCollection either."
Answer: 42920.0

User story: "Run jointcal with S18 HSC-PDR1 reprocessing single frame results.     The software version and config: TBD"
Answer: 510195.0

User story: "The pipelines.lsst.io documentation is topic-based, which means that each type of content needs to have a corresponding template. This ticket is to create a template for task documentation.    The template itself will be in https://github.com/lsst/templates and documentation will be added to https://developer.lsst.io/stack/task-topic-type.html"
Answer: 110819.0

User story: "Finished up csum methods in Forwarder, on branch jbparsons_csum_additions."
Answer: 13.0

User story: Testing the stack with Python 3.7 fails when building {{utils}}.    Python 3.7 requires boost 1.68 (DM-15385). To reproduce:    * Install lsstsw using {{bin/deploy -b}} to get the "bleeding edge" conda packages.  * Rebuild utils with boost 1.68: {{rebuild -r tickets/DM-15385 utils}}    This will hang during the utils {{test_cache.py}} tests. The hang occurs even with optimization disabled in {{utils}}. I have not tried to disable boost optimization.
Answer: 2972.0

User story: "DM-15139 standardized the method for returning an inverse transform to {{inverted}} but left the old {{getInverse}} and {{invert}} methods for backwards compatibility (even though all DM stack code was updated).    Please remove the deprecated methods after a suitable time period has elapsed, e.g. after the next major release."
Answer: 182897.0

User story: "This ticket covers fixes to nbreport and LTD Keeper as the notebook-based report system is being integrated with the api.lsst.codes/nbreport server in end-to-end publication trials (DM-15306)."
Answer: 711.0

User story: "This ticket is to deploy a proof-of-concept report to show off the notebook-based reporting system. [~<USER> created a notebook based on the characterization report that consumes data from the SQUASH API (https://gist.github.com/SimonKrughoff/0ada129d858dd92e9a46acea310612b2). I'll use that as the starting point. "
Answer: 1856.0

User story: "Fix Characterization Report for 16.0 in pipelines.lsst.io"
Answer: 21.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: "They should go in afw instead, so we can reverse the dependency.    We could also consider putting them in a third package (possibly a new one).    Might want to remove the old Gen2 Formatters from afw first (DM-7667) first to avoid confusion."
Answer: 1054348.0

User story: "This subpackage depends on Gen2 and a lot of science pipelines primitives.  Move it out of daf_butler; one reasonable new home would be obs_base."
Answer: 590584.0

User story: "When the crosstalk correction code was moved to above CCD assembly the routine {{extractAmp}} was changed to work on un-assembled CCDs.  This broke measureCrosstalk (this is hard to fix nicely until DM-15409 is resolved).    Additionally, {{measureCrosstalk}} assumes that you have enough data to constrain all the crosstalk coefficients, and has no way to write the outputs.  Please fix these while you have the package open."
Answer: 5967.0

User story: Change in SQuaSH production database requested by [~<USER>:  {noformat}MySQL [squash]> update job SET env=JSON_SET(env, "$.version_tag", "w_2018_30") WHERE job.id='1633';  Query OK, 1 row affected (0.01 sec) Rows matched: 1 Changed: 1 Warnings: 0     MySQL [squash]> update job SET env=JSON_SET(env, "$.version_tag", "w_2018_30") WHERE job.id='1634';  Query OK, 1 row affected (0.01 sec) Rows matched: 1 Changed: 1 Warnings: 0    MySQL [squash]> update job SET env=JSON_SET(env, "$.version_tag", "w_2018_30") WHERE job.id='1635';   Query OK, 1 row affected (0.01 sec) Rows matched: 1 Changed: 1 Warnings: 0    MySQL [squash]> update job SET env=JSON_SET(env, "$.version_tag", "w_2018_30") WHERE job.id='1636';   Query OK, 1 row affected (0.01 sec) Rows matched: 1 Changed: 1 Warnings: 0    MySQL [squash]> update job SET env=JSON_SET(env, "$.version_tag", "w_2018_30") WHERE job.id='1637';  Query OK, 1 row affected (0.01 sec) Rows matched: 1 Changed: 1 Warnings: 0    MySQL [squash]> update job SET env=JSON_SET(env, "$.version_tag", "w_2018_30") WHERE job.id='1638';  Query OK, 1 row affected (0.01 sec)Rows matched: 1 Changed: 1 Warnings: 0{noformat}
Answer: 5.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: [~<USER> and I noticed that running {{mosaic.py}} with {{numCoresForReadSource}} >1 no longer works, it hangs forever, results in timeout like below:    {code:java}  Traceback (most recent call last):    File "/software/lsstsw/stack3_20171023/stack/miniconda3-4.3.21-10a4fa6/Linux64/meas_mosaic/16.0-6-ged8029f+4/bin/mosaic.py", line 5, in <module>      MosaicTask.parseAndRun()    File "/software/lsstsw/stack3_20171023/stack/miniconda3-4.3.21-10a4fa6/Linux64/pipe_base/16.0-6-g44ca919+2/python/lsst/pipe/base/cmdLineTask.py", line 575, in parseAndRun      resultList = taskRunner.run(parsedCmd)    File "/software/lsstsw/stack3_20171023/stack/miniconda3-4.3.21-10a4fa6/Linux64/pipe_base/16.0-6-g44ca919+2/python/lsst/pipe/base/cmdLineTask.py", line 224, in run      resultList = list(mapFunc(self, targetList))    File "/software/lsstsw/stack3_20171023/stack/miniconda3-4.3.21-10a4fa6/Linux64/meas_mosaic/16.0-6-ged8029f+4/python/lsst/meas/mosaic/mosaicTask.py", line 80, in __call__      result = task.run(*args)    File "/software/lsstsw/stack3_20171023/stack/miniconda3-4.3.21-10a4fa6/Linux64/meas_mosaic/16.0-6-ged8029f+4/python/lsst/meas/mosaic/mosaicTask.py", line 1054, in run      numCoresForReadSource, readTimeout, verbose)    File "/software/lsstsw/stack3_20171023/stack/miniconda3-4.3.21-10a4fa6/Linux64/meas_mosaic/16.0-6-ged8029f+4/python/lsst/meas/mosaic/mosaicTask.py", line 871, in mosaic      readTimeout, verbose)    File "/software/lsstsw/stack3_20171023/stack/miniconda3-4.3.21-10a4fa6/Linux64/meas_mosaic/16.0-6-ged8029f+4/python/lsst/meas/mosaic/mosaicTask.py", line 554, in readCatalog      resultList = pool.map_async(worker, params).get(readTimeout)    File "/software/lsstsw/stack3_20171023/python/miniconda3-4.3.21/lib/python3.6/multiprocessing/pool.py", line 640, in get      raise TimeoutError  {code}    Stack version {{w_2018_30}} was used.     FWIW, I was able to run the same thing using only 1 core for reading source catalog ({{--numCoresForReadSource=1}}).  
Answer: 5315.0

User story: "Add {{lsst_dm_stack_demo}} so that it is run as a part of standard continuous integration.  This will remove the need to have the demo run as an afterburner."
Answer: 57769.0

User story: "After {{flake8}}, {{API tests}} and \{docker image}} build passed, deliver to docker hub the resulting image. Use tag {{tickets-DM-####}} for PRs and tag {{latest}} when the PR is merged to master."
Answer: 26190.0

User story: "[~<USER> reports that he may be seeing cases where {{setConfigRoot}} is not updating anything, resulting in the temp directory from DM-15372 being ignored.  Investigate this problem and add more tests. Also investigate removal of an unnecessary line in config.py constructor that may be confusing things."
Answer: 4165.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: "Something seems to not be quite right in the calculation of cross-correlations in {{MakeBrighterFatterKernelTask}}, as the sum of the cross-correlations are coming out much higher than they should be (I think, based on the code it was ported from at least).    Find out why, and once that's done, put the config value {{xcorrCheckRejectLevel}} back to the nominal value of 0.2 (or was it 0.1, check Will's code), if appropriate."
Answer: 105221.0

User story: "Bost 1.67 renamed the boost python library to {{libboost_python36}}. This leads to Galsim 1.66 to fail to build because it can't find that library. The SConstruct needs to be patched to add the new name as an option."
Answer: 5451.0

User story: "The MOC display doesn't show correctly when 'Galactic' is selected from the image viewer.          Implemented:    this development fixed the MOC display bugs in Galactic coordinate system by converting the world point with the same coordinate system as that of the project center while finding some pixel alongside the great circle passing the given projection center and a world point.    test:  do hips image search and get moc display in galactic coordinate system."
Answer: 1037.0

User story: "The main improvement is in the test steps formatting:   * have them in a table   * differentiate the steps from an included test case         However, more changes are required in order to make the generation of the document consistent with the approach described in https://confluence.lsstcorp.org/display/DM/DM+Test+Approach "
Answer: 86323.0

User story: "Python DAX containers should consume stack containers and build their own containers based off of them. In this case, they will look like normal setuptools packages, installable by {{python setup.py install}} - though it may be nice to upload them to PyPI also (alternatively https://python-packaging.readthedocs.io/en/latest/dependencies.html).    This includes:  dax_webservcommon  dax_imgserv  dax_metaserv    and dax_webserv, if applicable.    Once this is finished, PyJWT and cryptography should be removed from the conda dependencies.    Pay attention to testing and also the use of Travis is a goal as well. We may also need to think about how version.py is handled (look into versioneer)"
Answer: 47442.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 testing Boost 1.68 in DM-15385, afw fails to build almost immediately because of failures in {{lsstGil.h}}.    {code}  include/lsst/afw/image/lsstGil.h:119:34: error: macro "GIL_DEFINE_BASE_TYPEDEFS" requires 3 arguments, but only 2 given  {code}    In v1.68 {{GIL_DEFINE_BASE_TYPEDEFS}} gains a new argument in the middle:    {code:c}  // B - bits size/signedness, CM - channel model, CS - colour space, LAYOUT - pixel layout  // Example: B = '8', CM = 'uint8_t', CS = 'bgr,  LAYOUT='bgr_layout_t'  ...  #define GIL_DEFINE_BASE_TYPEDEFS(B, CM, CS)  {code}    This is not documented as a breaking change so I wonder if we are using internal APIs here. The immediate fix would be to add the channel model definition to our header file, but it would be preferable to use a public API if one exists since that might also work for boost 1.66 (that we are currently using).  
Answer: 21228.0

User story: "We want to migrate the manual deployments out of docker on qserv-dax01 and into the kubernetes PDAC cluster, so that they restart and are properly routed and all that good kubernetes stuff.    This will enable later work to get the builds into CI, and we'll have something to call to deploy them automatically after that.    Exit critiera; Check in service and other definitions to enable this, and have it running on the PDAC cluster."
Answer: 31726.0

User story: Using sconsUtils with Python 3.7:  {code}  /sconsUtils/16.0-1-gd93e90d/python/lsst/sconsUtils/builders.py:202: FutureWarning: Possible nested set at position 11    files_expr += "-name %s -prune" % re.sub(r"(^|[^\\])([[*])", r"\1\\\2", file)  {code}
Answer: 5791.0

User story: "PyYAML 1.11 does not seem to build with Python 3.7. v1.13 does build fine."
Answer: 20108.0

User story: "That feature is missing in the current implementation because we were not able to query specifications from the API until recently. See DM-15240."
Answer: 17664.0

User story: "Upgrade boost to v1.68 -- this will enable boost-python to build with python3.7 (we still need boost-python for galsim)."
Answer: 21425.0

User story: "This ticket covers the work to get an initial working deployment of https://github.com/lsst-sqre/sqre-uservice-nbreport on Google Kubernetes Engine in the api.lsst.codes cluster.    - Add {{/nbreport/}} to the Nginx gateway  - Add k8s configurations and secrets  - Demonstrate deployment"
Answer: 1312.0

User story: "This ticket covers the work to get an initial working deployment of https://github.com/lsst-sqre/sqre-uservice-nbreport on Google Kubernetes Engine in the api.lsst.codes cluster.    - Add {{/nbreport/}} to the Nginx gateway  - Add k8s configurations and secrets  - Demonstrate deployment"
Answer: 531.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: "So far we are not using parameters for datastore.get. This will have to change if we wish to support efficient subsetting of large datasets.  To be able to handle ChainedDatastores properly, parameters will need to be able to be handled by formatters, and generically by using code in StorageClass assembler classes. This requires that the formatter (which will be called first) has to be able to indicate which parameters it has already handled before the remaining parameters are passed to the assembler class."
Answer: 50026.0

User story: "It is necessary for a datastore to be able to specify a list of datasetTypes that are supported, or a list that are unsupported. For posixdatastore this can currently happen by a StorageClass not being listed as a formatter, but a more general approach is needed. In particular, it may be that an InMemoryDatastore should only cache a subset of datasettypes when used as part of a ChainedDatastore.    I think we need to support allow lists and deny lists, although it only makes sense to specify one of those options in a particular configuration (allow means only those listed should be allowed so deny becomes superfluous)."
Answer: 360394.0

User story: "Some of the butler/datastore tests use a fixed name for the datastore root. Now that we are regularly building daf_butler on Jenkins we are getting test failures due to race conditions since now test methods using the same root are running in parallel. Modify the tests to use a different root in {{setUp}}."
Answer: 1049.0

User story: "Based on the DCR-corrected templates generated in DM-15370, reprocess HiTS 2015.    Also reprocess the HiTS 2015 data with direct-coadd templates.    Then compare the results."
Answer: 190204.0

User story: "Based on the reprocessed HiTS 2014 data from DM-15080, and the DCR-corrected template construction code from [~<USER>, build DCR corrected templates."
Answer: 171569.0

User story: "The alert DB is currently light on requirements ([~<USER> is working on that), but we know that at least we need some system that is capable of receiving all the alerts we generate and providing some minimal query capability over them (by alert ID, time, position, for example). What technologies are available that might address this? We could consider e.g.    * A conventional RDBMS (Oracle, MySQL, PostgreSQL, ...)  * A document store (MongoDB, CouchDB, ...)  * A filesystem and tar, plus some other index database  * A object store, plus some other index database  * Something else!    Look at some websites, do some brainstorming, and see if there are any obvious contenders."
Answer: 124524.0

User story: "Following DM-15053, we are running each filter in a separate Docker container, talking to a local (per-node) Kafka system.    But... how many filter-containers can we run on each node? Currently we're using 20, but how far can we go (order of magnitude is fine — obviously, it'll be hardware dependent at some level)?"
Answer: 40290.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: "Try to use {{makeButlerRepo.py}} on NCSA Oracle database to create (empty) schema."
Answer: 184513.0

User story: "For expediency we (mostly me) haven't been as diligent in making sure our {{Registry}} ABC stayed up to date with changes to {{SqlRegistry}}.  Update it."
Answer: 3005.0

User story: "On DM-15350 it was suggested by [~<USER> to standardize on one kind of quotes. Subsequent discussion on Slack revealed a preference for double quotes.  Update the code to use them wherever possible (e.g. nested quotes can use single)."
Answer: 70.0

User story: "Routines that parse raw FITS metadata in the form of PropertyLists sometimes (but not always) provide an option to strip parsed keywords.  This functionality should be extended to all such routines, and we should also provide routines to strip without constructing objects in cases where the latter is expensive.  Finally, ExposureInfo needs to provide a routine to parse and/or strip metadata that delegates to all of its children."
Answer: 100614.0

User story: "That's required now that we handle datasets with multiple filters. Instead of selecting the {{filter_name}} afterwards in the bokeh application for display it should be possible to apply this filtering when querying the {{/monitor}} and {{/code_changes}} resources in the API.    This implementation is an work around until we have a proper dataset model in SQuaSH (DM-15317)"
Answer: 1457.0

User story: "Currently fgcmcal calibrates slot_ApFlux_flux, and this is not configurable.  I see that (a) this should be slot_CalibFlux_flux by default, and (b) should be configurable."
Answer: 64.0

User story: "Respond to any technical questions; ensure PoC is headed in a direction to produce useful results."
Answer: 51621.0

User story: "Write code to fit COSMOS galaxies with pyprofit, both as a code test and to build a catalog of bulge-disk decompositions for testing of fitting LSST-quality images.    The COSMOS galaxies were chosen because they have HST and deep HSC data. We are using fits to the HST images as the truth because they have better spatial resolution, which makes deblending and fitting small galaxies easier."
Answer: 184407.0

User story: "Describe the process for getting an LSP account at the LDF by the self registration mechanism."
Answer: 53.0

User story: "https://project.lsst.org/meetings/lsst2018/content/interfacing-prompt-products-database"
Answer: 9803.0

User story: "After merging DM-15098 it was found that {{sphgeom::HtmPixelization::pixel}} causes a segfault when called on Linux.  Some investigation has shown that this bug was prexisting (and not unit tested) and caused by an upstream pybind11 bug (https://github.com/pybind/pybind11/issues/1132).  Until that is fixed, work around it by changing the holder type of all {{sphgeom::Pixelization}} subclasses to {{std::unique_ptr<T>}}."
Answer: 1342.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 multi-Gaussian approximations to the exponential and de Vaucouleurs profile as in Hogg & Lang 2013 ([http://adsabs.harvard.edu/abs/2013PASP..125..719H|http://adsabs.harvard.edu/abs/2013PASP..125..719H)])."
Answer: 165619.0

User story: "1. [x] Write up a document detailing the conceptual needs for a set of datasets to test DRP+AP at CI, Small, Medium, and Large scales.  2. [x] Define the requirements and goals of those scales  3. [x] Discussion connection to previous DM-SST dataset-definition work.  This will be more fully elaborated on in DM-15448.  4. [x] Provide examples.  5. [x] Discuss limited runs on individual machines (laptop, desktop, medium AWS Jenkins worker node)  "
Answer: 21484.0

User story: "Convert meas_base to numpydoc format."
Answer: 216018.0

User story: "In the SummaryState event for atHeaderService, the SummaryStateValue should be filled using the summary state enumeration available in the CSC library for the correct state transition."
Answer: 4600.0

User story: "Provide instructions on how to use the test management in Jira:   * test case    * test plan and runs         Describe the procedures involved in the generation and approval of the Test Specification and Test (Plan and) Report."
Answer: 19935.0

User story: "Processing HSC PDR1 for DM-11787 resulted in one obviously bad astrometric fit: HSC-Y tract 15832. The jointcal log ({{/project/parejkoj/DM-11783/logs/jointcal-SSP_WIDE_15832_HSC-Y-141536.2.log}})  shows a number of questionable entries leading up to the  poor final {{chi2/ndof=827}}. This ticket is to investigate why the fit was bad and see what we can do to mitigate that. A first step might be simply re-running on a newer processing of that data."
Answer: 35855.0

User story: "Several methods of the new {{DcrModel}} class need unit tests written for them."
Answer: 449731.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: In order to use DataUnit objects inside DatasetType and DataId objects on DM-15034, we need to make it possible to construct a DataUnitRegistry without having a Registry instance.  In many ways that makes DataUnitRegistry analogous to StorageClassFactory, and hence we should follow the same approach: make it an append-only singleton.    This is complicated by the fact that Schema and DataUnitRegistry are closely intertwined; DataUnit objects actually currently have some SQLAlchemy objects attached to them.  We'll have to remove those as part of this ticket, and instead attach them to Schema in a way that allows it to retrieve them with DataUnit objects or names as keys.    The recommended implementation plan is roughly:   * Move the "tables" sections out of the individual DataUnit sections in schema.yaml into the main "tables" section at the end; this should break at most a tiny bit of the parsing logic for that configuration (and possibly nothing).   * Remove the "foreignKey" sections nested under "link" sections in the yaml; instead generate these programmatically.   * Split the DataUnit content (now free of any SQL-specific stuff) into its own yaml file; adjust the levels of both dataUnits.yaml and schema.yaml appropriately (e.g. remove the now-superfluous "tables" section heading?).   * Change SchemaBuilder so SQLAlchemy objects are put somewhere in Schema where they can be looked up via DataUnit name or object, instead in the DataUnit objects themselves.  Fix whatever this breaks in SqlRegistry and SqlPreflight.
Answer: 44301.0

User story: "Build and Test SAL code for OCS Integration of Spectrograph Image Creation Components"
Answer: 5777.0

User story: "To improve performance of image display in Firefly, allow an afwDisplay instance with the Firefly backend to track {{display.scale}} and {{display.pan}} settings that precede {{display.mtv}}, and apply these at the time of image display. Also add a small correction to the pan method so that it uses the LSST pixel coordinate convention.    Implemented:    Modify the {{display_firefly}} backend to remember the results of scale (stretch) commands, and to apply scale and pan parameters when displaying an image with {{lsst.afw.display.mtv}}.   * Remember and apply the serialized RangeValues string that Firefly uses   * Correct pan command by 0.5 pixels to follow LSST convention   * Apply the remembered pan position when using {{mtv}}   * Make {{'slate.html'}} the default if it is not passed explicitly or if the environment variable {{FIREFLY_HTML}} is not defined. This is necessary for Firefly to show readout of LSST pixel convention."
Answer: 4251.0

User story: "Create a prototype JSON representation of all the footprints in an LSST SourceCatalog, for the regular footprints only (excluding heavy footprints), for use in Firefly.    Include bounding box information as well as the details of the individual pixels included in each footprint. Coordinate with development of DM-15326."
Answer: 65062.0