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: "Create new controller to deal with actions on LC or periodogram or phase folded curve table and xy-plot:  * on row changed,  * on plot highlight.    On both actions, as time changed, the image should be updated in the image grid view with the new single exposure from the dedicated search processor (see DM-7164)    Note: Take into consideration that a user could select a different flux column     Fixed in DM-7167."
Answer: 53224.0

User story: "LC viewer should be able to display a phase folded light-curve after getting the periodogram.  The phase folded light-curve is nothing more than the original LC table (WISE mep) where column 'time' (usually 'mjd') has been divided by a period (in days), where the period is the first value coming from the peaks table or any user defined value.     The new search should produce a new table called phase folded curve based on  * Original table searched  * Period whether it comes from the API result or any other user input    _Note_ on how to compute phase folded curve:    The way to compute the phase is such that:  fluxes = array of fluxes (col1)  times = array of times (col2)  phase[i] = time*[i] - floor(time*[i])    (where “floor” operates like this : 5.6 - floor(5.6) is 0.6. ), where time*[i] = (time[i] - min(time) ) /period     New table produced (phase folded curve) should look like original one (N columns):    col1, col2, ... colN, colN+1    where colN+1 is the phase values.  Plot should be flux (col1) vs phase (colN+1)."
Answer: 50308.0

User story: "One feature the LC viewer (DM-7159) should have is the way to display the single image taken at a particular time corresponding to the flux observed.    The LC table could come with metadata to specify the URL to get the image but if it's WISE, we would take the frame_id value and build the IBE request on the server side.    Create a search to return the image of a particular point in time from the time dependent table.  This will be triggered any time on a row highlighted or a dot in the xy-plot is clicked (DM-7166).    The cutout will be displayed in the image grid view. (The image grid and 'auto-play' can be very fancy, keep as simple as possible by displaying one image at a time?)    Note: For WISE mep, the table has 4 fluxes, the band of the single exposure to be displayed should be an option somewhere in the viewer."
Answer: 94902.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: "A new search is needed to call the API with the particular request and return:  * Power vs period should be viewed as table and plot  * peaks table should be view as table at least     In principle, the new API will return 2 tables (periodogram and peaks table, + extra output parameters if needed) based on the input parameters (see DM-7160).    Nexsci will provide the API to compute a periodogram. See example of the UI here: http://exoplanetarchive.ipac.caltech.edu/cgi-bin/Pgram/nph-pgram    Add a processor that will have as input:  - original table  - API required parameters    and as output those 2 tables describe above (see result of DM-7196).     The processor have a parameter that can distinguish and give back one table or the other so it can be called separately. "
Answer: 53238.0

User story: The main period values come from the result of computing the periodogram (DM-7162), called the peaks table.   The user can input any period value to produce a new table, the phase folded curve (DM-7165).    Add a UI that will take the period value so the user should be able to submit a new request (DM-7165):  * To compute the phase folded curve with the user defined period value    Note: The first time the UI is displayed, the field is empty and the user could 'guess' the period and be able to compute the phase folded curve, without the need to ask for the periodogram. If there is a periodogram, the UI could be suggesting the main period value from the first row of the peaks table. Another way to do it is to add an extra column in the table peaks (DM-7162) that will show a "phase folded curve" link and this could be a trigger to produce a new phase folded curve with the period value from that particular row (TO BE DISCUSSED)
Answer: 94817.0

User story: "A periodogram is the result of applying a algorithm that will found the power spectrum vs. the periods in a time dependent flux data-set. The result of calling the external API will be two tables typically, one the power-spectrum vs periods, and the second is the peaks table. The first value of the peaks table is the main period used to plot the folded phase curve (original flux vs. time/period).    This story is about creating the input panel for requesting a periodogram.    For the LC viewer, we need a place next to the XY plot or to extend the xy plot options to add the following:  * a drop-down list to display choice of API periodogram algorithm  ** For now, Lomb-scargle is the only one available  * input field parameters that are required by the LS algorithm: min period, max period, etc. See snapshot  * 'submit' button to make the call (this is async, for prototype, we could fake the server side search to be slow.)  * field with the period that is a result of the API call, can be changed by user to be re-submit"
Answer: 75994.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 prototype could be considered as a sort of IRSAViewer for handling LC objects / Time dependent dataset, with extra feature that would enable the existing relationship between catalog and image, in particular for WISE, PTF, which could be a reference to single-epoch image (IBE referenced URL typically).    For each observation a corresponding image should be retrieved and placed in a grid (image vs time) either in the same LC object (table) or separately.   One could expect that any LC data-point (time point) would be pointing to an image (single-epoch, exposure) taken from a dataset (image axis would be a 3rd dimension or a 3rd view of LC).  LC should display LC object as following views:  * X-Y plot (typically flux vs time)  * Table  * Images (corresponding image dataset single exposure at a particular time)  The high-level requirements are:  # Easily plot light curve  # Compute Period using Lomb-Scargle   # Display folded Light Curve and Periodogram   # Link Light Curve Points with Single-Epoch Images  # Download Cutouts and Light Curves    In order to create the Light curve viewer prototype, we need to *create a skeleton app to start adding the tri-views* (Upper: plot, Bottom left: table, bottom-right: grid image): (DM-7406)  * Should handle single (one position) LC (table & plot flux or magnitud vs. time, tipically 'mjd')  ** For the prototype it will be a fixed table given  * Image of the single exposure to be displayed at least single page mode  * Should display input for computing a periodogram (the result of an API call)  ** Power spectrum (Power vs log(period) ) as table and xyplot  ** Peaks as a table (Power vs. period)  ** Period (first Period in peak table) as a field (editable), tipically in days.    In order to connect table/plot to single exposure image, be able to compute periodogram and plot based on the table focused, we need a 2 new UI components, 3 new searches and 2 new controllers (tickets will be created separately and added here):      1. UI components:    * To handle the algorithm input parameters to compute ‘periodogram’  (DM-7160)  * To handle the period input (DM-7161)    2. Processors:    whether it is in one search processor or in different one, we need to have the following task processor:    * One to deal with API to compute periodogram that will result at least in 2 tables (periodogram and peaks table, + extra output parameters fi needed) (DM-7162)  * one for getting the image cutout (single exposure) (DM-7164)  * one to build the phase folded curve based on (DM-7165)  ** Original table searched  ** Period whether it comes from the API result or any other changes from user afterward    3. Controllers:  * For image to change on row or xy plot curve clicked (DM-7166)  * For plotting chart based on the type of the table (power vs period, or LC or phase folded) (DM-7167)  "
Answer: 60612.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: "Sort a table first. Then using image selection tool, select an area, then filter: the filter fails. Points are outside the selected area.  Attach one or more files to this issue      This is originally described in DM-7089"
Answer: 1630.0

User story: "I wasn't sure if this should have a ticket or not, so close this out if this has already been addressed.    I read through the draft LDM-151 (version: Friday 15th July, 2016, 23:16hrs) to better understand the app design and how this will relate to what orchestration will have to provide. In the course of doing that, I found the following:    page 24: 3.1.0.8 - Missing word in sentence “Mask CCD defects based on the and saturation”  page 24: 3.1.0.10 - Missing word at the end of  “Source detection to the 5ó limit of”   page 25: 3.1.0.11 - “if” should be “is” in: “Source measurement if for all…”  page 28: 3.2.0.25 - Remove “w” in “…of a TemplateCoadd w that is matched to…”  page 29: 3.2.0.27 - “tempalte” should be “template” in “subtraction of the tempalte image,”  page 30: 3.2.0.29 - Either remove “(“ in “(whose ephemerides have been…” or add one to the end of the sentence…. I wasn’t sure what the intended use was.  page 34: 3.4 - This is the first reference to “Butler”, which hasn’t been mentioned before and is not in the glossary.  Consider adding info about what the Butler is intended to do.  page 41: 4.1.2.3 - Remove “a” from “…this baseline calls for a a routine..”  page 41: 4.1.2.3 - Correct “thie” to “the” in “(outside the scope of thie WBS)”  page 49: 5 - “Howver” should be “However” in “Howver, some part of the graph…” at the end of the paragraph.  page 58: 5.1.2 - Missing comma(s) in “In addition to updating the CalExp WCS and PhotoCalib…”  page 61: 5.2 - “subract” should be “subtract” in “but only subract the updated…”  page 80: 5.5.1 - “later” supposed to be “layer” in “From the Science Pipelines side, Multifit is implemented as two routines, mediated by the orchestration later”  page 87: 6.1 - Third bullet sentence should use “use cases” instead of “usecases”  page 92: 6.2.2 - The sentence “show the running time of the deblending step” seems to be orphaned, and possibly should be removed.  I wasn’t sure of the intent here.  "
Answer: 711.0

User story: "Work required to allow AFW to work on Python 3."
Answer: 12829.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 configurations such as format and levels are different between {{lsst.pex.logging}} and {{lsst.log}}. With DM-6999 logs of command line tasks are changed from {{lsst.pex.logging}} to {{lsst.log}}.  For running command line tasks, logs are configured in {{pipe_base}}.      Based on RFC-203, another main use case is debug logging by running unit tests. In this case, log are not (and cannot be) configured in {{pipe_base}} command line interface.  This ticket adds a default configuration in {{lsst.utils.tests}} so the default logs will look more similar to what they have been with pex.logging when running unit tests. Developers can put customized configuration in each unit test (after DM-6999).   "
Answer: 2875.0

User story: "- Add parameter to indicate which table to display if it's a multi-table fits file.  - If a column is an array type, display the array's data-type and length."
Answer: 14348.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 one is made to include some issues reported in DM-7027 (issue 1, 2, 3, 7, 8)    1. The default coordinate system when "pure numbers" are used should be pixel positions on the original image.  The [spec](http://ds9.si.edu/doc/ref/region.html) says the following:   "...the default system is implicitly assumed to be PHYSICAL. In practice this means that for IMAGE and PHYSICAL systems, pure numbers are pixels."  'If no coordinate system is specified, PHYSICAL is assumed.'  More explanation can be found [here](http://hea-www.harvard.edu/RD/funtools/regcoords.html)    2. PHYSICAL coordinate system does not mean screen pixels. The question is whether we can always use image pixels.  If wcs is "physical", WCS is the pixel coordinate system of the original image, which may be different from the pixel coordinate system of the current image, if the current image is the result of an imcopy or other geometric transformation operation. In the "physical" coordinate system the ltv, ltm and the axis attribute parameters wtype, axtype, units, label, and format may be edited, but the FITS parameters crval, crpix, and cd cannot. [reference](http://stsdas.stsci.edu/cgi-bin/gethelp.cgi?wcsedit)  => PHYSICAL and IMAGE coordinates are treated the same to solve this issue. More improvement will be made in the future to formulate transformation between PHYSICAL  and IMAGE coordinate by looking into FITS header.     3. When used in API, the actions are dispatched one after another. For example, dispatchCreateRegionLayer might be issued before image plot has finished loading. Can we make regionCreateLayerActionCreator wait for image with plotId to finish loading?    More details: If I create a region layer with a few regions in image coordinates right after firefly.showImage, two errors are loaded to console:   doOnAppReady: uncaught TypeError: Cannot read property 'getImageCoords' of null(…),   RegionFactory:602: Uncaught (in promise) TypeError: Cannot read property 'getImageCoords' of null(…)    7. It's possible to select regions only in in the first region layer added. In the other layer, you can sometimes see the selection blinking, but it does not stay.    8. If region format is wrong, for example  'image; box 40 400 72 72 # color=blue' instead of  'image; box 40 400 72 72 0 # color=blue',   the region is silently ignored, no warning or error is logged to console.  
Answer: 8378.0

User story: "At present, if {{lsstsw/bin/deploy}} has successfully installed miniconda but has a failure while installing conda package, the install can not be repaired by rerunning {{deploy}}.  This is due to the miniconda installer refusing to run if the install directory already exists.  This deadlock scenario could be avoided if the miniconda and conda package installs were protected by different lock files."
Answer: 115.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 nature of the process is to have additional monitoring and interaction with staff to review and observe how well plans are followed, tickets are recorded in a timely fashion, and deviations from plans are also recorded and available for analysis and process improvements. "
Answer: 28711.0

User story: "Per RFC-52, packages should list all of their direct dependencies in their table files. This should be included in the developer guide in a page documenting the structure of EUPS packages."
Answer: 1286093.0

User story: "I just tried to build LSST ndarray on Python 3 and it does not work. It's all going wrong as {{include/ndarray/swig}} seems to not be compiling.  {code}  In file included from tests/ndarray-python-mod.cc:25:  In file included from include/ndarray/swig.h:46:  In file included from include/ndarray/swig/numpy.h:33:  include/ndarray/swig/PyConverter.h:175:25: error: use of undeclared identifier 'PyString_AsString'              char * cs = PyString_AsString(s.get());                          ^  {code}  That API changed in Python 3 and it probably should be {{PyBytes_AsString}}.    http://stackoverflow.com/questions/22487780/what-do-i-use-instead-of-pystring-asstring-when-loading-a-python-module-in-3-3#22491037    "
Answer: 1103.0

User story: "BasicTable is no longer needed.  All of its functionalities are covered by TablePanel.  Convert all usage of BasicTable to TablePanel and then remove it.  Add client-side filtering.  It is not converted, yet.     Done, copied from GitHub (8/15/2016)  # removes BasicTable  # client-side filtering  # added more jsdoc to table related code  # fix filter input field auto-correct issue.  # Added table options to basic table as a property. Currently, options is available to fits headers as well as XYplot columns selections dialog.    "
Answer: 16079.0

User story: "As reported by [~<USER> yesterday, if a CI run fails in {{rebuild}} before {{lsst-build prepare}} has completed, bogus log files may be printed to the jenkins console obscuring the true cause  of the build failure.  This appears to happen because log files can be left over from a previous build until {{lsst-build prepare}} has sanitized all product repos that are part of the current build.  "
Answer: 28646.0

User story: "pykg_config 1.2 does not work on Python 3. v1.3 does work."
Answer: 11288.0

User story: This means using the code developed in DM-7129 to study the results achieved on some real data. Likely start by using ci_hsc as a test dataset, and find other data as & when necessary.    End goal is a set scatter plots showing covariance as a function of distance and a parametric fit to that. The easy case is for the "middle" of a coadd, ie with a constant number of inputs: harder, but still necessary, is to see how boundaries where the number of inputs change affect the output.
Answer: 963203.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 code will exist on a ticket (or user) branch, and is not intended for merging to the stack.    It's fine to avoid the normal niceties of I/O for this purpose: ie, dump outputs directly as NumPy arrays to disk, rather than working through the Butler."
Answer: 116726.0

User story: "Maybe start by writing some notes which could be an introduction to a tech note describing the whole of DM-6176."
Answer: 30489.0

User story: "I’ll give two talks at the 2016 project and community workshop    1. A talk for project members on tech writing best practices. I’ll also include a primer on writing numpydoc docstrings.    2. A talk for the community on documentation platforms, and how science collaborations might adopt our platforms."
Answer: 38605.0

User story: "Make an inventory of all packages, Python namespaces, and tasks. This will aid in planning the structure of the Science Pipelines documentation site."
Answer: 203971.0

User story: "while waiting for sign off on composite dataset requirement, begin design work based on current requirements.    "
Answer: 40346.0

User story: "Backup the stable ESXi images externally so we can reproduce the hypervisor environment in the future."
Answer: 41744.0

User story: "Following the installation instructions from http://dm.lsst.org/ produces the following:    {code}  $ curl -O https://sw.lsstcorp.org/eupspkg/newinstall.sh    % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current                                   Dload  Upload   Total   Spent    Left  Speed  100   263  100   263    0     0    740      0 --:--:-- --:--:-- --:--:--   747  $ bash newinstall.sh  !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!  You are following obsolete instructions!  See https://pipelines.lsst.io/install/ for new instructions  !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!  {code}    That's a bit sad for the public face of the project."
Answer: 1172.0

User story: "Current version of my prototype script does not read (forced)sources from database. These will be needed in AP for calculation of the DiaObject parameters. This is probably one of the most interesting features because it is time-based queries and it will potentially have a big impact on database design and may require changes to schema."
Answer: 40447.0

User story: "Issues to think/discuss (in README)  # mention of Firefly Tools  # mention of viewer, plot  (for image display)  # testing data location     "
Answer: 142699.0

User story: "Currently pybind11 uses an explicit mapping:    * {{std::vector}}, {{std::list}} <-> {{list}}  * {{std::tuple}}(, {{std::pair}}) <-> {{tuple}}    The problem of that lies in the two-way conversion. This means that wrapped C++ functions with {{vector}} or {{list}} arguments cannot accept a Python tuple and functions with {{tuple}} (or {{pair}}) parameters cannot accept a Python list. The same holds true for any other sequence type.    This ticket aims to fix this in upstream pybind11."
Answer: 105739.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: While doing timing of various large queries in my AP prototype script I noticed that for some of them significant time is spent in the script itself (CPU time is approximately wall clock time). Profiling shows that most of that time is in sqlalchemy "query compiler". With large query szie (few MBs) this is probably reasonable but I still want to avoid it if possible to get more useful time estimates. Will try to rewrite my script to not use sqlalchemy query mess and instead producing query test myself.    Another reason for this change is to speed up my prototype, right now it runs slower than real life mostly because of CPU time in sqlalchemy.
Answer: 20562.0

User story: "Python future 0.16 is now out. We should update to that version before we begin to use it in earnest."
Answer: 279652.0

User story: "As pointed out in the discussion in SIM-1314, libboost_python.dylib no longer builds against libpython.dylib, so the install_name_tool hack can (probably) be removed from eupspkg.cfg.sh"
Answer: 1563502.0

User story: "Only the first three months of F16 were concretely resource loaded and ingested into PMCS at the start of the cycle. A provisional plan was loaded for the remaining three months. Check, refine and update than plan as necessary."
Answer: 41181.0

User story: "Deliver a modified version of the slides from the July 2016 Joint Directors (sic) Review, plus service any other requests from Project Management."
Answer: 32789.0

User story: "Configure cluster and adapt scripts and methodology as necessary to support qserv deploy on the PDAC cluster at NCSA, as is currently done at IN2P3.  "
Answer: 152322.0

User story: "Support John in adapting scripts and methodology as necessary to support qserv deploy on the PDAC cluster at NCSA, as is currently done at IN2P3.  "
Answer: 103046.0

User story: "This is an initial step to manually launch the containerized DAX services on the new PDAC cluster.  This is meant to expose container configuration, account setup, privilege, logging, debugging, etc. issues."
Answer: 152559.0

User story: The JSON generated by post_qa should include two more fields required by DM-6992 obtained from the following env variables in Jenkins    "ci_name"   from "PRODUCTS"  "ci_dataset"  from "dataset  "ci_label" from "label"    Example of env variables available from Jenkins     https://ci.lsst.codes/job/validate_drp/177/dataset=cfht,label=centos-7,python=py2/injectedEnvVars/  
Answer: 12665.0

User story: "This technote will present an implementation plan for implementing the Science Pipelines documentation site based:    - Initial experience migrating the LSST Stack’s documentation from doxygen to sphinx (see 7094 and DM-7095).  - Pipelines documentation sprint meeting with Science Pipelines representatives, held December 6-9, 2016.    This technote will also cover initial plans for content strategy."
Answer: 220048.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: Since daf_base is low in the dependency tree and dominated by C++ APIs, it is an excellent candidate for exploring Sphinx-based package documenation for C++ with breathe and doxygen. We will also see how astropy’s automodsumm sphinx extension works with SWIG’d Python APIs.    This prototype will build upon the system developed in DM-7094.    Lessons from this prototype will be fed into a "Pipelines Documentation Implementation Planning" tech note in a follow-up ticket.
Answer: 205791.0

User story: "This ticket will kick-off a pilot implementation of pipelines documentation in Sphinx. Specific goals are    1. Develop template for sphinx-ready doc/ directories in packages (based on SQR-006)  2. Setup a MVP sphinx template that works well with numpydoc and astropy automodsumm. Simply porting astropy’s sphinx template would be pragmatic.  3. documenteer-driven configuration for sphinx.    These will be MVPs, and iterated upon in later tickets that implement sphinx API docs for stack packages."
Answer: 205805.0

User story: Our "weeklies" are currently tagged on an ad-hoc basis, often several weeks apart (at time of writing, the latest — {{w_2016_28}} — is 3 weeks 6 days old). Please arrange for them to automatically be built on a predictable weekly cadence.
Answer: 84060.0

User story: "Catalog search panel in IrsaViewer, the target panel label, feedback, and input box are jumping as input is being typed.  Their position should be fixed."
Answer: 5630.0

User story: "Image plot with multiple layers incorrectly apply selection and filtering to all of the layers instead of just the active one.    Steps to recreate in Firefly:    - catalog search, m31 -> radius 100arcsec  - catalog search, m31 -> radius 200arcsec    - select a source in the outer circle of the '200' catalog, notice one is selected from the '100' catalog as well.    - -both layers are acting on the same mouse click-.    - _Sort a table first_. Then using image selection tool, select an area, then filter:  the filter *fails*. Points are outside the selected area.  (DM_7155 has been created for this bug)   "
Answer: 33456.0

User story: "The image select panel needs to be able to modify the coverage image."
Answer: 5546.0

User story: "At present, the doxygen builds are being made available https://lsst-web.ncsa.illinois.edu/doxygen/, which is mapped to {{/home/buildbot/public_html}} on lsst-dev.    This was being accomplished by rsyncing the doc builds over ssh from the {{lsstsw}} account to the {{buildbot}} account.  The {{create_xlinks.sh}} script needs to be updated to simply install into a local path.    [~<USER> has been requested to remap https://lsst-web.ncsa.illinois.edu/ to {{/home/lsstsw/public_html}}."
Answer: 5469.0

User story: "Monitor and generate notifications if the full  stack docs haven't been updated for some reasonable time period.  Say, ~1day."
Answer: 1314844.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: "Time to run my incomplete L! prototype on real hardware, for that I need MySQL and PostgreSQL servers on a dedicated machine in in2p3 cluster (ccqserv124). Probably start with installing what comes with the system repos before trying latest and greatest stuff.    Both servers need to be configured to allow me create databases/tables, and I only need to enable connections from localhost.  "
Answer: 2868.0

User story: "Test and deploy django admin fix from DM-7071."
Answer: 442.0

User story: "Review [Airflow|https://github.com/apache/incubator-airflow] workflow management system against criteria defined in the epic."
Answer: 6064.0

User story: The current build of our Doxygen documentation, as displayed at https://lsst-web.ncsa.illinois.edu/doxygen/x_masterDoxyDoc/index.html, is labelled "Generated on Mon Jun 27 2016 03:52:22 for LSSTApplications". At time of writing, that's more than a month ago. Important additions to the documentations made during the last month are missing.  
Answer: 6003.0

User story: "This upgrade requires moving from Topbeat to Metricbeat which requires some minor rework and upgrading the entire system at once."
Answer: 175545.0

User story: "Install, configure and snapshot MacOS Sierra. This requires configuring the vmx file then installing Mac OS X Mountain Lion and upgrading."
Answer: 3.0

User story: "Install, configure and snapshot Mac OS X El Capitan. This requires configuring the vmx file then installing Mac OS X Mountain Lion and upgrading."
Answer: 2.0

User story: "Install, configure and snapshot Mac OS X Yosemite. This requires configuring the vmx file then installing Mac OS X Mountain Lion and upgrading."
Answer: 2.0

User story: "Install, configure and snapshot Mac OS X Mountain Lion. Unfortunately this is required to install any other Mac OS VM on ESXi."
Answer: 2.0

User story: "Install and configure ESXi on the Mac Pro server."
Answer: 11.0

User story: "Travel to Princeton June 13-17 and meet with the DRP team; work and learn about L2 processing; discuss the workflow requirements and use cases. "
Answer: 1.0

User story: "Django admin interface is useful to edit db entries in SQUASH if needed, e.g decam measurements that were incidentally pushed to the dashboard during X16.    A bug was found using the admin interface in development mode, due to a bad field returned by the Jobs model.    This ticket is to capture the fix for this bug, this new git ref will be deployed for better control of data in SQUASH database.    "
Answer: 162.0

User story: "There are three values at the top of Associations.cc under a TODO comment that should be lifted up into JointcalConfig so they can be configured at runtime. It would be good to try to add tests to check different values for them (and possibly just remove usnoMatchCut)."
Answer: 359977.0

User story: "Work relating to getting daf_persistence to run on python 3. Includes some code modernization."
Answer: 15481.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: "*Issues*    Gator:  * Missing feature: before migration, in expanded mode, the toolbar had an 'added image' button which was bringing an image search panel to add images to the current view.    * The Gator Multi-object search seems having problem with the coverage image.    Atlas:    * if marker/footprint overlay is clicked, that doesn't activate the image viewer and doesn't update the layer dialog either. Large drawing layers block viewer from becoming active, WFIRST footprint or WFC3/IR cause the problem.  *  -in expand mode and zoom 'fill the visible space' clicked, the magnifier image doesn't show anything from the coverage- - not a bug, magnifier is disable when zoom level is above 8x     API:  *  In API, it is not possible to drag dialogs (ex. Drawing Layers).    All Firefly (found by Tatiana):    * The highlight should of catalog or coverage overlay should just change if you are close to the point. For now I am setting it to 20 pixels  * -Catalog overlay should not use table id in drawing layer description. (See the attached screenshot.) It should be using MetaConst.CATALOG_OVERLAY_TYPE attribute value.- _Moved to_ DM-7055    * After using distance tool in one plot, then the other, clicking again in the first plot does not make it active. (You have to click on the border of the plot to make it active, clicking inside does not help.)    This seems to cause strange behavior, when selections do not work as expected. For example: select ruler, select some lines alternating first and second plot. Unselect ruler, select area icon. Selecting in the first plot will still show distance. I had to delete distance tool drawing layer or click on the border for things to start showing area selection.    In general, there is some confusion with active plot, when I have two viewers. Should a plot become active as soon as mouse enters is? Otherwise in readout, compass thumbnail will still show active plot, while readout thumbnail could use another plot.  _note from trey: this is the same problem as the marker/footprint in atlas described aboved_"
Answer: 5666.0

User story: "lsst/jointcal is still linked to the upstream repo at lsst_france. I believe all the relevant changes have been ported. It's time to break that upstream link, so that pull requests can be made in a more obvious fashion."
Answer: 16207.0

User story: "Work required to get pex_logging working on python 3. Will also include some package cleanups."
Answer: 15639.0

User story: A package for experimental Jupyter widgets for Firefly is being developed in  https://github.com/Caltech-IPAC/firefly_widgets . Using the Firefly Javascript API for Images and Tables, add this functionality:    * a "connect" method that connects to user-specified Firefly server location and loads JS from it  * for images served by 2MASS, change the location and the survey band  * change the colormap for images  * allow a FITS image to be uploaded to a ImageViewer widget  * allow a table to be uploaded to a TableViewer widget  
Answer: 116828.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: It was realized that the "shared stack of lsstdev" was not actually usable on the local condor pool due to /ssd usage.   In response to this,  an effort for a second shared stack on NFS  was initiated in DM-6968.  This issue captures the emergent work of pipeline testing to validate the new stack of that issue. 
Answer: 1492.0

User story: "This issue captures emergent work to support for example DM-6905 , for which I spent some cycles locating datasets of the 2013  SDRP, staging some files off of BW tape through globus online and unpacking to /nfs/scratch,  etc.    This effort may not fit exactly as 'emergent middleware',  but it was roughly the best fit at this time. "
Answer: 1512.0

User story: "Following the same pattern as DM-6926, DM-6297, etc.    The tests included in this ticket are:    # testSchema.py  # testSimpleTable.py  # testFunctorKeys.py"
Answer: 161543.0

User story: "# disable sorting when content is html  # table options: auto-adjust all column width based on content  # table refractoring: exposing more actions to saga.  #* renamed a few actions to better reflect what it's doing.  #* added TABLE_FILTER  #* added document for sequence of actions where applicable.  # update build script to skip buildClient when possible.  # Catalog overlay should not use table id in drawing layer description. (See the attached screenshot.) It should be using MetaConst.CATALOG_OVERLAY_TYPE attribute value"
Answer: 7474.0

User story: "[~<USER> & [~<USER> will meet with the SUI/T team on 2016-07-26 and discuss how we can best engage with them."
Answer: 3.0

User story: "Create a database populated with complete catalogs resulting from processing of the *SDSS Stripe 82* data at both NCSA and IN2P3 sites. -The database has to be created at NCSA on the following database server *lsst-db.ncsa.illinois.edu*-  * 2016-08-10: *CORRECTION*: that was the original plan. Due to the space limitation on that server the database will be installed on Nebula volume *lsst-dm-<USER> attached to image *lsst-<USER>0* (floating IP address *141.142.211.152*). See details on this setup in the comments stream below.)     The database name will be: *<USER>SDRP_Stripe82*    The database will be populated with the contents of the following databases:  * *NCSA* (lsst-db.ncsa.illinois.edu):  {code}  daues_SDRP_Stripe82_ncsa  daues_SDRP_dedupe_byfilter_0  daues_SDRP_dedupe_byfilter_1  daues_SDRP_dedupe_byfilter_2  daues_SDRP_dedupe_byfilter_3  daues_SDRP_dedupe_byfilter_4  {code}  * *IN2P3* (ccdb02.in2p3.fr):  {code}  lsst_prod_DC_2013_2  lsst_prod_dedupe_byfilter_g  lsst_prod_dedupe_byfilter_i  lsst_prod_dedupe_byfilter_r  lsst_prod_dedupe_byfilter_u  lsst_prod_dedupe_byfilter_z  {code}    Additional requirements:  * The duplicate entries (due to the overlap in the RA range) will need to be carefully assessed and eliminated.  * the referential integrity of the resulted database will need to be tested  "
Answer: 77991.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: "It looks like getting things working again is simply a matter of adding XrdSsiRequest::PRD_Normal as the return value for void QueryRequest::ProcessResponseData(char *buff, int blen, bool last).    To get it working as desired will take more work. If XrdSsiRequest::PRD_Hold is returned, and then restarted later, then ProcessResponseData(char *buff, int blen, bool last) will have exactly the same information as the first time, correct?    I suspect what I will do is have QueryRequest remember if the last call triggered a large response and if 'not last' then increment a semaphore or something and return XrdSsiRequest::PRD_Hold. There might be a race condition between returning XrdSsiRequest::PRD_Hold and the call to XrdSsiRequest::RestartDataResponse(), and I'm not sure what would happen if XrdSsiRequest::RestartDataResponse() is called before XrdSsiRequest::PRD_Hold is returned. It might take some shenanigans to ensure that the semaphore is updated after the return statement.    There's also InfileMerger::_largeResultPool which will no longer serve a purpose.    xrootd specifics  http://xrootd.org/doc/dev42/ssi_reference.htm#_Toc452741870  "
Answer: 423393.0

User story: "Currently LTD Keeper uses a sqlite DB. This ticket will migrate that DB to Google’s Cloud Platform’s managed SQL. This solution provides automatic backups, and provides flexibility to run multiple ltd-keeper pods. Google’s SQL makes sense since LTD Keeper is run on Google Cloud Platform."
Answer: 10413.0

User story: Implement RFC-204 by adding new entries for all patch/tract and config mapping definitions to .yaml files in daf_butlerUtils, and removing any such entries that are identical to the common ones from .paf files in obs* packages.    I think the "common" entry can usually be defined by consensus between any two of obs_cfht, obs_decam, and obs_subaru (and frequently all three).  If there are any patch/tract or config datasets for which no two cameras agree, I think we should use obs_subaru's definitions (but I doubt there are any such cases).    Entries that are not identical to the common ones should not be removed on this issue (that should make this change entirely backwards compatible), but should be documented in new per-camera issues for later standardization.
Answer: 75411.0

User story: "need to change obs_decam's ingest task to use the newer class hierarchy to get the root of the butler's single repository. (longer term there should be a butler API for this or the task should get the value of root from somewhere else)"
Answer: 316.0

User story: "Work involved in ensuring that pex_config passes all tests on Python 3 and legacy Python."
Answer: 12998.0

User story: "There is a requirement for composite datasets that components of composites be cached and shareable, and we expect to use an object cache for this.   We have identified that we need to be able to cache C++ weak_ptr and python weakref in the same cache in an opaque way. This needs some prototype R&D."
Answer: 123641.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 a port of [HSC-1397|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1397] to support reduction of observations with the new HSC-I2 filter.  There is already support for reading that data, but we need a few config tweaks to allow processing it."
Answer: 1160.0

User story: "Reference band selection currently depends on the configured band priority order, with exceptions made for sources with low signal-to-noise in the high priority bands.  [HSC-1411|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1411] points out that some additional qualifications, such as success for major measurements (e.g., CModel and Kron), would be helpful."
Answer: 1793.0

User story: "In DM-6629, a new measurement API was introduced into validate_drp that established a JSON data model for metrics, specifications of metrics, measurements, and general blob datasets. The intent of that work is to enable rich plots in the SQUASH dashboard, with access to data behind measurements. The new data model also clarifies the subtleties of metric specifications (filter dependence, and dependence on other specifications). This ticket will incorporate validate_drp’s new data model into the SQUASH database and API.    Also related to DM-7041, which will update the post-qa tool that submits validate_drp json to the SQUASH API."
Answer: 253819.0

User story: "This ticket is to refine and improve the usability and documentation of {{validate_base}}, original ported in DM-7692.    One goal is to improve API usability by better incorporating astropy units.    Another goal is to {{validate_base}} to use PEP-style names (RFC-97).    On the matter of RFC-97, which is still flagged, SQuaRE does have a waiver to use PEP8. As {{validate_base}} has not consumers (yet), is is appropriate to switch API naming at this time.    In conjunction with this, the docs should be updated to use the new Sphinx templates and configuration (DM-7094), be updated with the new API names, and generally be polished."
Answer: 179052.0

User story: "DM-6629 introduced a new measurement API. The {{post-qa}} app needs to be updated to shim and upload this JSON to the SQUASH API.    Note that this ticket only updates the shims for the new measurement api's JSON to the current SQUASH API. A separate ticket will be needed to then adapt this the output schema for a more fully-featured SQUASH API.    This ticket should use [JSON Schema|http://json-schema.org] to validate that the shims are successfully producing the JSON that is expected by the SQUASH API."
Answer: 138651.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "<USER>writes in [HSC-1414|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1414]:  {quote}  See the following lines:    meas_algorithms/HSC-4.0.0/python/lsst/meas/algorithms/objectSizeStarSelector.py:466  in ObjectSizeStarSelector.selectStars():  {code}      if psfCandidate.getWidth() == 0:          psfCandidate.setBorderWidth(self._borderWidth)          psfCandidate.setWidth(self._kernelSize + 2*self._borderWidth)          psfCandidate.setHeight(self._kernelSize + 2*self._borderWidth)  {code}    In reduceFrames, these lines set the width of psfCandidate to be 21  for the first time the execution reaches there.    When the first CCD image has been processed, the worker process  continues to process another CCD image, and the execution reaches  here again.  This time, psfCandidate.getWidth() is 41, because  psfexPsfDeterminer has set it to be 41, and the value has been  retained because the width is a static member.  And so, for the second  CCD image, the width of psfCandidate is not 21 but 41.    Since psfCandidates are widened, stars positioned at edges of images  are rejected.  It results in a smaller number of PSF candidates than expected.    Only CCD images that are initially given to the worker processes  are processed with psfCandidate.getWidth() == 21. The other CCD images are  processed with psfCandidate.getWidth() == 41.  When the number of SMP cores changes, CCD images are processed with different  parameters.    The change in the number of PSF candidates results in different Psf, a different  result of image repair, and different catalogs.  {quote}    The line numbers are different on the LSST side because of refactoring (objectSizeStarSelector.py:466 has moved to starSelector.py:148), but the bug is still present.  The main problem appears to be that the {{PsfCandidate}} elements are {{static}}, are being set in both the star selector and the PSF determiner and one of those is conditional on what the value is.  I will investigate moving the {{static}} class variables to instance variables --- the desired size appears to vary by context, so it shouldn't be a class variable."
Answer: 11583.0

User story: "Familiarize yourself with the RFC-37 driven Footprint redesign. Start thinking about ideas for how you could implement it and what the transition plan from the current Footprints might be.    A great outcome would be to propose a set of stories which would tackle the new Footprint development effort.    A good outcome would not be to have the stories ready to go, but to be well prepared for a discussion with [~<USER> & [~<USER> where we'll come up with some stories as a group."
Answer: 18646.0

User story: "We need generate and publish JSDoc for Firefly JavaScript API, both high and low level."
Answer: 53578.0

User story: "Changes needed to make pex_policy work on Python 3"
Answer: 13276.0

User story: "Meet with Simon & John. Discuss the Algorithmic Components section of LDM-151: clarify any ambiguities and perform an initial resource loading estimate"
Answer: 2.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: "Meet with Jim & Simon. Discuss the Algorithmic Components section of LDM-151: clarify any ambiguities and perform an initial resource loading estimate"
Answer: 2.0

User story: "Meet with Jim & Simon. Discuss the Software Primitives section of LDM-151: clarify any ambiguities and perform an initial resource loading estimate."
Answer: 2.0

User story: "- Image is coming with one draw layer. (I can delete this draw layer and nothing changes on the image)    - When draw layer is deleted, and no more layers are present, the layers dialog should be closed. (It stays with nothing to display, you have to click x to close it.)    - After selecting an area in one viewer, I select an area in another viewer, then move the mouse to the first one:      147 ImageViewerLayout.jsx:314 Uncaught TypeError: Cannot read property 'x' of null at ImageViewerLayout.jsx:314   Nothing works after that. I have to reload.    - Selection appears with an offset, if the page, which contains the viewer is scrolled. (Load the attached script, press 'Start selection tracking' click to select a point, then scroll page a bit down, then click to select another point - it shows down from where it should be.)    - I have 2 image viewers in separate divs. Selected line in one, then selected line in the other. The line from the first one disappeared, but its label is still there. (See attached image.)    - Selection is working differently from distance. To select in another plot, I need to press selection again. I don't need to press ruler again to select new distance in another plot.    - It's possible to select distance tool and then area selection. First drag would define area selection, all the following line. A click would be defining a 0 length line, even if point selection is enabled. _move to_ DM-6473    - The payload.attValue of CHANGE_PLOT_ATTRIBUTE action is using WorldPt for area and point selections (when payload.attKey is 'SELECTION' or 'ACTIVE_POINT'), but ImagePt for line selection (when payload.attKey is 'ACTIVE_DISTANCE') How can I make them all use image coordinates?        "
Answer: 4393.0

User story: "Changes necessary to get daf_base to work with Python 3."
Answer: 14394.0