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: The following (running on lsst-qserv-dax01)     {code}  dataRoot="/datasets/<USER>data/DC_2013/calexps/"  butlerPolicy="calexp"  ids = id {'filter': u'g', 'field': 694, 'camcol': 4, 'run': 5646}    def getImageByIds(self, ids):      butler = lsst.daf.persistence.Butler(dataRoot)      img = butler.get(butlerPolicy, dataId=ids)      return img, butler  {code}    Results in this error   {code}    File "/lsst/stack/dax_imgserv/python/lsst/dax/imgserv/locateImage.py", line 286, in getImageByIds      img = butler.get(self._butlerPolicy, dataId=ids)    File "/lsst/stack/Linux64/daf_persistence/12.1/python/lsst/daf/persistence/butler.py", line 586, in get      location = repoData.repo.map(datasetType, dataId)    File "/lsst/stack/Linux64/daf_persistence/12.1/python/lsst/daf/persistence/repository.py", line 180, in map      loc = self._mapper.map(*args, **kwargs)    File "/lsst/stack/Linux64/daf_persistence/12.1/python/lsst/daf/persistence/mapper.py", line 173, in map      return func(self.validate(dataId), write)    File "/lsst/stack/Linux64/daf_butlerUtils/12.1+1/python/lsst/daf/butlerUtils/cameraMapper.py", line 294, in mapClosure      return mapping.map(mapper, dataId, write)    File "/lsst/stack/Linux64/daf_butlerUtils/12.1+1/python/lsst/daf/butlerUtils/mapping.py", line 142, in map      return ButlerLocation(self.python, self.persistable, self.storage, path, additionalData, mapper)    File "/lsst/stack/Linux64/daf_persistence/12.1/python/lsst/daf/persistence/butlerLocation.py", line 62, in __init__      self.additionalData.set(k, v)    File "/lsst/stack/Linux64/daf_base/12.1/python/lsst/daf/base/baseLib.py", line 4136, in _PS_setValue      return _propertyContainerSet(self, name, value, _PS_typeMenu)    File "/lsst/stack/Linux64/daf_base/12.1/python/lsst/daf/base/baseLib.py", line 4098, in _propertyContainerSet      raise lsst.pex.exceptions.TypeError("Unknown value type for %s: %s" % (name, t))  TypeError: Unknown value type for filter: <type 'unicode'>  {code}
Answer: 11120.0

User story: "to gather requirement and dependencies on other DM teams for Alert subscription system developed by SUIT.    After much discussion with AP team and the re-plan exercise, the requirement for alert subscription has been identified as the following:  *use the API that AP team will provide to*    # provide a UI for user to specify the filters on alerts of their interests, the destination of the alert to be sent  # save the specification in a DB  # provide UI to allow users to make modification of the filters and destinations of alerts  # possibly to annotate the alerts and allow user to access the annotation    This will involve SLAC for DB, NCSA for user management  "
Answer: 29094.0

User story: "- Add image tables, Science_Ccd_Exposure and DeepCoadd, into the item search list.   - show DD table if any of the image table is selected for LSSTMetaSearch.  - show the image metadata table for LSSTCatalogSearch.  "
Answer: 1972.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "As part of DM-7293, we added getBytes/setBytes to the SWIG interface for afw:table:BaseRecord, but it doesn't have tests. There are similar SWIG methods for strings that also don't have tests. We should add some tests for those at the python layer, to make the pybind11 conversion easier to manage."
Answer: 2033426.0

User story: "Calexp and coadd image directory trees from NCSA and IN2P3 sides of the strip82 processing need to be merged, so imgserv can serve images for the entirety of stripe82.  We anticipate doing this with some scripts to build the merged directory trees as link farms.    The datasets will be put into this folders:  {code}  /datasets/sdss/preprocessed/dr7/sdss_stripe82_00  /datasets/sdss/preprocessed/dr7/sdss_stripe82_00/calexp  /datasets/sdss/preprocessed/dr7/sdss_stripe82_00/coadd  {code}  The name of the bade folder matches the name of the corresponding catalog within the PDAQ Qserv.  "
Answer: 1696.0

User story: Currently, all catalog data for the NCSA/IN2P3 overlap region of the Stripe 82 processing in the PDAC has been taken from the NCSA side of the processing.  However, the NCSA side of the processing does not include data for all patches on its "outer" boundary of the overlap region (and same is true for IN2P3 processing with respect to the the opposite overlap boundary).    The catalog merge will need to be redone, with patch division moved away from either of the overlap region boundaries in order to avoid "holes".    Based on a layout of *patches* (see a PDF document attached by this tickets) the new boundary should be laid between *375* and *376*. 
Answer: 279172.0

User story: "The instructions for running the lsst_dm_stack_demo and checking the astrometric relative RMS with {{bin/check_astrometry output}} won't work for OS X El Capitan+ because of SIP.  I think there is a known fix for this, if the issue is similar to [https://jira.lsstcorp.org/browse/DM-4921]."
Answer: 8228.0

User story: "per  https://community.lsst.org/t/bug-in-daf-persistence-blob-master-python-lsst-daf-persistence-utils-py/1389/2  allow dicts to count as a 'sequence' in sequencify."
Answer: 63.0

User story: "It is desirable to retrieve images by their identifiers for calexps, deepCoadd, and raw images."
Answer: 103577.0

User story: "The photometry task needs its own refObjLoader.  This means it will also need a loadAndMatch method.    This will require that calibrate.py will need to be updated to pass the refObjLoader."
Answer: 1192.0

User story: "Let the config name be set by the indexed reference ingester so that multiple ingested reference datasets can reside in the same repository."
Answer: 79577.0

User story: "A new package, {{sims_survey_fields}}, will be added to the _repos.yaml_ in {{lsstsw}}."
Answer: 1619.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 flask internal web server is single-threaded, which will cause web services to be blocked e.g. during long running queries.  We will need to place some sort of multithreaded/pooling web server (e.g. nginx + wsgi) ahead of the flask service for acceptable behavior until implementing/adopting disconnected queries. "
Answer: 22361.0

User story: "I'm messing with SuperTask and it would be nice to have few unit tests there to avoid regression."
Answer: 18350.0

User story: "write a test that shows that butler can find mapper from _parent directories when using v1 butler functionality"
Answer: 19760.0

User story: "Improve the original fix proposed by [DM-8119] to make it fully compatible with the Debian Linux distribution used to build Qserv containers. It requires to have the following two files to be properly initialized:  {code}  /etc/localtime  /etc/timezone  {code}  *NOTE*: the second file doesn't exists in the RedHat-based Linux distributions.    Some ideas on how to solve this problem for Docker container can be found in the following documents:  * [https://www.ivankrizsan.se/2015/10/31/time-in-docker-containers/]  * [https://debian-administration.org/article/213/Changing_the_timezone_of_your_Debian_system]"
Answer: 1661.0

User story: The decam linearizer files we have commited to obs_decam are pickles files produced with python2, and required a fix to daf_persistence to specify an encoding:    {code}  if sys.version_info.major >= 3:      finalItem = pickle.load(infile, encoding="latin1")  else:      finalItem = pickle.load(infile)  {code}    I believe that we can fix this by just re-running makeLinearizer.py on python 3, to get the encoding explicitly specified, but I'm not certain.    Once done, we should probably remove that encoding specification from daf_persistence. It would also be a chance to fix the file naming in DM-8219.
Answer: 1353297.0

User story: "This ticket will handle the first part of DM-8180, which will result in correct histogram display for the long values that can be converted into doubles without loosing precision.  (ex. LSST htm index)"
Answer: 8984.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, if an error happens on the server, it is logged on a console, but the display of the chart keeps showing the spinning wheel. We need to show in UI that the chart has failed."
Answer: 30556.0

User story: "{{lsst.afw.image.readMetadata}} returns a {{PropertySet}}, which doesn't track the order of header keywords.  {{PropertyList}} is the proper type for FITS headers, so {{readMetadata}} should return that instead."
Answer: 8655.0

User story: The {{butler.get(dataset + "_md", dataId)}} pattern is only supported for images, not catalogs.  It would be useful to allow this to work on catalogs.  At the same time, it would be useful to add support for getting the length and schema of a catalog.
Answer: 8912.0

User story: "It would be helpful to be able to read a catalog schema without reading the entire catalog (e.g., to prepare for concatenating catalogs).  I propose adding {{static}} methods:    {code}  Schema::readFits(std::string const& filename);  Schema::fromFitsMetadata(daf::base::PropertySet & header);  {code}"
Answer: 1623.0

User story: "{{obs_cfht}} wraps its config options for astrometry in a try block that falls back to a different set of configurations on failure, assuming that failure is due to the astrometry task having been retargeted to {{ANetAstrometryTask}}.  Unfortunately, this doesn't actually work, because this block will have already been run by the time the user has an opportunity to retarget the astrometry task.  And we've encountered at least one occasion where the catch triggers due to a different exception, which is then masked."
Answer: 103915.0

User story: - Do more validation on the  server.  - Pass detailed server error to the client.    jbpagliuco November 7    We have a request to make the getJSONFromTask function more helpful on failure. Right now, if something went wrong while trying to execute a task script, we get the error message "edu.caltech.ipac.firefly.server.query.DataAccessException: Unable to data from external task: Failed to obtain data. null", which isn't very helpful in tracking down the problem. It would be really great if we could get a better message telling us the problem. For instance, firefly couldn't find the dispatcher file, or if there was a syntax error somewhere tell us which file and line. It would make debugging these problems infinitely easier
Answer: 19018.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 think there are flaws in how showImages are set in FireflyViewerManager layoutManager saga. In the first catalog load, coverage is not shown if active table is set before the table is loaded.    At dispatchUpdateLayoutInfo time     When active table is set before table is loaded:                        tableResults.added     showImages=false  tableResults.active     showImages=false  table.loaded                showImages=true  charts.data/chartAdd  showImages=false    When active table is set after table is loaded:    tableResults.added     showImages=false  table.loaded                showImages=true  charts.data/chartAdd  showImages=false  tableResults.active     showImages=true    You can test it by changing line 340 in TablesCntlr.js:      dispatchActiveTableChanged(tbl_id, options.tbl_group);    instead of       dispatchAddSaga(doOnTblLoaded, {tbl_id, callback:() => dispatchActiveTableChanged(tbl_id, options.tbl_group)});"
Answer: 133342.0

User story: "This story tracks a means for snapshotting the Redis DB instances running in the system in a manner that is easier to use than the built in method Redis offers. It writes a file in a rather complex format that must be parsed and filename collisions of the save file are a problem.    Because all entities in the Level 1 transport system are already using a messaging service, it has been decided to use this service rather than deal with the need to transfer the snapshot file and then parse it. The list of primary keys is iterated through and Redis 'hgetall' is called resulting in a python dictionary of the key's contents.This dictionary is placed beneath a key to ALL primary key hash structures, and then YAML dumped into a message and set to the message queue which the InfluxDB front end is listening to. After loading the YAML'd data back into a dictionary, code has been built to translate the code into the format needed for insertion into an Influx timeslice.    This approach has the advantage in that it is easy to incorporate non-Redis events that need to be persisted by sending a report to the queue."
Answer: 1.0

User story: "Current SuperTask interface consist of many placeholder methods that may not be really needed. Review all of that and try to simplify it so that only necessary things are there."
Answer: 15951.0

User story: "The plan of DM-7844 & DM-7860 was circulated to stakeholders ([~<USER>, [~<USER>, [~<USER>, [~<USER>, [~<USER>) on 2016-11-03. Wait for feedback, then revise the plan appropriately."
Answer: 72200.0

User story: "Based on the plans in DM-7846 and DM-7860, develop a new set of planning packages for DRP and CPP in Excel sheet form."
Answer: 3353.0

User story: "35 TB dataset has been loaded in Galactica/openstack cluster by Vincent Gatignol. This ticket will allow to use it with provisioning script."
Answer: 95570.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: "DM-7005 implements a data table connected with the metrics plot that list the jobs, measurement values and packages that changed with respect to the previous job linked to the corresponding git urls.    The implementation can be tested here:  https://angelo-squash-squash.lsst.codes/    it was merged to master and can be shipped to production.        "
Answer: 17240.0

User story: "Work begun under DM-7807."
Answer: 259137.0

User story: "To speed up development, DM-7888 was restricted to creating a list of {{Point2D}}. Since a list of other {{Point}} specializations would be nearly identical, they are best implemented by converting {{Point2DList}} into a template class.    The conversion must be done in a way that does not break existing code depending on {{Point2DList}}."
Answer: 157041.0

User story: "Cinder blocks from Openstack are not yet fully supported by Kubernetes, a work around in Nebula is to mount a cinder block and create a NFS server for the cluster"
Answer: 4.0

User story: "At the moment, when an error occurs, the panel does not update leaving the loading masks visible indefinitely.  This panel should instead update itself with error message(s) from the fetch.    TODO:  - Fix CatalogConstraintsPanel  - add generic error display into BasicTableView  - move createErrorTbl from TablesCntlr to TableUtil"
Answer: 6086.0

User story: "Create an initial model of the Data Backbone enclave"
Answer: 39219.0

User story: "Exercise the service model using representative use cases "
Answer: 39250.0

User story: "Define architecture/schema for Service Level Targets in Enterprise Architect"
Answer: 39248.0

User story: "Extract Data Management requirements from Enterprise Architect and catalog as the basis for Service Level Targets (SLT)"
Answer: 49.0

User story: "Identify & populate the EA model for known services"
Answer: 52.0

User story: "A new email notification should be sent for every successfully completed background jobs when a new email is entered."
Answer: 25875.0

User story: "When a user selects Get Download Script, the user should be prompted with a dialog of options.  Attached images show what it used to look like.    "
Answer: 51410.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: Server side now handles the expressions and passes 14 significant digits, which the client can handle.    This ticket addresses the following issues:  - Flexible histogram tooltip precision based on the bin width. You should not see bin ranges like "0.000000 to 0.000000" for when the boundaries are small numbers.  - Histogram and heatmap now handle quoted column names and expressions. (Can be tested with NED.)   - Histogram options will show range for quoted and unquoted columns.  - Expressions for all charts are now handled by database. (There will be a separate ticket for cleanup.)      Original description (Nov.16):    Histogram display is incorrect for large long values. There are several aspects contributing to this issue:    1. The data from the server should be passed at the full precision the client can handle.    To solve this issue, we can either set the format string or avoid formatting table data when passing them in JSON (which would be a separate ticket).    2. For large long numbers we are loosing precision twice:    First, when converting log to double on server side:      new Long(69327485392650247l)).doubleValue()      result: 6.9327485392650248E16    Second, in Javascript:       parseFloat("6.9327485392650248E16")      result: 69327485392650250    To solve these issues, the server side code constructing bins should be using the same precision the client side can handle.      
Answer: 761520.0

User story: "Currently, background jobs and statuses are kept on the client.  That information is lost after a browser reload.  We need to save that information so that a user can come back at a later time and still get this information presented.    Implementation:  - save data on the server.  - push all statuses to client when connected  - continue to update statuses while client is connected"
Answer: 20157.0

User story: In the DPDD DIASource schema, there is a field {{totFlux}}, which is described as "Calibrated flux for point source model measured on the visit image centered at the centroid measured on the difference image (forced photometry flux)". This is not currently measured by {{imageDifference.py}}, and it would be very useful for  categorizing DIA source detections.
Answer: 986550.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: After looking at the code, sims requires sqlalchemy 1.0 but 1.1 has been released and was being installed.    {code}  ======================================================================  ERROR: setUpClass (__main__.CompoundCatalogTest)  ----------------------------------------------------------------------  Traceback (most recent call last):    File "tests/testCompoundInstanceCatalog.py", line 228, in setUpClass      idColKey='id')    File "/opt/conda-lsst/miniconda/conda-bld/work/python/lsst/sims/catalogs/db/dbConnection.py", line 782, in __init__      indexCols=self.indexCols, **kwargs)    File "/opt/conda-lsst/miniconda/conda-bld/work/python/lsst/sims/catalogs/db/utils.py", line 125, in loadData      dataTable = createSQLTable(dtype, tableId, idCol, metaData)    File "/opt/conda-lsst/miniconda/conda-bld/work/python/lsst/sims/catalogs/db/utils.py", line 55, in createSQLTable      sqlType = satypes._type_map[nativeTypes[name]]  AttributeError: 'module' object has no attribute '_type_map'    ----------------------------------------------------------------------  Ran 2 tests in 0.068s    FAILED (errors=1)  tests/testCatalogDBObject.py  {code}    See the complete _build.log here:    https://gist.github.com/<USER>9769504866aa08f0771f3a0410e661f0
Answer: 96458.0

User story: "In order to be able to psf-match a WarpedPSF or a CoaddPsf, ModelPsfMatch needs to know the dimensions of the WarpedPsf. Currently the only way to get this is to compute the kernel image first.  There are cheaper ways to compute the dimensions, starting by asking the undistorted PSFs (either PsfexPsf or PcaPsf) for its dimensions. Simplest solution is to give all PSFs a getDimensions method. "
Answer: 60621.0

User story: In going through at least the level 1 catalogs, I think there might be some errors or inconsistencies in the tables in the DPDD that are causing some confusion and can be clarified.    * In DIAObject table, the description for {{fpFluxMeanErr}} is "Standard error of fpFlux" whereas {{psFluxMeanErr}} is "Standard error of psFluxMean".  Is it standard error of *Flux or *FluxMean?  * In SSObject table, for {{oeCov}} should the covariance matrix length 28 and not 21?  * In DIASource table, should {{parentSourceId}} really be {{parentDiaSourceId}} and the description should refer to deblending from another diaSource, not {{Source}}?   * In DIASource table, should the {{dipCov}} covariance matrix length be 21 instead of 15?
Answer: 70157.0

User story: "A Firefly browser tab allows downloading a PNG of the current image. For work inside a Jupyter notebook with afwDisplay, it would be very useful to download such a static screenshot and save it with the notebook."
Answer: 483702.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: {{afw.display.setDefaultBackend("firefly")}} will attempt to connect to a Firefly server running on localhost:8080. If no connection is possible, the command fails. For cases when a remote server or alternate port are desired, {{setDefaultBackend}} will be modified to accept optional arguments.    Meanwhile, the workaround is to use {{afwDisplay.Display(frame=n, host=xxx, port=yyyy)}} to connect to a remote Firefly server.
Answer: 136887.0

User story: "See RFC-246 for the reasoning and for an example implementation."
Answer: 142439.0

User story: "Respond to enquiry from Emily Petroff re the role of IVORNs in VOEvents. Ensure documentation at http://voevent.readthedocs.io/en/latest/reading.html#ivorns-and-identifiers is accurate and reflects this response."
Answer: 30.0

User story: "continue to refine the work packages"
Answer: 170424.0

User story: "After discussion with Mario in September 2016, it is tentatively decided that the workspace will be achieved by using JupyterHub and Jupyter NB. This story is to capture that thought."
Answer: 171679.0

User story: "Currently the catalog of reference objects in the matcher is not loaded on a area relative to the max shift/rotation allowed. For larger shifts/rotations/distortions this could lead to portions of the chip being outside of the loaded reference catalog area and thus unconstrained in future wcs fitting.    Deliverables: Fix to meas_astrom so that it loads an area of the reference catalog relative to the max shift/rotation."
Answer: 211793.0

User story: "Before migration, IRSAViewer could be called directly via URL in the browser to display images from FITS for example.   A typical URL currently used OPS by NED is for example:    http://irsa.ipac.caltech.edu/irsaviewer/app.html#id=FFToolsImageCmd&DoPlot=true&RequestClass=WebPlotRequest&File=http%3A%2F%2Fned.ipac.caltech.edu%2Fimg%2F1988MNRAS.230..345N%2FARP_220%3AI%3A6cm%3An1988.fits.gz  &URL=http%3A%2F%2Fned.ipac.caltech.edu%2Fimg%2F1988MNRAS.230..345N%2FARP_220%3AI%3A6cm%3An1988.fits.gz  &RangeValues=92%2C-2%2C92%2C8%2C1%2C0%2C1%2C2%2C44%2C25%2C600%2C120&PostTitle=ARP%20220&TitleFilenameModePfx=cutout&ColorTable=1&TitleOptions=FILE_NAME&Type=TRY_FILE_THEN_URL&    Please, make IRSAViewer be called from the browser with same URL parameters to display images directly entering the URL in the browser. "
Answer: 12519.0

User story: "Apparently few telescopes provide UT1 in their headers. We can compute it from TAI with astropy using a downloaded database. If we want to get ERA correctly, we'll need UT1.    Note that once we get UT1 in VisitInfo, DM-8053 will be almost trivial."
Answer: 1355573.0

User story: "Encoding messages to Avro using the avro-python3 module is slow enough that message consumers can read much faster than the encoded messages can be generated.  Look at swapping out the avro-python3 module with fastavro."
Answer: 60254.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: This is the working extension for DM-8010.  The DM-8010 implemented MetaData and TableData search processors.  The image search processor is needed as well.  It will also exercise the cutout service that SLAC imgServ API will provide.    The image search processor (LSSTImageSearch) is searching the DAX using either id or a set of ids to locate the image and then displaying them in the tree-view window.  There are two types of search URL:    Coadded image (and cutout) retrieval   curl -o outImageCoadd.fits "http://lsst-qserv-dax01.ncsa.illinois.edu:5000/image/v0/deepCoadd/id?id=23986176"      For Science CCD, it can also be searched using id.   But the preferred way is using a set of ids, such as:    curl -o outImage3.fits "http://lsst-qserv-dax01.ncsa.illinois.edu:5000/image/v0/calexp/ids?run=3325&camcol=1&field=171&filter=z"    The image search processor processes the parameters passed from the UI and then build the URL like above to find the image.              
Answer: 60879.0

User story: "Add support for allocation of HTCondor nodes through Slurm via allocateNodes.py command.  This is related to work being done for DM-8154"
Answer: 63319.0

User story: "This captures the logging plugin changes from upstream xrootd xrdssi branch. Passed jenkins."
Answer: 2849.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: h1. The problem    The data loader script *qserv-data-loader.py* fails to load large tables into *Qserv*. This was observed when loading a large 14 GB table 'Science_Ccd_Exposure_Metadata' into 'qserv-master01' from 'qserv-db01' using:  {code:bash}  % qserv-data-loader.py \  --verbose --verbose --verbose --verbose-all \  --host=lsst-qserv-master01 --port=5012 \  --secret=/home/<USER>production/stripe82/wmgr.secret \  --no-css --worker=lsst-qserv-master01 \  --config=/datasets/<USER>production/stripe82_catalog_load/production_load/common-non-part.cfg \  sdss_stripe82_00 Science_Ccd_Exposure_Metadata \  /datasets/<USER>catalogs/<USER>SDRP_Stripe82/Science_Ccd_Exposure_Metadata.sql \ /datasets/<USER>catalogs/<USER>SDRP_Stripe82/Science_Ccd_Exposure_Metadata.tsv \  >& logs/Science_Ccd_Exposure_Metadata.log  {code}    The relevant message at a log file of the *wmgr* service used by the loader has:  {code}  % sudo tail -200 /qserv/log/qserv-wmgr.log  ...  2016-10-30 14:28:19,831 [PID:442] [ERROR] (log_exception() at app.py:1423) wmgr: Exception on /dbs/sdss_stripe82_00/tables/Science_Ccd_Exposure_Metadata/data [POST]  Traceback (most recent call last):    File "/qserv/stack/Linux64/flask/0.10.1.lsst2+1/lib/python/Flask-0.10.1-py2.7.egg/flask/app.py", line 1817, in wsgi_app      response = self.full_dispatch_request()  ...    File "/qserv/stack/Linux64/flask/0.10.1.lsst2+1/lib/python/Werkzeug-0.11.10-py2.7.egg/werkzeug/formparser.py", line 521, in <genexpr>      form = (p[1] for p in formstream if p[0] == 'form')    File "/qserv/stack/Linux64/flask/0.10.1.lsst2+1/lib/python/Werkzeug-0.11.10-py2.7.egg/werkzeug/formparser.py", line 497, in parse_parts      _write(ell)  IOError: [Errno 28] No space left on device  2016-10-30 14:28:20,833 [PID:442] [INFO] (_log() at _internal.py:87) werkzeug: 141.142.181.132 - - [30/Oct/2016 14:28:20] "POST /dbs/sdss_stripe82_00/tables/Science_Ccd_Exposure_Metadata/data HTTP/1.1" 500 -  {code}    The current implementation of the *wmgr* services creates temporary files at the following folder:  {code}   /qserv/run/tmp  {code}    h1. Proposed solutions    Extend the container deployment configuration to allow mapping /qserv/run/tmp inside container to some larger file system outside the container. Consider these options:  * /qserv/tmp  ** this folder can be created on a large file system which is available in the present QServ deployments in *IN2P3* and *NCSA-PDAC*  * /tmp  ** this folder may not work in all deployments due to its relatively small size (depends on a configuration of the hosts)  
Answer: 22028.0

User story: "We would like a binary release of the latest sims version, which is b2323 on the eups build database on lsst-dev."
Answer: 100731.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: dax_imgserv experiences an error while loading lsst-qserv-dax01:/datasets/<USER>data/DC_2013/coadd/deepCoadd/r/0/321,4.fits.   This same file should be available as:   lsst-dev01.ncsa.illinois.edu:/datasets/<USER>data/DC_2013/coadd/deepCoadd/r/0/321,4.fits.  The error is:  {code}    MalformedArchiveError:     File "src/CoaddPsf.cc", line 358, in virtual std::shared_ptr<lsst::afw::table::io::Persistable> lsst::meas::algorithms::CoaddPsf::Factory::read(const InputArchive&, const CatalogVector&) const      Archive assertion failed: catalogs.size() == 2u {0}    File "src/table/io/InputArchive.cc", line 105, in std::shared_ptr<lsst::afw::table::io::Persistable> lsst::afw::table::io::InputArchive::Impl::get(int, const lsst::afw::table::io::InputArchive&)  {code}    On lsst-qserv-dax01.ncsa.illinois.edu this can be reproduced by  {code}  $ source /software/lsstsw/stack/loadLSST.bash  $ setup meas_algorithms  python  >>> import lsst.afw.image  >>> e = lsst.afw.image.ExposureF("/datasets/<USER>data/DC_2013/coadd/deepCoadd/r/0/321,4/coadd-r-0-321,4.fits")  {code}
Answer: 4037.0

User story: "Implement the ZOGY algorithm in stamps across an image and re-stitch the results back into a final diffim and S_corr. This will be the final necessary step which will enable future (a) implementing it in the stack itself and (b) testing on actual images in a realistic way."
Answer: 273899.0

User story: "DM has long assumed that all work is delivered in Project GitHub organizations, but this was never clearly stated in the Developer Guide. This ticket explicitly documents DM GitHub orgs."
Answer: 3009.0

User story: "To inform planning for processing runs of HSC public data, we need to estimate the following:    - The likely size of the raw data which will be released;  - The likely size of the processed image data and other ancillary products which will be stored to disk;  - The number of rows of catalogue data which will be persisted (either as afw::table cataloges or database tables);  - The number of core hours required to process the data; and  - The minimum RAM per core required.  "
Answer: 5591.0

User story: "DPDD includes a URL to http://ls.st/l9u which end up going to a TRAC page talking about the Winter 2013 LSST DM Data Challenge Release Notes.    Given the current status of TRAC I don't think LSE documents should point to those URLs. Can we please consider moving this content somewhere else. I'm not entirely sure whether it should be a DM tech note or a confluence page (I'd say an LDM but it's not clear people like nicely formatted PDFs entering an archive)."
Answer: 116694.0

User story: "Reading section 4.3.2 of DPDD and comparing it with DMS-REQ-0271, we have an inconsistency regarding the number of possible objects that are associated. DPDD states that the nearest 3 will be stored, whereas DMSR states that all the objects within TBD arcsec will be associated. Please clarify."
Answer: 144175.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: "Move several common datasets to obs_base.  This will not affect the dataset definitions of the individual cameraMappers."
Answer: 21906.0

User story: "Create patches for DM-8029, DM-8035 MariaDB and MariaDBClient, remove DM-7980, DM-7774 which are specific to the Conda packaged GCC 4.8.5. Patch python future for galsim. Patch git-rev version from MariaDB/MariaDBClient 10.1.11 to 10.1.18.    Built using Continuum's base Docker image. Which uses CentOS5 and GCC 5.2.0."
Answer: 15309.0

User story: "See: https://github.com/conda-forge/docker-images    I reproduced DM-8035 using CentOS6 and Conda Forge's Docker image which uses devtoolset-2. I also reproduced DM-7980, DM-7774 using Conda GCC version 4.8.5 package. There are a few interesting changes such as gosu and tini.    This is definitely a viable option but it did not resolve the current problems I was having with creating v12.1 using conda-lsst. I chose to use ContinuumIO's CentOS5 with GCC 5.2.0 since it's the official Conda build container."
Answer: 15334.0

User story: "Since the Conda build wouldn't work under the conda GCC 4.8.5 package or ContiuumIO's Docker installed GCC 5.2.0; I investigate other possible GCC versions.    There were a number of issues found with other community conda GCC packages. Additionally when these did work I was able to reproduce problems in DM-7980, DM-8035, DM-7774.    https://github.com/conda-forge/staged-recipes/issues/872    https://anaconda.org/salford_systems/gcc-5    https://github.com/conda-forge/conda-forge.github.io/issues/29    The conda-forge Docker image uses CentOS6 with devtoolset-2. https://github.com/conda-forge/docker-images/blob/master/linux-anvil/Dockerfile    It keeps going there is a lot of discussion and bugs around the available community gcc versions. It should be noted that ContinuumIO's business model is built around this exact fact. If you purchase support you can get further access to build tools."
Answer: 15343.0

User story: "Eventually through fixing DM-8035 and removing DM-7774 and DM-7980 we were able to reproduce DM-8029 using gcc 5.2.0 instead of Conda's gcc 4.8.5.    This is preferable because this uses the same gcc that ContinuumIO uses when they build most official recipes."
Answer: 15357.0

User story: The goal in these attempts were to align the conda-lsst environment and requirements with lsstsw. This addresses the "It works for me" issue with demonstrating build issues.    There appeared to be a problem with how cmake built mariadb and mariadbclient. See DM-8035 and DM-7340. In the end Conda's cmake version 3.3.x was used to build mariadb along with the changes in DM-8035 and patching conda-lsst to use MariaDB/MariaDBClient 10.1.18 instead 10.1.11.
Answer: 15364.0

User story: "Recreate DM-7774, DM-7980, DM-8083 using lsstsw in the conda-lsst docker image."
Answer: 15381.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 running the demo with the Conda v12.1 binaries this error happens:    {code}  vagrant@ubuntu:/opt/var/lsst_dm_stack_demo$ ./bin/demo.sh  Setting up: astrometry_net_data             Flavor: Linux64    Version: LOCAL:/opt/var/lsst_dm_stack_demo/astrometry_net_data  Traceback (most recent call last):    File "/opt/var/miniconda2/opt/lsst/pipe_tasks/bin/processCcd.py", line 23, in <module>      from lsst.pipe.tasks.processCcd import ProcessCcdTask    File "/opt/var/miniconda2/opt/lsst/pipe_tasks/python/lsst/pipe/tasks/processCcd.py", line 22, in <module>      from lsst.ip.isr import IsrTask    File "/opt/var/miniconda2/opt/lsst/ip_isr/python/lsst/ip/isr/__init__.py", line 24, in <module>      from .isrLib import *    File "/opt/var/miniconda2/opt/lsst/ip_isr/python/lsst/ip/isr/isrLib.py", line 27, in <module>      _isrLib = swig_import_helper()    File "/opt/var/miniconda2/opt/lsst/ip_isr/python/lsst/ip/isr/isrLib.py", line 26, in swig_import_helper      return importlib.import_module('_isrLib')    File "/opt/var/miniconda2/lib/python2.7/importlib/__init__.py", line 37, in import_module      __import__(name)  ImportError: No module named _isrLib  {code}    This is caused because ip_isr eventually depends on log4cxx which can't find libexpat.so.0. See this python repl log for the error.    {code}  vagrant@ubuntu:/opt/var/lsst_dm_stack_demo$ which python  /opt/var/miniconda2/bin/python  vagrant@ubuntu:/opt/var/lsst_dm_stack_demo$ python  Python 2.7.12 |Continuum Analytics, Inc.| (default, Jul  2 2016, 17:42:40)  [GCC 4.4.7 20120313 (Red Hat 4.4.7-1)] on linux2  Type "help", "copyright", "credits" or "license" for more information.  Anaconda is brought to you by Continuum Analytics.  Please check out: http://continuum.io/thanks and https://anaconda.org  >>> import sys  >>> sys.path.append("/opt/var/miniconda2/opt/lsst/ip_isr/python/lsst/ip/isr")  >>> import lsst.ip.isr  Traceback (most recent call last):    File "<stdin>", line 1, in <module>    File "/opt/var/miniconda2/opt/lsst/ip_isr/python/lsst/ip/isr/__init__.py", line 24, in <module>      from .isrLib import *    File "/opt/var/miniconda2/opt/lsst/ip_isr/python/lsst/ip/isr/isrLib.py", line 27, in <module>      _isrLib = swig_import_helper()    File "/opt/var/miniconda2/opt/lsst/ip_isr/python/lsst/ip/isr/isrLib.py", line 26, in swig_import_helper      return importlib.import_module('_isrLib')    File "/opt/var/miniconda2/lib/python2.7/importlib/__init__.py", line 37, in import_module      __import__(name)  ImportError: libexpat.so.0: cannot open shared object file: No such file or directory  {code}    This error happens because there was a major release of expat between CentOS5 (the conda build environment) and Ubuntu16.04 (the platform where the error happened).    The fix is to add {pre-link.sh} and {pre-unlink.sh} to our own lsst-log4cxx Conda package that creates a softlink and removes the softlink to the missing file.    
Answer: 18651.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "This will collect the recommendations for all of the individual mapper dataset changes into a single ticket.  These are changes to the Mapper.paf files to correct bugs or inconsistencies.  However, there is no plan to move template locations."
Answer: 27898.0

User story: "Continued effort to understand the components in the Batch Production Service swim lane diagram (DM-7678, DM-8041, etc) and the interactions between components. "
Answer: 34503.0

User story: "Prototype with Pegasus to create an abstract workflow based on the ProcessCcdTask use case, which includes a scatter-gather pattern over multiple dataIds.   Investigate how Pegasus handle outputs as opposed to a butler output repo. "
Answer: 14358.0

User story: "Refactor camera mapper to stop accessing repository data by making filesystem calls directly.    Introduce Storage class and PosixStorage class, and use file-access methods in those classes instead."
Answer: 198732.0

User story: I discovered this morning that there are a bunch of "dead" builds (zombies) listed for the build slave that runs on the same node as the jenkins master.  The master was reporting that it is unable to create temp files and that is why the threads for these builds crashed.  Further investigation shows that the master node is out of disk space and this seems to be due to 100's of GiB of console output from a build that has been running since the 25th and it is still running.  
Answer: 245.0

User story: "Create DMTN documents chronicling the work done for this epic and knowledge gained about the Optimistic Pattern Matcher algorithm.    Deliverables: 1-3 DMTNs:       Document on the prototype python OPMb matcher.      Document describing the data and reasons the algorithm failures.      Document fully describing the final algorithm implemented in the stack."
Answer: 846749.0

User story: "After failures are assessed in DM-8112, implement the fixes to the OPMb algorithm that are required to correct the failure modes.    Deliverable: Implement set of fixes to current algorithm or proposed change to new algorithm to make current failures run properly."
Answer: 194401.0

User story: "Understand specifically why failures occur for certain data sets in both algorithms and if new implementation succeeds explain why.    Deliverable: Short documentation of each failure. (e.g. what was run, how it failed, field properties) Proposed fix if possible."
Answer: 139791.0

User story: "Run the python implementation of OPMb on data with known failure modes with the previous matcher.    Deliverables: Pass/Fail for new code."
Answer: 80591.0

User story: "Implement Optimistic Pattern Matcher B in pure python outside of the stack for testing and better understanding of the algorithm.    Deliverable: Working python code."
Answer: 50151.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: "Email <USER>and <USER>for data that fails astrometric matching.    Copied data to LSST-dev and ready it for processing.    Failure modes have been collected and run. When using GAIA the DECam Hits (visit: 303497) data and CFHT D3 data(visits: 793169, 980526, 896070) all pass with the current LSST matcher.    For the HSC New Horizons data(visit: 3358) the large majority of the CCDs fail to find a match and fail immediately. A few CCDs find a match but the solution yields a scatter of greater than 1 arcsec(ccds: 23, 68, 79). A few other ccds with a lower density of objects that are attempted for matching(~2000 sources) succeed in matching to the GAIA catalog. They are ccds: 108, 110, 111."
Answer: 50151.0

User story: "The API change to footprints will require changes to many things. This is a ticket to capture the work related to updating to the new API."
Answer: 260583.0

User story: "Using the API described in DM-7176, define the new Footprints class based on SpanSets."
Answer: 109361.0

User story: "Move the free function nearestFootprint to a free function in SpanSets, rename it to nearestSpanSet, and update functionality."
Answer: 128069.0

User story: "Add a method to SpanSets which returns a new SpanSet that contains the pixels at the boarder of the original SpanSet"
Answer: 121144.0

User story: Currently SpanSets can intersect, intersectNot, and union between a themselves and another SpanSet. This ticket will add the ability to use these methods with masks as "other". This work will replace the intersectMask and footprintAndMask methods from the old footprint implementation.
Answer: 50154.0

User story: "This ticket covers edits to the [v1 integration branch|https://github.com/lsst/LDM-493/pull/4] of LDM-493 based on feedback from the DMLT."
Answer: 11859.0

User story: "Considering how problematic readProxy objects are to deal with, I feel it might be better to default to {{immediate=True}} for {{butler.get()}} calls. For any test code or interactive code, we want to get an immediately useable object, while inside the pipeline we can be more explicit about {{immediate=False}} when we realize that we're waiting on I/O."
Answer: 151064.0

User story: "version should be 'dev' here, but 'dev' need to be updated to contains DM-7139 code:    {code}  admin/tools/docker/deployment/swarm/manager/env-docker.sh  @@ -2,8 +2,8 @@   # Allow to customize Docker container execution      # VERSION can be a git ticket branch but with _ instead of /  -# example: u_fjammes_DM-4295  -VERSION=dev  +# example: tickets_DM-7139, or dev  +VERSION=tickets_DM-7139  {code}"
Answer: 47341.0

User story: "The currently implemented publisher and consumer objects are written in Python. This story tracks the implementation of a C++ publisher and consumer using a C++ wrapper for Rabbitmq."
Answer: 51837.0

User story: "This story sets down in a spec, the needed interaction between OCSBridge and DMCS. Message dictionary for this part of the L1 ingest system will be located on Confluence page - link to follow."
Answer: 51841.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: "Andy H. provided the solution:  {quote}Hi Fabrice,    Yes, this is common for configurations that don't expect to be dynamically  written to but yet export the space in R/W mode (which we do). All the  message is saying is you don't have enough space for impromptu writes (which  is true but then you don't expect any). So, there is a configuration  directive to resolve this problem:    cms.space 1k 2k    The directive is documented here:  http://xrootd.org/doc/dev45/cms_config.htm#_Toc454223038    I would add this directive to the config file as soon as you can and restart  he cmsd.    Andy{quote}"
Answer: 48255.0

User story: "We update the lsst-dev7 + Verification Cluster documentation to cover the transition / renaming of the head node from lsst-dev7 to lsst-dev01 . "
Answer: 1171.0

User story: "[~<USER> believes we can get back to nulling the low-order SIP terms if we infer the CD matrix as well as the polynomial (but not the CRPIX offset).  He's attached a document (sip_tx.pdf) to DM-3549 with the math demonstrating it.  "
Answer: 1822132.0

User story: "Currently we PSF-match then warp when making PSF-matched coadds. In the case where the output projection is simply a rotation, translation or scaling (circularly symmetric) this is OK if matching to a symmetric model. But for the general case of any affine transform, warping after PSF-matching will undo the PSF-matching.  Also, currently we cannot make PSF-matched co-adds with calexps which were processed with PsfexPsf because ModelPsfMatchTask requires that the input PSF be a KernelPsf.  => we can make PSF-matched co-adds for SDSS which uses PcaPSF by default but not HSC which uses Psfex by default.  (PcaPsf inherits from KernelPsf, and PsfexPsf inherits from ImagePsf.)    This ticket will make the appropriate changes to WarpPsf, ModelPsfMatchTask and WarpAndPsfMatchTask, to make PSF-matching warpedPSFs and PsfexPSFs possible and swap the order of operations. Some emergent considerations for warping first:  1) Warping first shrinks area on which to model the PSF. Need to pad by the spatial cell size.   2) Warped PSF is currently not guaranteed to be: square,  the same size for each image, or the same size across one image. The PSF matcher requires that the model PSF and the science PSF be the same dimensions. Make minimal changes to WarpedPsf to produce square PSFs and PSFs of constant dimensions across the image. Push (modelPsf = self.config.modelPsf.apply() if self.config.doPsfMatch else None) down a level to adapt to the WarpedPSF size rather than be specified by the user. This requires that PSFs have cheap method revealing their dimensions.   3) Spatial Variation.  Currently, a WarpedPsf is an ImagePsf but is not a KernelPsf.     This ticket will include testing. Not in the scope of this ticket is testing and improvement of the performance of the PSF modeling and matching. "
Answer: 45008.0