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 originally put the executionOrder parameter (which determines when a plugin is run, relative to others), in the config object, simply because that's where it was in the old framework.  But it's really not something that should be configurable, as it depends only on the inputs the algorithm needs, which don't change."
Answer: 12704.0

User story: DDL information is embedded as comments in the master version of the schema (in "cat" repo). Currently we are only using it for schema browser. This story involves designing the procedure involving loading DDL information into MetaServ. We need to be ready to support a variety of scenarios: * we are getting already preloaded database, need to just load metadata about it to metaserv (we might have the original ascii file with extra information, or not) * we are starting from scratch, need to initialize database (including loading schema), and need to load the information to the metaserv * we already have the database and metadata in metaserv, but we want to change something (eg. alter table, or delete table, or delete database).
Answer: 71291.0

User story: "After removing the old measurement framework in meas_algorithms, we should also end support for version=0 Schemas in memory, and instead convert version=0 Schemas to version 1 when we unpersist them."
Answer: 231790.0

User story: "We can make address a lot of dependency issues if we move the Source classes to meas_base, because we'll no longer have low-level code (e.g. afw::table persistence) in the same module as very high-level code (e.g. slots).   It will also put all the slot code in the same place, instead of spreading it across two pacakges.  This should be straightforward, except that we'll have a lot of downstream code to (trivially) change, and there's a good chance Swig will get confused somewhere along the way."
Answer: 50641.0

User story: "While working on DM-1218 and DM-464, I've grown quite dissatisfied with the current state of the slot and alias mechanisms, and we now have a concrete proposal for larger-scale changes on RFC-11.  Unfortunately, I don't think we'll be in a good position to do much about this until we've completed the transition to meas_base and removed the old measurement framework in meas_algorithms."
Answer: 807883.0

User story: "In order to make GalSim eups distrib installable on OSX, we need to use install_name_tool on anaconda's dynamic libraries to make sure that they point to the right place.  In most cases, this can be handled by changing anaconda's eupspkg.cfg.sh.    When lsstsw is deployed, it clones and builds anaconda independent of EUPS.  Therefore, the deploy script in lsstsw must also be changed to use install_name_tool in the case where it is being deployed on lsstsw.  There will be two branches associated with this ticket: One in lsstsw to alter the deply script. One in anaconda to alter eupspkg.cfg.sh"
Answer: 10391.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: - import sui.sql.bzip2.out (produced by Serge) into MySQL for DeepSource and DeepForcedSource tables: - remove columns chunkId and subChunkId for each chunk table - merge all chunk table into the main table - join DeepSource and DeepForcedSource to add coordinates of DeepSource (director) object in DeepForcedSource table. then dump  DeepSource and DeepForcedSource  to files DeepSource.csv and DeepForcedSource.csv {code:sql} SELECT f.*, COALESCE(s.ra, f.ra), COALESCE(s.decl, f.decl) FROM DeepForcedSource f LEFT JOIN DeepSource s ON (f.deepSourceId = s.deepSourceId) INTO OUTFILE '/db1/dump/DeepForcedSource.csv' FIELDS TERMINATED BY ',' OPTIONALLY ENCLOSED BY '"' LINES TERMINATED BY '\n'; {code} - Load this file using Qserv loader.  A sample should be made and tested first to validate this procedure. This sample could be added in qserv_testdata
Answer: 10151.0

User story: "It's difficult to load manually data in Qserv, so a way to do that is to use integration test framework to automatically do this.  Big data file won't be stored in git, but the user wil lhave to retrieve them manually, and the test case won't be executed by integration tests."
Answer: 17161.0

User story: "After the repository split, changes are required to get the auto build tool to work properly. Firefly and Firefly based applications are built using Gradle system.  "
Answer: 34037.0

User story: "This captures some miscellaneous minor cleanups I made to meas_base test code while working on DM-1725; I decided I didn't want to pollute the tiny but high-priority fix for that branch with the larger, mostly aesthetic changes here."
Answer: 4638.0

User story: "The following external packages (and one DMS package) add to LD_LIBRARY_PATH for Linux but do not add to DYLD_LIBRARY_PATH for MacOS X.  To the extent that these packages are for the Qserv server only, this may be acceptable, but in general we should try to have all packages portable whenever possible.  Accordingly, I plan to modify the table files for all but xrootd.  * libevent * log * log4cxx * protobuf * sqlite * xrootd * zookeeper"
Answer: 106.0

User story: "We still see noise artifacts in some deblended images on the LSST side when running the M31 HSC data.  They look like the result of running NoiseReplacer on HeavyFootprints in which the children can extend beyond the parents.  This was fixed on the HSC side on DM-340 (before the HSC JIRA split off), and I *think* we just need to transfer the fix to LSST."
Answer: 100677.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: "Please see next discussion: https://github.com/LSST/qserv/commit/bcee8f2ebd348f6c260bf377d5a3ff09d68fc337#commitcomment-9161198  A counter per Qserv instance, kept centrally and persistent over restarts, is one alternative, but it could have performance problems with multiple czars. A counter per czar, still persistent, along with a czar identifier, would be better. Another could be a hash of the query; with anywhere from 160 to 512 bits, collisions should be negligible. I don't know if that would make the table name too long. "
Answer: 44.0

User story: "We want to alert people who are just using a newinstall.sh they have lying around (old or hacked up or...) that they are not using the official server version.  "
Answer: 579195.0

User story: "Do the following:  - refactor fftools to allow for specialized viewers. - make a generic fftools viewer. - make an irsaviewer package in ife-new that will build. - generalize the catalog search and add factories to access the lsst search process. "
Answer: 5637.0

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

User story: As discussed on DM-1220, the table files for:  - mysqlproxy  - protobuf  - lua  - expat should have the MANPATH entry removed entirely, while:  - xrootd should have ":" added to the end of its MANPATH value, to allow the default paths to be searched as well.
Answer: 1360542.0

User story: "Take prior research and come up with rough firefly migration proposal.  Include how to use a hybrid system for foreseeable future. Write some prototype code."
Answer: 51149.0

User story: "- Make GitHub firefly ready but not public - Add firefly to LSST git - Clean up any lingering issues from separation - break up IRSA Viewer from Firefly Viewer"
Answer: 50236.0

User story: "The stack fails to build with gcc 4.8, with a test failure in meas_base (though a similar problem on the HSC fork suggests the problem is actually in afw).  [~<USER> reports that on OpenSuse 13.1, the failure goes away when compiling with opt=1 instead of the default opt=3, indicating that the problem is overly aggressive optimization.  This, and the fact that a traceback of the HSC-side failure implicates MaskedImage::getXY0, leads me to guess that something is going wrong with the alignment of the Eigen data members in afw::geom::Point.  Until that theory is disproven, this probably belongs in my court, though I'd be happy to let someone steal it from me if they're interested in working on it."
Answer: 42788.0

User story: "This option should be required only if there are compressed files given as input."
Answer: 2183175.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: "Suggestions:  * provide --keep-input-data option, * replace --chunks-dir option with --work-dir, because it's also used for non partitioned data, and remove default value so that the user is aware where data are stored. * in cfg files part.id and dirColName seems to have the same semantics: double check and if yes, use only one parameter. * comment each field in an example cfg file and explain what is required by partitioner, duplicator, css or other loader components."
Answer: 2939447.0

User story: Following discussion on qserv-l, we only need to generate "secondary" index for director table, no other table is supposed to have it. Need to modify data loader to recognize which table is director table and generate index only for that table. 
Answer: 34705.0

User story: "{{eupspkg}} currently has all product eupspkgs (tarballs) in a single directory:   {code}  /products/{PRODUCT_NAME}-{VERSION}.eupspkg  {code}  This is not going to scale well as we go to many packages and many versions of each.  It already takes a long time to load {{https://sw.lsstcorp.org/eupspkg/products/}}.  Perhaps we should change to at least   {code}  /products/{PRODUCT_NAME}/{PRODUCT_NAME}-{VERSION}.eupspkg  {code}  ?    This change would have to happen in {{eups/python/eups/distrib/eupspkg.py}} and would be incompatible with the current distserver, obviously, although both could be maintained (even in the same URL hierarchy)."
Answer: 2396868.0

User story: "Need to properly implement query killing through Ctrl-C"
Answer: 197374.0

User story: "Apparently killing a query through Ctrl-C is confusing xrootd. Disable query killing (which seems to be only partly implemented)."
Answer: 100553.0

User story: Schema browser displays detailed info about schema, including custom fields like UCD, units etc. This information is stored as comments embedded in the master version of the schema (in "cat" repo). Currently we are generating ascii from the master schema for schema browser, and we load it into mysql, then schema browser reads it from mysql. This story involves changing schema browser such that it will read the schema information directly from MetaServ.
Answer: 156738.0

User story: {code} from lsst.afw.table import BaseCatalog, Schema  s = Schema() c1 = BaseCatalog(s) c2 = BaseCatalog(s)  c1.extend(c2) {code}  The above fails, saying:  {code} Traceback (most recent call last):   File "test.py", line 7, in <module>     c1.extend(c2)   File "/Users/jds/Projects/Astronomy/LSST/stack/DarwinX86/afw/10.0+3/python/lsst/afw/table/tableLib.py", line 6909, in extend     _tableLib.BaseCatalog_extend(self, iterable, deep) ValueError: invalid null reference in method 'BaseCatalog_extend', argument 3 of type 'lsst::afw::table::SchemaMapper const &' {code}
Answer: 135.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 sort results, because we can't always rely on ORDER BY. So we need a formatting per query in the integration tests (sort result for some, don't sort for others etc.)    The following queries have been disabled because we don't have result sorting, so once it is implemented, we will need to re-enabled them prior to closing this ticket:  {code}  case02/queries/0003_selectMetadataForOneGalaxy_withUSING.sql  case02/queries/3001_query_035.sql  case02/queries/3008_selectObjectWithColorMagnitudeGreaterThan.sql  case02/queries/3011_selectObjectWithMagnitudes.sql  case02/queries/3011_selectObjectWithMagnitudes_noalias.sql  {code}"
Answer: 321176.0

User story: "Examine fqdn/hostname assignment for OpenStack instance"
Answer: 57722.0

User story: "Clone OpenStack volume for use against multiple instances"
Answer: 26274.0

User story: "Create read only OpenStack volume and execute processing scenario"
Answer: 26277.0

User story: "* A quick proof-of-concept prototype of loading tool for loading database-information into metadata store.   * Handling mysql credentials through auth file in home dir instead of hardcoded values."
Answer: 92305.0

User story: "Define appropriate interfaces and connect them with the RESTful API (see DM-1695)."
Answer: 101885.0

User story: "Implement proof of concept, skeleton of the prototype. The work will continue in follow up stories in February and in S15."
Answer: 61653.0

User story: "The facade was lacking the ability to retrieve per-table overlap parameters. This ticket adds that capability. The RelationGraph code also relied on overlap when determining whether a query was evaluable. This ticket updates the RelationGraph code to use the per-table overlap info."
Answer: 1552280.0

User story: "DM-854 exposed an issue in handling large results. Result rows are returned from worker to czar in protobufs messages. However, protobufs messages should not be larger than some number of megabytes, according to protobufs documentation. IOW, protobufs is not designed to handle messages on the order of hundreds of megabytes. There may be some code in the protobufs implementation that does not scale beyond messages of a few megabytes. Hence, in order to send larger amounts of result rows, we need to use multiple messages. The current protobufs definition for result messages includes a placeholder for chaining result messages, but there is no code on the czar or worker that implements result chaining.   The scope of this ticket is to implement message chaining for results on the worker and on the czar, in such a way that it places no limits on the overall number of result rows (if there is a limit, it should be no smaller than quadrillions and be well-documented).  "
Answer: 189976.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: For now Qserv CSS version is defined 3 times, this is not good:  {code:bash} core/modules/css/constants.h:char const VERSION[] = "1"; ///< Current supported version core/modules/css/Facade.cc:// NOTE: THIS NUMBER MUST MATCH VERSION DEFINED IN qservAdmin.py. core/modules/css/Facade.cc:const int VERSION = 1; core/modules/css/Facade.cc:const std::string VERSION_STR = boost::lexical_cast<std::string>(VERSION); qserv@clrinfoport09:~/src/qserv (u/fjammes/DM-627 *) $ grep -rw VERSION admin/python/ admin/python/lsst/qserv/admin/qservAdmin.py:# NOTE: THIS NUMBER MUST MATCH VERSION DEFINED IN CSS/FACADE. admin/python/lsst/qserv/admin/qservAdmin.py:VERSION = 1 {code}
Answer: 2187113.0

User story: "PsfAttributes.cc uses a local BBox; why not a parent bbox: {code} double PsfAttributes::computeGaussianWidth(PsfAttributes::Method how) const {     /*      * Estimate the PSF's center.  This *really* needs to be rewritten to avoid using MeasureSources;      * we shouldn't need to instantiate source objects just to measure an adaptive centroid!      */     afwImage::MaskedImage<double> mi = afwImage::MaskedImage<double>(_psfImage);     typedef afwImage::Exposure<double> Exposure;     Exposure::Ptr exposure = makeExposure(mi);      afwDetection::Footprint::Ptr foot = boost::make_shared<afwDetection::Footprint>(exposure->getBBox(         afwImage::LOCAL)); {code}  Measure.cc MeasureSources::apply: uses local BBox; why not PARENT? {code} source.setFootprint(refFoot->transform(*referenceWcs, *wcs, exposure.getBBox(afw::image::LOCAL))); {code} "
Answer: 137731.0

User story: "In afw Background.cc sets _imgBBox to the local bounding box. Why is this not the parent bounding box?"
Answer: 141352.0

User story: "QueryAction::Impl currently has a handful of private members/methods related to maintaining a collection of errors that occurs while processing a query (_addErrorMsg, IntString, IntStringVectory, _errors, etc.)  It would be useful to split this stuff out into a separate, re-usable utility class, and extend, then extend with some additional functionality (output stream operator, subclass from std::exception, maybe capture __LINE__ and __FILE__, integrate with logging, etc.)  [Fabrice: discuss requirements and basic design w/ Fritz and/or Daniel]"
Answer: 63248.0

User story: "Dependency on SWIG 2.0+ was introduced into Qserv, and this broke Qserv building on systems relying on SWIG 1.3.x.  This ticket introduces basic code to override SWIG_LIB on those systems to allow use of the broken installation (some SWIG search paths are fixed during its build process otherwise)."
Answer: 38639.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: "Pandas is well integrated with the other parts of SciPy: numpy, matlibpy, etc.  It’s a good candidate for data analysis, especially where time series are involved. However, there are no multidimensional columns, poor metadata support for FITS files and a need to use masks instead of NaN values. These may, or may not, be problems.  There is a 400 page book about Pandas, so it will take some further time to learn its value, especially with astronomical data in different situations."
Answer: 52191.0

User story: "Use a local database here at IPAC with 5 Qserv tables in it. Looked at several Python query interfaces. Used the pymysql interface for testing because it's pure Python and because I found reports suggesting it was almost as fast as the mysqldb interface that requires C language libraries.  Ad hoc queries can be constructed in three lines of code, so useable in a science environment.  Found a couple of bugs in Qserv that were reported."
Answer: 52192.0

User story: This works well, at least for a simple case. You can move directly from a query statement to a Pandas data frame for analysis in just a few lines of code. Here is the start of an iPython Qserv session showing how easy it is.  In [6]: import pandas as pd In [7]: import pymysql as db  In [8]: conn = db.connect(host='lsst-db1.ipac.caltech.edu',port=4040, user='qsmaster', passwd='', db='LSST')  In [11]: df = pd.read_sql("select deepCoaddId, tract, patch, ra, decl from DeepCoadd", conn)  In [12]: df Out[12]:     deepCoaddId  tract   patch        ra      decl 0      26607706      0  406,11  0.669945  1.152218 1      26673242      0  407,11  0.449945  1.152218 2      26804242      0   409,2  0.011595 -0.734160 3      26673154      0   407,0  0.449945 -1.152108 … 
Answer: 52194.0

User story: Used "pip" to install it. "Conda" should work as well. Therefore, it should be easy to make it part of the delivered system: VM, container, tar file, after the fact download, etc. It has documentation, uses the MIT license, under active development and available from PyPI. DB connection is straight forward and requires little experience to get meaningful work done.
Answer: 52194.0

User story: "LSE-70, the operations plan, contains decisions about the Cyber security. While not a complete program, it's now necessary to  revise the master plan to be consistent with the decisions embedded in that document. "
Answer: 2727609.0

User story: "researched the docushare traversing the plans for materials to be embedded in the OCS and similar systems, as well as extant operational plans. The goal was to understand how to separate the the security responsibilities of development, what security constraints ought to be but on items that are delivered, and what to tell the camera and telecscope teams  to mender ea smooth integration with IT security systems upon delivey and integration of their sub systems in Chile."
Answer: 439012.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: "Fix anything necessary for qserv dependencies to build on OS X with clang.  Note -- making qserv itself build is more complicated and may require a separate ticket."
Answer: 367712.0

User story: "The last change to ApertureFlux to make it work with the new C++ design changed ApertureFluxAlgorithm into an instantiatable class.  However, I have now figured out how to make this work with SWIG while still allowing measure and fail to be defined by default at the ApertureFlux level..  So this issue is to put things back in order."
Answer: 47556.0

User story: "{code:bash} fjammes@clrlsst-dbmaster-vm:~/src/qserv (u/fjammes/DM-627 $%) $ qserv-test-head.sh -h  Usage: qserv-test-head.sh [options]    Available options:     -h          this message     -q          quick: only rebuild/install new Qserv code,                 and perform test case #01    Rebuild from scratch, configure and run integration tests against   a Qserv git repository.   Pre-requisite:     source loadLSST.bash     setup qserv_distrib -t qserv     setup -k -r ${QSERV_SRC_DIR}    Can be used with 'git bisect' :     cd ${QSERV_SRC_DIR}     git bisect start     git bisect bad     git bisect good git-commit-id     git bisect run /home/fjammes/src/qserv_testdata/bin/qserv-test-head.sh {code}  Code is in DM-627 ticket branch."
Answer: 38898.0

User story: "Follow up metadata store schema development to ensure SUI will be able to use it. Define the fields that should go into Data Definition table. Define the fields that must be present in the image metadata table, which SUI will be searching."
Answer: 46282.0

User story: "buildbot's Web interface currently runs on port 8010 of lsst-buildx.ncsa.illinois.edu.  Various networks, including unsecured visitor and public networks, block access to unusual ports.  It would avoid problems on such networks if buildbot were to move to port 80 (HTTP) or port 443 (HTTPS)."
Answer: 1139109.0

User story: "Implement simplest use case for data loading with one or more worker database separate from czar database. Simplest means minimal functionality in what concerns access to workers, just assume for now that we can connect to every worker directly using regular TCP connection. It should be possible to just add a list of worker nodes as an option to loader script and send the chunks in some random order to the workers in that list. Of course chunks for different tables should end up on the same host, so some form of chunk management is needed (use for now whatever is defined in CSS doc on trac)."
Answer: 11516.0

User story: "- checkout the classes - understand the FITS standard and current implementation"
Answer: 51915.0

User story: "It looks like the code that would read FITS history and comment cards is being hidden by a check for empty values. Changing the order of these statements should result in the history and comment cards being put in the PropertyList structure."
Answer: 2897.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: According to https://confluence.lsstcorp.org/display/LDMDG/Getting+Started+in+DM  "Contact lsst-sysadmins _at_ lsst.org to set up the following..."  but I am getting:  {code} -------- Forwarded Message -------- Subject:  Undeliverable: new employee Date:  Mon, 8 Dec 2014 18:59:04 -0800 From:  Mail Delivery Subsystem <<EMAIL>>  *Delivery has failed to these recipients or groups:*  <EMAIL> <mailto:<EMAIL>> Your message wasn't delivered due to a permission or security issue. It  may have been rejected by a moderator, the address may only accept email  from certain senders, or another restriction may be preventing delivery.  The following organization rejected your message: isgsa-1.lsst.org. {code}   <EMAIL> is failing too:  {code} On 12/08/2014 07:04 PM, Mail Delivery Subsystem wrote:> *Delivery has failed to these recipients or groups:* >  > <EMAIL> <mailto:<EMAIL>> > The email address you entered couldn't be found. Please check the  > recipient's email address and try to resend the message. If the problem  > continues, please contact your helpdesk. >  > The following organization rejected your message: lists.lsst.org. {code}  What is the correct address? Can you fix it?  
Answer: 1564.0

User story: "Use an OpenStack instance to run an HTCondor Central manager"
Answer: 58916.0

User story: "1. discuss with IPAC director and managers to open source Firefly 2. study the major open source license,Apache, GPL, BSD 3-clause, MIT.  3. final decision: BSD-3 clause"
Answer: 60.0

User story: Document a procedure for building the stack on a new system in a way that is appropriate for both project members and external contributors.  This can be linked as a "getting started" guide from http://dm.lsst.org/.
Answer: 34589.0

User story: "Research popular web development technologies to prepare Firefly for the future with the focus on front-end framework. "
Answer: 1.0

User story: "Make sure CORS related headers are not sent when the Origin header is missing.  Firefox does not like it."
Answer: 1.0

User story: "Update build and deploy related scripts to reflects the changes affected by open sourcing of Firefly."
Answer: 52100.0

User story: The title says it all. Please open ticket for next release when closing this one.  Tasks to do:  - publish last buildbot build under a temporary eups-tag ("qserv-dev")and test it, if it works fine: - create git-tags for Qserv and dependencies - publish the release with eups-tags "qserv" and "YYYY_MM" - generate and publish the doc for release "YYYY_MM" - update release number in Qserv code and set "YYYY_MM+1" as release in dev and "YYYY_MM" as stable release (update {{admin/bin/qserv-version.sh}}, {{doc/source/conf.py}}, {{doc/source/toplevel.rst}}) - generate and publish the doc for release "YYYY_MM+1"  - look at the doc - commit  {{admin/bin/qserv-version.sh}}, {{doc/source/conf.py}}, {{doc/source/toplevel.rst}} with current ticket number   This procedure should be validated and documented.
Answer: 8804.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: Please implement a git hook to only allow pushes to master if they are: 1) non-fast-forward merge commits or 2) documentation fix commits with "#master-doc-fix" in the commit message.  This will prevent accidental fast-forward merges from confusing the master history.
Answer: 2448621.0

User story: "Email notices of new RFCs filed with a DM component go to dm-devel Email notices of new RFCs filed with a DM component go to Data Management chat room Email notices of all new RFCs go to Bot: RFC room "
Answer: 111681.0

User story: "* Create dbserv for handling database related web-based queries, support running queries through web (initial version).  * Integrate dbserv, metaserv and imgserv RESTful API into the webserv - want to run all services (meta, image, db) under one server.  * Also want to be able to run them separately, so have some handy servers for each service * Proof of concept for supporting multiple formats (html, json)"
Answer: 112299.0

User story: "The title says it all. Please open ticket for next release when closing this one."
Answer: 50072.0

User story: "I wasn't able to find documentation on how to create a new package, including things like where to find a template for a new package. "
Answer: 2188718.0

User story: "This is a follow u pto DM-1453, we need to add a unit test that will prove that mismatched versions in zookeeper and software are properly handled."
Answer: 19925.0

User story: "Implement Python library for creating mysql tables on all active workers."
Answer: 120787.0

User story: "Implement Python library which creates databases on all active workers based on info from CSS."
Answer: 112411.0

User story: "Provide Python interface for accessing information in CSS which is relevant to distributed management, such as database/table/node data. This interface can be used also by data loader and replicator."
Answer: 90588.0

User story: "To manage remote workers we need a way to access services on remote machines that run workers. Services may be something like mysql (which we would prefer to run without TCP port open) and optionally xrootd. This ticket will implement Python module which will hide a complexity of doing things like ssh/port forwarding/authentication from the client."
Answer: 80417.0

User story: "For management of the distributed databases/tables we need info in CSS about all workers and tables. The info will be created by data loader and updated by replicator which do not exist yet. For this issue we need to provide python API which can fill the same information in CSS so that we can build and test other pieces needed for this epic."
Answer: 70520.0

User story: "MySQL client 4.1 and higher is stripping out comments before sending them to server, so the fixes done in DM-1539 are not sufficient."
Answer: 48.0

User story: "This is a placeholder story, we should break it down into more smaller stories..."
Answer: 120980.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: "Integrate prototype developed through DM-1255 with cat and db as appropriate (don't hardcode schema, don't hardcode credentials, etc)."
Answer: 8552.0

User story: "Relevant links:  * http://www.ivoa.net/documents/SIA/20141024/index.html - there’s a list of metadata in the document  * CAOM (Common Archive Object Model): http://www.cadc-ccda.hia-iha.nrc-cnrc.gc.ca/caom2/"
Answer: 10132.0

User story: "The following tests in meas_algorithms need to be ported to the meas_base framework:  measure.py psfSelectTest.py testPsfDetermination.py ticket2019.py testCorrectFluxes.py (though this cannot be done until the algorithm exists)"
Answer: 15018.0

User story: "I should have thought about it when doing DM-1601 but I didn't... it'd be good to add test queries that test comments before/after/inside query."
Answer: 1346.0

User story: Connecting to qserv from java fails because the jdbc driver inserts comments. "/* ... */" in front of queries (example pasted below). The fix involves removing the comments at the proxy level   {code} SQLException: Qserv error: 'ParseException:ANTLR parse error:unexpected token: /:'  Query being executed when exception was thrown: /* mysql-connector-java-5.1.34 ( Revision: <EMAIL>-20141014163213-wqbwpf1ok2kvo1om ) */SHOW VARIABLES WHERE Variable_name ='language' OR Variable_name = 'net_write_timeout' OR Variable_name = 'interactive_timeout' OR Variable_name = 'wait_timeout' OR Variable_name = 'character_set_client' OR Variable_name = 'character_set_connection' OR Variable_name = 'character_set' OR Variable_name = 'character_set_server' OR Variable_name = 'tx_isolation' OR Variable_name = 'transaction_isolation' OR Variable_name = 'character_set_results' OR Variable_name = 'timezone' OR Variable_name = 'time_zone' OR Variable_name = 'system_time_zone' OR Variable_name = 'lower_case_table_names' OR Variable_name = 'max_allowed_packet' OR Variable_name = 'net_buffer_length' OR Variable_name = 'sql_mode' OR Variable_name = 'query_cache_type' OR Variable_name = 'query_cache_size' OR Variable_name = 'license' OR Variable_name = 'init_connect' {code}
Answer: 421.0

User story: "Produce a confluence page describing the approach to be taken to solve DM-1074. Ensure that all the relevant folks have reviewed that page and are happy. Break down DM-1074 into stories appropriate to that design."
Answer: 94945.0

User story: Following the landing of DM-1545, it's possible for an erosion operation on a footprint to cause it to split into multiple components and for peaks which were previously inside the footprint to not fall inside any of those components.  Here, we should provide a "clean up" operation that takes a multiple-component footprint and splits it into a set of contiguous footprints with appropriate peak lists.
Answer: 1130650.0

User story: "Write some prototype code with Angular and then try to do the same thing with React"
Answer: 37480.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "I will take the lead on DM-1074. First step will be to sit with [~<USER>, get a feeling for what needs to be done, and sketch out a set of stories."
Answer: 37243.0

User story: "Need to build a form that will be used to capture user input about existing image repositories (users will be registering their files/repositories). Options to consider: python-based django, java-based system that is part of Fermi DataCat. "
Answer: 62085.0

User story: "Implement crawler that walks through registered repos (through the form) and loads metadata from fits headers into the mysql backend"
Answer: 93689.0

User story: "Web alpha version of the form (using django or Fermi Java webservices code) that collects input from users about data repositories. Authentication not covered in this version."
Answer: 89427.0

User story: "We have a lot of files/images already brought in or generated through Data Challenges done to date. We need a system for cataloging them. This story will define such system, eg, sketch of UI, underlying technology used (DataCat, plain mysql, schema etc)."
Answer: 30922.0

User story: "Data Release Production will generate highly structured image metadata (exposure* tables). If we decide to use DataCat (e.g., for keeping more ad hoc metadata), the question arises if/how to integrate all this together: * should we integrate all exposure* tables from all releases into DataCat? (eg via foreign tables) * should we keep them distinct, and integrate at higher level (e.g., Metadata Service)"
Answer: 30932.0

User story: "This should be further refined.  The solver will be required to work with several input formats.  It will only be required to solve in the in the presence of a reasonable starting point with reasonable pointing errors.  Failure should be graceful.  If multiple, equivalent solutions are found, this should be reported (for situations including perfect grids of sources)."
Answer: 133524.0

User story: "Astrometry.net index files are hard to generate and hard to read.  We need another, more flexible, more standard system for storing reference files.  We should also be able to read FITS files and other formats, but having a standard format with the utilities to create and query them is a must.  Coming up with a format that satisfies astrometry.net's solver may be too hard, because a.net requires quads, which a non-blind solver may not need. However, a format that we can convert to something suitable for a.net would probably suffice (conversion would presumably be a separate task that is run once).  It will be easier to identify a suitable format once we have identified at least one solver other than than a.net that we wish to implement or adapt. hscAstrom appears to use a catalog of star positions, which is nice and simple."
Answer: 708499.0

User story: "It is confusing that photocal is in meas_astrom.  I assume that is historical.  I think it could probably live in pipe_tasks."
Answer: 262014.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 AstrometryTask and Astrometry class share work.  E.g. distortion is done in AstrometryTask but matching is done in Astrometry.  AstrometryTask also makes assumptions about what fields are available in the solver config.    The AstrometryTask interface should be sanitized so that it can be used as a thin wrapper for calling any astrometry solver.  Top level config params should go in the AstrometryTaskConfig and solver level work should be done in the solver class and configured at the solver level."
Answer: 153478.0

User story: "Get the pipeline running on HSC data to the point where nothing is obviously wrong."
Answer: 139226.0

User story: "Setup Qserv on lsst-db2 with and load some reasonable data set (perhaps PT 1.2). One potential caveat: we need to setup access for some accounts that are ideally other than our internal qsmaster."
Answer: 105563.0

User story: "Integration tests should provide a new test case which use sph-duplicate in partition package."
Answer: 135882.0

User story: "We are starting to gel around some ideas. "
Answer: 64862.0

User story: "Begin looking into JS frameworks. Start to look into AngularJS, try to write some sample code.  Attempt to understand the main concepts. Gat an overview of the others out there.  "
Answer: 11697.0

User story: "Some of the grid lines are not drawn right and the labels are not in the locations."
Answer: 20041.0

User story: "If a command-line task is run with doRaise false and doReturnResults true, and the task fails, a traceback results due to an uninitialized error.  The fix is trivial, though it requires coming up with a suitable value for the result field of the returned Struct. I propose to use None, but an empty Struct would also be a good choice."
Answer: 51.0

User story: "SDSS allows two ways to access their catalog data: via HTTP Post service, accessible to anonymous users, and via CasJobs services, which require having an account. Evaluate how SDSS catalog data can be accessed from an application by prototyping single and multiple target searches accessing SDSS services. "
Answer: 4.0

User story: "To start the development I should be able to connect to the QSERV development database via VPN and run simple queries.   Ideally, I'd like to be able to connect to QSERV with JDBC, view the data, run spatial queries. I also need an access to data dictionary to interpret data."
Answer: 31516.0

User story: "Currently we are using a generic 2-d binning algorithm, that is finding minimum and maximum values of the two columns to be visualized and bins the values into 2-d grid with the specified number of grid cells.  This algorithm distorts data in the pole regions and whenever data are on both sides of ra=0. More smart binning based on a spatial index is necessary when reducing the number of (ra,dec) entries intended for visualization.  "
Answer: 142614.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 default home page of JIRA shows tickets assigned to me, which is great, but not tickets I'm reviewing. There's a link for that, but I often forget to follow it.  If it's hard to show the tickets themselves, then a decent fall-back would be to show a count of *count* of the tickets I'm reviewing. If it's > 0 I'd know to click on the link.  Basically by default I think the home page should show users the tasks they are responsible for."
Answer: 2743462.0

User story: in obs_test, at least, the data product "calexpBackground" does not seem to survive the round trip of using the butler to persist and unpersist it.  I wrote this bit of obs_test to match obs_lsstSim, so I suspect the same issue exists there.  To see the problem, uncomment these lines in pipe_tasks test/testProcessCcd.py on tickets/DM-1293 (unless that has been merged to master). Then run the test using a recent master of obs_test. {code}             # calexpBackground = butler.get("calexpBackground", dataId)             # self.assertGreaterEqual(len(calexpBackground), 1)             # bg0Arr = calexpBackground[0][0].getImageF().getArray() {code} The call getImageF() will fail with a traceback that includes the explanation "nxSample and nySample have too few points for requested interpolation style". 
Answer: 180022.0

User story: "partition, Qserv, qserv_testdata and possibly scisql doesn't relies on the same eups build procedure, i.e. commands {{setup -r .; scons; scons install}} have not exactly the same behaviour. This could be solved or at least, documented."
Answer: 2399093.0

User story: "Analogous to DM-1128, but shrinking rather than growing footprints."
Answer: 16905.0

User story: "The code that pulls data out of a {{MYSQL_ROW}} and puts it into a protobuf {{RowBundle}} does not handle binary data correctly. See [_fillRows|https://github.com/LSST/qserv/blob/master/core/modules/wdb/QueryAction.cc#L217] for the relevant code.  The issue is that the generated {{add_column(const char*)}} member function of {{RowBundle}} treats the input as C-style NULL-terminated strings. But in the case of {{BINARY}} column data (and {{VARBINARY}}/{{BLOB}} variants, maybe also {{BIT\(n\)}}), the contents can contain embedded NULLs. We are currently using such columns for user defined types in MySQL (e.g. image bounding polygons), so it's important to get this right. On the protobuf side the fix is as simple as calling {{add_column(const char* value, int size)}} instead. I'm not a MySQL C API expert, but the size will presumably have to be obtained/derived from the corresponding {{MYSQL_FIELD}}.  "
Answer: 240283.0

User story: The mysql/SchemFactory code has incomplete logic for dealing with columns that have BIT type - in particular, it doesn't properly handle the length of a bit field, and it sets the SQL type to "BIT?", which causes table creation failures later on. Fixing this requires modifying SchemaFactory, and making sure that bit values are  transmitted properly.
Answer: 271442.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: "SUI which rely on JDBC fail because they internally issue some queries that are not yet supported by Qserv. Need to patch it (in the short term), and add proper support (in the long term). This story covers the patching only. The queries that upset Qserv are listed below.   {code} SHOW VARIABLES WHERE Variable_name ='language' OR Variable_name = 'net_write_timeout' OR Variable_name = 'interactive_timeout' OR Variable_name = 'wait_timeout' OR Variable_name = 'character_set_client' OR Variable_name = 'character_set_connection' OR Variable_name = 'character_set' OR Variable_name = 'character_set_server' OR Variable_name = 'tx_isolation' OR Variable_name = 'transaction_isolation' OR Variable_name = 'character_set_results' OR Variable_name = 'timezone' OR Variable_name = 'time_zone' OR Variable_name = 'system_time_zone' OR Variable_name = 'lower_case_table_names' OR Variable_name = 'max_allowed_packet' OR Variable_name = 'net_buffer_length' OR Variable_name = 'sql_mode' OR Variable_name = 'query_cache_type' OR Variable_name = 'query_cache_size' OR Variable_name = 'license' OR Variable_name = 'init_connect'  SELECT @@session.auto_increment_increment  SET NAMES latin1  SET character_set_results = NULL  SET autocommit=1  SET sql_mode='STRICT_TRANS_TABLES' {code}"
Answer: 64.0

User story: "Can we use IPMI in place of a KVM?  Can we reliably do the following across our various server vendors?  - power cycle hung systems  - view and use text console  - view and use remote gui console  - boot from a remote ISO"
Answer: 112319.0

User story: A heterogeneous collection of docker images have been accumulating within the public docker repository  daues/lsstdistrib . Such a heterogeneous collection prevents the assignment of a "latest" tag to allow users to easily obtain the most recent image for a particular item (detailed version numbers, labels currently required.)     Thus we should break out the single repository into multiple repositories where are "latest" tag will be effective.  We also make  github repositories of matching names to hold the Dockerfiles which produced images (a common pattern for github/dockerhub usage, especially with automated builds; so we start this practice.) 
Answer: 3137.0

User story: "Identify potential KVM hardware that would meet our needs.  e.g. a current version of the Avocent or Dell KVMs used at NCSA."
Answer: 112337.0

User story: "The Cyber security center has provided a risk template consistent with their templates,  The Center attempted to populate their templates with material from LSE 99  to the templates,   The impedance mis match was too large, The way forward is seem as  attempting a high level decomposition of risk into the templates."
Answer: 100705.0

User story: "processFile.py uses the old measurement framework in meas_algorithms, but all the other components expect it to be using the new measurement framework in meas_base."
Answer: 94651.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: "Get familiar with FIrefly package, build and run an application.  Understand the coordinate grid overlay on an image. "
Answer: 1.0

User story: The SUI team is using JDBC connector and queries like  "SET @@session.autocommit = {0}".format(switch)  are derailing everything. We should add support for these queries. 
Answer: 125.0

User story: "Qserv build system use system swig, it should be fixed to use eups swig. "
Answer: 2278458.0

User story: "On Ubuntu 12.04, gcc --version says: {code:hide-linenum} gcc (Ubuntu/Linaro 4.6.3-1ubuntu5) 4.6.3 Copyright (C) 2011 Free Software Foundation, Inc. This is free software; see the source for copying conditions.  There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. {code}  This apparently isn't quite what sconsUtils expected, because it says: {code:hide-linenum} scons: Reading SConscript files ... Checking who built the CC compiler...(cached) error: no result CC is unknown version unknown {code}  Happily, everything seems to work anyway, as the fall-back options for the unknown compiler work fine with this one."
Answer: 39265.0

User story: "Calling {{catalog.extend(other, mapper)}} isn't equivalent to {{catalog.extend(other, mapper=mapper)}} because the second argument is the boolean {{deep}}.  When a SchemaMapper is passed as the second argument, we should recognize it for what it is."
Answer: 69119.0