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: "When you rerun {{ci_hsc}} after changing something it fails as the versions have changed.  The/a natural reaction is to run {{scons -c}} (i.e. clean), but unfortunately that doesn't help.    Please make {{scons -c}} delete the rerun/ci_hsc directory.  "
Answer: 43.0

User story: "When building astshim on maxOS I see the following warnings from ndarray that seem as if they might be easy to fix:  {code}  In file included from /Users/<USER>UW/LSST/lsstsw/stack/DarwinX86/ndarray/1.3.0/include/ndarray.h:20:  /Users/<USER>UW/LSST/lsstsw/stack/DarwinX86/ndarray/1.3.0/include/ndarray/ArrayRef.h:393:39: warning: struct template 'ArrayAccess' was previously declared as a class template        [-Wmismatched-tags]      template <typename Array_> friend struct detail::ArrayAccess;                                        ^  /Users/<USER>UW/LSST/lsstsw/stack/DarwinX86/ndarray/1.3.0/include/ndarray/detail/ArrayAccess.h:26:7: note: previous use is here  class ArrayAccess {        ^  /Users/<USER>UW/LSST/lsstsw/stack/DarwinX86/ndarray/1.3.0/include/ndarray/ArrayRef.h:393:39: note: did you mean class here?      template <typename Array_> friend struct detail::ArrayAccess;                                        ^~~~~~                                        class  {code}"
Answer: 818237.0

User story: "The fundamental issue is that {{lsstsw/lsst-build}} operate on refs in the git repo.  Due to the way eups generates version strings from git tags, we are unable to tag the repos for 3rd party products.  This means that we are unable to build a last tagged release from source once a 3rd party dependency has been upgraded to an incompatible version."
Answer: 14284.0

User story: "[~<USER> requested:  I think it'd be really helpful to have a relatively short document describing (or at least mentioning) the features that are in the butler that the `classic' butler didn't have.    I think we can put a section in LDM-463 for this."
Answer: 39031.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: In python 3 all integers are 64 bit "long" integers, while in python 2, 32 and 64 bit integers are differentiated by the int and long types respectively. This causes confusion when adding a new field to a schema using addField in afw/table/Base.i in python 3, where the python type is converted into a C++ type using a dictionary    {code:python}  aliases = {      long: "L",      int: "I",      float: "D",      str: "String",      futurestr: "String",      numpy.uint16: "U",      numpy.int32: "I",      numpy.int64: "L",      numpy.float32: "F",      numpy.float64: "D",      Angle: "Angle",  }  {code}    In RFC-227 it was decided that {{int}} and {{long}} will be removed from {{aliases}}, leaving  {code:python}  aliases = {      str: "String",      futurestr: "String",      numpy.uint16: "U",      numpy.int32: "I",      numpy.int64: "L",      numpy.float32: "F",      numpy.float64: "D",      Angle: "Angle",  }  {code}    All existing code using `type=long` will need to be updated as part of this ticket.    This will be included in the pybind11 wrapped code, with a deprecation warning for users attempting to add fields using {{int}} or {{long}}.
Answer: 201219.0

User story: There are some lingering incorrect "you should..." statements in the "merging work" section of DMTN-027, that should be referring to the "other developer", and the text needs to be reworded to reflect that dependencies on master need to live in {{lsst}}, and so some extra repository shuffling has to happen.    A few relevant quotes from Slack:    About how to move things without deleting daf_butlerUtils:    {quote}  <USER>[11:50 AM]    move daf_butlerUtils into lsst-sqre, move obs_base into lsst, move daf_butlerUtils into lsst-dm  {quote}    About unclear "you":    {quote}  <USER>[11:53 AM]  Oh, except I missed this at the top "Once your rename has been merged to master,"  One thing about that section that I noticed before but didn't comment on: it's sometimes unclear who "you/your" is -- the renamer or the "other developer"    <USER>[11:55 AM]  I tried to make it always be “you” as the person doing the rename. The person the whole document is aimed at.  If I got that wrong somewhere, I’m happy to fix it.    <USER>[11:55 AM]  But "your work-in-progress branch" is really "the other developer", no?  Same for "Check that the branch in the new clone matches your branch in meas_worst,"  @parejkoj So I think the rest of the document is fine as long as you put in that merging to master also involves moving to lsst and change the remote url in the instructions.  {quote}
Answer: 269.0

User story: "Swarm mode provide high availabilty feature wich will be tested on Openstack."
Answer: 50301.0

User story: """Swarm mode"" now works on Openstack, it will be tested at CC-IN2P3 before PDAC deployment."
Answer: 43109.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: {code}  [dev@centos-7 conda-lsst]$ conda lsst make-recipes build:b2317 afw --build  Traceback (most recent call last):    File "/opt/conda-lsst/bin/conda-lsst", line 105, in <module>      config = Config(root_dir, [os.path.expanduser('~/.condalsstrc'), 'etc/conf  ig.yaml'])    File "/opt/conda-lsst/conda_lsst/config.py", line 298, in __init__      ] + _get_our_channels(self.our_channel_regex)    File "/opt/conda-lsst/conda_lsst/config.py", line 315, in _get_our_channels      chans = [ urljoin(conda.config.context.channel_alias, str(u)).rstrip('/ '$   + '/' for u in conda.config.get_rc_urls() ]    File "/opt/conda-lsst/miniconda/lib/python2.7/urlparse.py", line 259, in ur$  join      urlparse(base, '', allow_fragments)    File "/opt/conda-lsst/miniconda/lib/python2.7/urlparse.py", line 143, in ur$  parse      tuple = urlsplit(url, scheme, allow_fragments)    File "/opt/conda-lsst/miniconda/lib/python2.7/urlparse.py", line 182, in ur$  split      i = url.find(':')  AttributeError: 'Channel' object has no attribute 'find'  {code}
Answer: 24512.0

User story: Since version 0.12.3 of bokeh [http://bokeh.pydata.org/en/latest/docs/releases/0.12.3.html] data tables can have editable fields.     In the monitor app table we can have a new field "Comments" for entering comments on a specific job (e.g. user wants to make annotations about a metric deviation)
Answer: 1193748.0

User story: "Dynamically Provisioning Persistent Volumes in the context of Openstack and Kubernetes. "
Answer: 272101.0

User story: "As discussed in [https://community.lsst.org/t/implementing-rfc-95-populating-datasets/1266/11], {{obs_subaru}} includes various proposal and field identifiers in the registry to enable a single repo to store data from multiple observing programs. {{obs_decam}} should be updated to enable the same thing. Storing the {{OBJECT}} and {{PROPID}} fields would be a would be useful to start, but I haven't looked exhaustively through the headers for any other useful entries."
Answer: 37.0

User story: "Create a deploy a Kubernetes cluster automatically on Nebula, with its own private Network, CNI, and dashboard in a automatic manner. "
Answer: 15776.0

User story: "Work through the ~40 action items that came out of discussing the CPP section of LDM-151 with [~<USER>.    The work will involve:  * editing the document   * multiple read-throughs while holding different things in my head which need to be checked against  * reading other parts of the document, and editing for them consistency   * hunting for the use each and every one of the outputs from the CPP section.  * discussing plans for parts of the processing with others and editing for consistency      "
Answer: 229377.0

User story: "Kubernetes made an auto-discovery process to create a build a Kubernetes cluster on top of a pre-defined cluster. This is an improvement on previous installation methods"
Answer: 15780.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: In a style similar to the conops document for data processing, produce what is destined to be a "living document" describing the taking (and processing?) of the calibration data.    This ticket doesn't budget for maintaining this document, nor making it perfect, but to produce a decent first pass to paint a picture and see if it will be useful going forward.    This will likely be a Google doc.
Answer: 211564.0

User story: "Review the document detailing Stubb's plan to use Am241 gammas from outside the cryostat to perform absolute gain calibration in the main camera for any gross errors in reasoning."
Answer: 2663.0

User story: "It was determined (DM-7841) that the previously claimed successful (DM-7657) implementation of decorrelation when pre-convolution is enabled is not actually working.    We therefore closed DM-7841 as wont-fix and this ticket is to be marked as Done, with a note that we have so far been unsuccessful in correctly and robustly implementing noise decorrelation when pre-convolution is enabled, either in the stack or outside of it.    We will investigate this further in the future after further evaluations of ZOGY, etc."
Answer: 2.0

User story: The last couple of weeklies don't see to have manifests for lsst_distrib.    For example, for {{w_2016_43}}, the [table file|https://sw.lsstcorp.org/eupspkg/tags/w_2016_43.list] refers to lsst_distrib version {{12.1+29}}.  However, there is [no corresponding manifest available|https://sw.lsstcorp.org/eupspkg/manifests/]; when I try to install with {{eups distrib}}, I get:    {code}  eups distrib: Trouble reading manifest for lsst_distrib 12.1+29 (generic): First line of manifest file /tmp/eups/distrib/lsst_distrib_azCwH2 is corrupted:      <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">  {code}
Answer: 15912.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 attempting to identify galaxy clusters in the HSC data via the red-sequence cluster finder CAMIRA, it was found that galaxies near the cluster center were entirely missing.  One likely cause of this is that the deblender is failing in one or more bands causing incorrect measurements of the colors.  This appears to be true for different flux measurements.  In the short term we have attempted to fix this by measuring colors in fixed apertures on the parent images, but we need to find what is the root cause.      Here is an example of a cluster at redshift z=0.74 with missing galaxies near the center.  The circled galaxies are those identified as part of the cluster.      !members.jpg|width=600!    Running sextractor on the same -i-band data and comparing 2" shows a number of outliers.      !sextractor.jpg|width=400!    If you plot the position of these outliers, many of them correspond to the cluster members at the center.  The outliers also correlate well with the blendedness parameter.    !outliers.jpg|width=600!      The position of this cluster is RA=32.8119 and Dec=-3.723.   There is another example of this at RA=215.97466 Dec=-0.43444.  It is estimated that 20% of large clusters suffer from this problem.         
Answer: 125623.0

User story: "After upgrading to El Capitan (and it's version of XCode), jointcal now segfaults at the {{CollectLSSTRefStars}} step, specifically at the start of {{AssociateRefStars}}. It appears that the bare refStar pointer in FittedStar isn't getting initialized when compiled with optimization on. We should probably make that bare pointer a shared pointer anyway. There may be other fun bad pointer usage hiding elsewhere too.    It's probably worth running valgrind (or equivalent) on jointcal to see what else turns up."
Answer: 85061.0

User story: "Using ProcessCcdTask as an example, produce a proof-of-concept demonstration of what future task documentation will look like."
Answer: 55584.0

User story: I feel the new {{PlusPlus}} bot is intrusive and that it dramatically lowers the S/N level in the rooms in which it lives. Unfortunately it seems that it can easily be invited into any room. I suggest it be deleted.    I understand a desire to be able to give kudos to users, but I wish it could be done without a scorecard (especially one all readers of a room have to see when anyone looks at it) and without the bot obnoxiously butting in every time somebody pats somebody on the back.    Perhaps it would suffice to accumulate a count of users whose posts get a "thumbs up" reaction and make that information available somewhere out of the way for users who care?    I realize many users are enjoying it. I also realize that the noise level will probably drop as folks get tired of it. Nonetheless, I request that it be removed.
Answer: 240503.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "We should load Earth Rotation Angle into VisitInfo, though it may require some calculations based on TAI/UT1 and/or the LST value read from the headers. Once we have ERA, we should convert our LST values to be computed from ERA.    Russell's comment about it on slack:    {quote}this seems to have the info: https://books.google.com/books?id=MM1LDzQIJ9kC&pg=PA317&lpg=PA317&dq=difference+between+earth+rotation+angle+and+greenwich+mean+sidereal+time&source=bl&ots=Hhg2i-DTVZ&sig=FzjubnSJpPYnALZ2aDtGKVwaJS8&hl=en&sa=X&ved=0ahUKEwiatubqperPAhWCgFQKHbbHBUAQ6AEIUTAH#v=onepage&q=difference%20between%20earth%20rotation%20angle%20and%20greenwich%20mean%20sidereal%20time&f=false    And, furthermore, it looks like ERA is equal to GMST within smallish terms.    None of the camera headers I know of for our obs_ packages specify UT1. Most seem to specify LST (I have no idea if that is mean or apparent). So it might make sense to just assume this is LMST, adjust for longitude and write it as an approximate ERA.    A different option, which relies on an internet connection, is to use astropy.Time to compute UT1 from TAI. This will download a file from IERS that has UT1-TAI from 1970 through a few months in the future. That file will quickly go out of date and thus need to be re-downloaded as we process newer data. (Dates outside the range of the file are handled by assuming things are static past the ends of the file, which is reasonable). It makes me uneasy to use such a file, but it would be very nice to have UT1 and ERA is trivial to compute from it.  {quote}"
Answer: 1371483.0

User story: "While we determine how we are going to work with Earth Rotation Angle (ERA), we should at least load Local Sidereal Time (LST) into VisitInfo. It is available from most of the current obs package headers.    Once we sort out ERA, we can decide whether to use the LST value from the headers, or one we've computed from ERA."
Answer: 39443.0

User story: "The level 1 db prototype schema from here: [https://github.com/lsst-dm/l1dbproto/blob/master/python/lsst/l1dbproto/l1db.py] and [https://github.com/lsst/cat/blob/master/sql/baselineSchema.sql] has some inconsistencies with the latest version of the DPDD (from 9/26/2016).    I've just looked through diaSource and diaObject, mainly.  The biggest things for the diaSource table are that dipole measurement fields in the DPDD are not in the schema and it is unclear how some fields like the second moments of intensity and some covariance terms match up between the schema vs DPDD."
Answer: 26263.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "When I am working on the unit test for Crop class, I noticed that it uses switch bitpix to deal with different data type.  Since float is used for FitsRead, it should be updated accordingly.    [Update 11-09-16]  In July 2015, the CropAndCenter was refactored.  When it was refactored, I noticed that Crop.java and CropAndCenter have many common codes.  So a method do_crop   {code}  Fits do_crop(Fits inFits, int min_x, int min_y, int max_x, int max_y)  {code}  was added to the CropAndCenter class.  Thus, the Crop.java became redundancy.   It could be removed from the system.  I searched usages and found it is not used at all.   I think that  it is safe to remove it now.    This ticket will include the following work:  * Remove Crop.java  * Refactor CropFile.java in the same manner as CropAndCenter, FitsRead etc.  * Add unit tests for both CropAndCenter and CropFile classes    "
Answer: 119666.0

User story: In order to understand when ZOGY will "break", we need to better quantify exactly when PSF measurement "breaks" in the stack. Use simulated very sparse and very crowded fields to test the PSF measurement task. (Using both "psfex" and "pca"?)
Answer: 59029.0

User story: "Assess the scaling of run-time with image size and number of PSF matching stars."
Answer: 46221.0

User story: In RFC-212 we adopted turning on the "junk suppression" temporary local background subtraction by default: {{SourceDetectionConfig.doTempLocalBackground=True}}.  Since the safe clipping coadd assembly (introduced in DM-2915) also performs object detection, this had the effect of turning on the junk suppression background there too.  The safe clipping algorithm was designed and tuned with no extra background estimations, thus {{doTempLocalBackground}} should default to *False* for that task.
Answer: 58977.0

User story: "Two of the functions in the display interface fail to return their values (one should be the transparency; the other the value of `show').    I need both of these to support ginga, so I'd like to add them.  I don't think that this can break anything, and I need practice merging properly so that's another benefit.  "
Answer: 15891.0

User story: "Curate documentation defining terms used in swim lanes diagram. Publish in appropriate location."
Answer: 188618.0

User story: "The new VisitInfo interface to exposure metadata has broken some minor functionality of the DCR modeling code, but promises to greatly simplify the task of reading real data. This ticket is to update the reading and writing of metadata to use VisitInfo."
Answer: 15836.0

User story: "Review of swim lanes diagram with SLAC and DM system architect."
Answer: 63292.0

User story: "Launch the ProcessCCD dag from the workflow management system. Initial implementation will most likely use Pegasus."
Answer: 63329.0

User story: "Run ProcessCCD pipeline at the level of Executor and beyond."
Answer: 18646.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 majority of the {{daf_persistence}} tests fail when attempting to build a conda package via {{conda-lsst}} on el5 with gcc 5.2.    {code:java}  Traceback (most recent call last):    File "tests/reposInButler.py", line 36, in <module>      import lsst.daf.persistence as dp    File "/home/<USER>conda-lsst/miniconda/conda-bld/work/python/lsst/daf/persistence/__init__.py", line 28, in <module>      from .persistenceLib import *    File "/home/<USER>conda-lsst/miniconda/conda-bld/work/python/lsst/daf/persistence/persistenceLib.py", line 27, in <module>      _persistenceLib = swig_import_helper()    File "/home/<USER>conda-lsst/miniconda/conda-bld/work/python/lsst/daf/persistence/persistenceLib.py", line 26, in swig_import_helper      return importlib.import_module('_persistenceLib')    File "/home/<USER>conda-lsst/miniconda/envs/_build/lib/python2.7/importlib/__init__.py", line 37, in import_module      __import__(name)  ImportError: No module named _persistenceLib  tests/butlerSubset.py  {code}    I'm at a loss as why the tests are failing in this environment.   The library is being successfully built.      {code:java}  $ ls -la /home/<USER>conda-lsst/miniconda/conda-bld/work/python/lsst/daf/persistence/_persistenceLib.so   -rwxrwxr-x 1 <USER><USER>9716560 Oct 19 14:47 /home/<USER>conda-lsst/miniconda/conda-bld/work/python/lsst/daf/persistence/_persistenceLib.so  {code}        {code:java}  $ swig -copyright    SWIG Version 3.0.10  Copyright (c) 1995-1998  University of Utah and the Regents of the University of California  Copyright (c) 1998-2005  University of Chicago  Copyright (c) 2005-2006  Arizona Board of Regents (University of Arizona)  {code}    
Answer: 118394.0

User story: "Please reprocess the validation data sets so that their output data contains the VisitInfo metadata structure (see DM-5503). I will provide a specific weekly to in the reprocessing in a comment."
Answer: 1248342.0

User story: "Once the {{meas_algorithms}} background model is being generated correctly, the original {{pipe_tasks}} test that first pointed to this problem in needs to be put back to higher precision. A comment in {{testProcessCcd.py}} indicates the assertions that should have their precisions lowered back to pre-py3-porting values. Presently, this test fails with lower thresholds because the background model is different than expected."
Answer: 163426.0

User story: "This new {{meas_algorithms}} test should verify that we are generating the background model we think we are."
Answer: 155292.0

User story: "The background model pixel values differ by 0.00011 ± 0.00035 on average in python2 versus python3. The cause of this discrepancy needs to be tracked down and fixed."
Answer: 161232.0

User story: "A utility class is needed to upload the unit testing data file in firefly_test_data tree."
Answer: 2889.0

User story: "The eimage dataset type is special to obs_lsstSim so was not updated in the process of implementing the VisitInfo ticket."
Answer: 21304.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: "Minor fixes for gcc 6.2 compatibility"
Answer: 2681.0

User story: "Following the constructive contact with the Jupyter team by <USER> pick up the thread and get in touch.  * Bring this issue up with DMLT  * Come up with a plan for actions needed with pros and cons  * Estimate the effort needed and benefit gained  * Decide whether to pursue it or not "
Answer: 1702545.0

User story: "Generate Metadata stream #2 as a mock OCS telemetry publisher and receive it with a bridge component and parse it, then translate it into DM internal messaging format."
Answer: 20118.0

User story: "Write a short document or set of notes describing the short-to-mid term scientific goals for the deblender. Which types of target are a priority? Which can we safely ignore for now (or, indeed, forever)?    In addition to discussion with the regular stakeholders, it might be appropriate to have an LSST [RFD|https://developer.lsst.io/processes/decision_process.html] and/or to meet with other interested parties in the astronomical community (e.g. the Peyton Hall regulars) to ensure these goals are the product of broad consensus."
Answer: 59160.0

User story: "We've now added the SDSS anti-shredding code to the deblender (DM-4550) and enabled consistent removal of peaks in multi-band. Check if this has been a net win. Identify:    - Objects which were getting shredded before but are now ok;  - Outstanding failures which *should* be ok, but still aren't.    In particular, check whether the centre of clusters is ok."
Answer: 69505.0

User story: "in composite datasets, sometimes the composite objects wants a component dataset that is a list generated by a call to butler.subset. (this is to implement this keyword and passing to the assembler)"
Answer: 40419.0

User story: "write default assembler & disassembler for composite objects"
Answer: 36069.0

User story: {quote}  <USER>\[7:32 PM\]    obs_subaru seems to be broken in master (when building product ci_hsc). see https://ci.lsst.codes/job/stack-os-matrix/17335/label=centos-7,python=py2/consoleFull …it seems to be throwing an exception and then failing in the handler because of an uninitialized var:  7/python/py2/lsstsw/stack/Linux64/obs_subaru/12.1-3-g0ef1cd8+22/python/lsst/obs/subaru/crosstalk.py", line 277, in subtractXTalk  :::::  [2016-10-17T21:32:22.663760Z]     msk.removeAndClearMaskPlane(tempStr, True) # added in afw #1853  :::::  [2016-10-17T21:32:22.663792Z] UnboundLocalError: local variable 'msk' referenced before assignment  from git blame, it looks like the error is related to changes made by @paulprice in August, tho I don’t know why it’s only now throwing an error that causes it to go into the ‘finally’ block.  {quote}    The {{msk}} isn't set until deep in the {{try}} block, which makes the code fragile.
Answer: 1138.0

User story: "datasets should not be written to disk if the policy marks the dataset as input only."
Answer: 41768.0

User story: "Merge in latest changes from upstream XRootD (includes gcc 6.2 fixes)"
Answer: 44.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 ticket is for the work to retrieve data in DAX.   With proper URI and query str, the correct data in the meta server, data server and image server will be located. Return a IpacTable for the meta and data search and return an image for the image search."
Answer: 30200.0

User story: "[~<USER> and [~<USER> pointed out that the stack is too chatty here:   {code:java}  reduceArc.py $PFS_DATA_DIR --rerun $whoami/talk --id visit=4 --clobber-versions  root INFO: Config override file does not exist: '/Users/<USER>LSST/obs/pfs/config/reduceArcTask.py'  root INFO: Config override file does not exist: '/Users/<USER>LSST/obs/pfs/config/pfs/reduceArcTask.py'  root INFO: input=/Users/<USER>PFS/Data  root INFO: calib=None  root INFO: output=/Users/<USER>PFS/Data/rerun/<USER>talk  CameraMapper INFO: Loading registry registry from /Users/<USER>PFS/Data/rerun/<USER>talk/_parent/registry.sqlite3  CameraMapper INFO: Loading calibRegistry registry from /Users/<USER>PFS/Data/CALIB/calibRegistry.sqlite3  {code}    and we should consider changing most of the above lines to DEBUG level. "
Answer: 5700.0

User story: "VisitInfo.h should have been added to the {{afw/image/image.h}}, but was not."
Answer: 1100.0

User story: "Make the   {{firefly_client}} Python API installable via pip. The package will be named {{firefly_client}}. The package will exist within the {{firefly}} repository.    copied from the pul request: (XW, 1018/2016)  copied Firefly License.txt  added a simple README  added setup.py and setup.cfg  moved package files to firefly_client directory  "
Answer: 2957.0

User story: "Add 2D Chart to client side phase folding dialog.  The chart should update as the user moves the slider.    copied from the github:  (Nov. 15, 2016 XW)  The implementation mainly,    add 2D chart on the client side phase folding dialog and the plot changes as any of the phase folding parameters (time column, flux column, zero time point, period) changes.  update the parameter items in the parameter setting dialog.  Test:    localhost:8080/firefly/lc.html  open 'lc_raw.tbl' from 'Raw Table', click 'search'  select tab 'Upload/Phase folding' and click button 'Phase Folding'  experiment the setting of all entries and move slider to set 'period', the plot will be updated as any of the parameter (except Flux error column) changes  click button 'Phase Folded Table' to close the dialog and a table with phase column is created (or updated) based on current setting of period, time column and zero point time.  Note:    The time and flux column names are set in default for IRSA cases. Those column names are settable while the phase folding dialog component is used."
Answer: 44662.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: Do the following with phase folding:    # Move Algorithm to the client side  # Make a dialog to modify phase folding parameters  # When Ok is push replace the existing phase folded table with new generated phase folded table  # Find a react slider that when can use as part of the system and use it for the period field. Connect the slider to our FieldGroup components.  # Work with [~<USER> to understand what it will take to put a chart in the dialog to show the 'test phase folded table".  It the next ticket you will put the chart in the dialog.    A couple of places to look for sliders:   - https://github.com/brillout/awesome-react-components   - https://github.com/enaqx/awesome-react
Answer: 30509.0

User story: "h1. The rationale    A possible workflow for loading a large catalog into Qserv may require various forms of parallelism both at the data preparation stage and when performing the actual loading. This opens a possibility that the actual data loaded stage may be operating on fragments of the same chunk spread between multiple input files. The current implementation of the database loading procedure is not safe to operate in the input data structured in this way. Neither it would work for subsequent loading fragments of the same chunk. There are two failure modes which would prevent the current procedure from succeeding:  * *chunk-to-worker node mapping*: each instance of the loading script will try to follow its own _round-robin_ allocation sequence of worker nodes for chunks as they (the chunks) are discovered in an input folder. Since no coordination has been employed so far between multiple instances of the loading script two instances may try to allocate different worker nodes for the same chunk. This would be a problem when an input data contains chunks split into fragments.  * *chunk creation*: the current implementation of the loading script is based on an assumption that the loading is always made on a fresh (empty) instance of Qserv. As a result of this the script won't check if a chunk structure already exists on the corresponding worker node. This may cause the script to fail when attempting to add more data to an existing chunk.    h1. The proposed solution    A solution to the *chunk-to-worker node mapping* problem would be to pre-populate the CSS database with the mapping before loading any chunks into Qserv.    A solution to the second problem (of the *chunk creation*) is to reinforce the implementation of the loading procedure to detect an existence of a chunk on a worker node and not to fail if the one already exists (was created earlier by some other instance of the loader run either in parallel or before this one).  "
Answer: 66161.0

User story: "  -  way to filter IRSA catalog master list: Gia on top of catalog list  -  Zoom to selection  -  then catalog panel do selection viewport corners  "
Answer: 10451.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: "(Apologies if I'm missing an existing ticket for this; there doesn't seem to be an exactly on-point one, though DM-7990 covers some of it.)    The SUIT portal for PDACv1, the main focus of which is the service of the forced photometry data from SDSS Stripe82 (LSST 2013 processing), needs to be able to deal with multi-band photometry data in a table in which data from all five SDSS filter bands (_u, g, r, i, z_) are mixed together as separate rows in the same table.    It is a minimal requirement to be able to display the data for a single selected filter band, and this should be able to be done in a more natural way than requiring the user to enter a filtering expression in the {{filterId}} column.    As noted in DM-7990, the next step would be the ability to show the light curves for multiple filter bands over-plotted on each other."
Answer: 331125.0

User story: " fix circles connecting & add way to reorder image tabs.  Most of this ticket has the code to reorder the images tabs in the image select panel  "
Answer: 1288.0

User story: "Migration of scientific datasets to butler repository structure per RFC-95."
Answer: 71958.0

User story: "Design/implement and test Workflow for data transformation required for nominated migrated scientific datasets."
Answer: 70334.0

User story: "Identifying project-valued scientific datasets for migration which includes project team deep dive into dataset retention polices"
Answer: 17326.0

User story: "Assess Spectrum Scale (formerly GPFS) efficiency for offered services."
Answer: 70337.0

User story: "Investigate how to use the stack with Pegasus, and use stack tasks (which can be example tasks or even fake tasks) as componenets of an abstract workflow to create a Pegasus dag."
Answer: 25804.0

User story: "lsst-wcslib fail on CentOS 5.11. This failure is similar to DM-7774 and is fixed through the same method.    See yet another VERY long log:    https://gist.github.com/<USER>7f6d494aded772ac776ecb7abf09f9f8"
Answer: 25317.0

User story: "butler can take a URI or relative path for it's inputs and outputs arguments, provided that it has a way to figure out what the details of the repo are, e.g. mapper, and provided the default mode (inputs 'r', outputs 'w') is acceptable.  this needs to be documented in the butler init function. and a formal test written."
Answer: 60433.0

User story: "Rebuild the docker image used to create Conda Linux binaries using ContinuumIO's base docker image. Add lsstsw for testing and debugging purposes.  "
Answer: 41747.0

User story: "There is extensive documentation in Confluence on how to use orca and conda for pipelines orchestration:    https://confluence.lsstcorp.org/display/DM/Orchestration    Being user guides, these need to be migrated to DM's user guides. LSST/NCSA-specific material can go into https://developer.lsst.io (https://github.com/lsst-dm/dm_dev_guide) while material associated more with pipelines code should go into https://pipelines.lsst.io (https://github.com/lsst/pipelines_docs)."
Answer: 283601.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: "Tests in {{DateTime}} depend on specific behaviour of {{enum}} that pybind11 does not support. These tests are hence (temporarily) disabled in {{DM-6168}}.  Deficiencies (or features) of the current upstream enum support are:    * enums are unordered (they have no less-than operator)  * enums (even unscoped ones) are not implicitly convertible to their underlying type    The latter property is sometimes desirable because it automatically prevents enums of different types to be interchanged in a call.  However, we do seem to have some code that depends on implicit convertibility (I would argue that we should use scoped enums more in general, but that is a separate matter).    This ticket aims to bring pybind11 enum support more in-line with the expected behaviour from C++."
Answer: 50406.0

User story: Decam has at least one new filter ("VR") that we do not have defined in the obs_decam mapper. This needs to be added, and it would be best to preemptively find any other new filters they have and add them too.
Answer: 1361.0

User story: "Due to the expressed end-user interest in fairly complex jenkins build notification behavior, [~<USER> and I have been discussing the option of handling this entirely external to jenkins, rather than trying to encode custom logic inside a plugin.  This would require shipping build status notifications to an external service which in turn makes notification decisions and pushes message(s) to slack."
Answer: 686498.0

User story: "Using either Piff or Roodman's donut_lib tools, characterize DECam PSFs, reproducing Roodman's results, at least for a subset of available images.  (Possibly presented here: https://spie.org/Publications/Proceedings/Paper/10.1117/12.2233366?origin_id=x4325&start_volume_number=9900 ?  (paywalled.))"
Answer: 404395.0

User story: The default {{TaskRunner.\_\_call\_\_}} [sets the log|https://github.com/lsst/pipe_base/blob/master/python/lsst/pipe/base/cmdLineTask.py#L337-L340] MDC ("Mapped Diagnostic Context" --- a key/value pair) for some special cases of argument lists ({{dataRef}} or list of {{dataRef}} is first argument), but the {{CalibTaskRunner.\_\_call\_\_}} doesn't delegate to its parent class and doesn't set the MDC.  Please modify {{CalibTaskRunner.\_\_call\_\_}} to set the MDC to something appropriate.  Alternatively, the MDC could be set in {{CalibTask.scatterProcess}}.  I don't think we have precedent for setting the MDC in a {{BatchPoolTask}}, so some thought might be required.
Answer: 1843523.0

User story: "Get tools compiled and running.  Compare with GalSim output both in terms of speed and accuracy.  Determine if these tools should be incorporated directly into Piff or not."
Answer: 58956.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-7900 introduced {{\-\-batch-type=none}}, which disables all MPI by calling {{Task.parseAndRun()}} directly.  However, various features which are included in the batch version (through {{BatchCmdLineTask.batchCommand}}) are not activated:  * Log setup (no {{lsst.ctrl.pool.log.jobLog(jobName);}}).  * Stats (from {{\-\-batch-stats}}).  * Profiling (from {{\-\-batch-profile}})."
Answer: 1843578.0

User story: "On recommendation from [~<USER>, I'm writing a short technote describing how to rename an LSST package, based on my experience from DM-7915."
Answer: 1772.0

User story: "As per RFC-193 add the starlink AST package. Name it {{starlink_ast}}.    Note: until we have the new WCS code further along it seems premature to add {{starlink_ast}} to {{lsst_distrib}}"
Answer: 1500.0

User story: Solve "WARNING: Usage of loopback devices is strongly discouraged for production use."    Additional informations are available in:  "https://jira.ncsa.illinois.edu/browse/LSST-785"
Answer: 1793903.0

User story: "Now that the package move/rename in DM-7915 has been finished, can we please get the daf_butlerUtils component renamed to obs_base to match?"
Answer: 21311.0

User story: Now that the daf_butlerUtils -> obs_base move is complete, we need to move obs_base to live in the lsst organization (it's currently in lsst-dm). github provides a "transfer repository" mechanism:    https://help.github.com/articles/transferring-a-repository-owned-by-your-organization/    but we can't use that until we've deleted daf_butlerUtils since obs_base is a fork (github gives the following error: "lsst already has a repository in the lsst/daf_butlerUtils network"). Once we're sure there are no more outstanding daf_butlerUtils branches, we can delete that repo (and thus break the fork link) and move obs_base to lsst and update repos.yaml. This shouldn't break Jenkins at all, as github does redirects when a repository is transferred.    I plan to do this at the beginning of November.
Answer: 55143.0

User story: This is one of series unit test ticket for package "package edu.caltech.ipac.visualize.plot".
Answer: 123875.0

User story: This class is in the package "edu.caltech.ipac.visualize.plot".  The unit test should be added to almost all the classes in the package.     This is one of the series of unit test tickets.
Answer: 182724.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: "Create a self-consistent subset of the large Stripe82 catalog and relevant image files (in the FITS format) in order to test SUIT implementations. The subset will cover 100% of the SDSS patch *366,0* in an area processed at NCSA:  *   9.50 <  RA  <  9.25  *  -1.00 < DECL < -1.25    The catalog should include:  * deep coads along with the relevant metadata  * objects detected on the coadds  * forced sources detected on calexps at the locations around the relevant objects  * calexps on which the sources were detected, as well as the relevant metadata tables (for calexps)    The database catalog will be placed at a MySQL/MariaDB server:  * host name: *lsst-db.ncsa.illinois.edu*  * database name:  *<USER>sdss_stripe92_patch366_0*    An image repository with FITS referenced by the corresponding catalog tables:  * coadds  * calexps"
Answer: 90.0

User story: "When running without a batch system, uncaught exceptions still cause a call to mpi.COMM_WORLD.Abort() which is confusing.  "
Answer: 1085.0

User story: "There's code in pex.config.history to colour output, but it's en/disabled unconditionally.  Please change it to never colour text that isn't going to the terminal.  "
Answer: 309.0

User story: "Qserv master on PDAC has been re-install from scratch for security reasons:  https://jira.ncsa.illinois.edu/browse/LSST-801    Qserv needs to be re-installed and re-tested here once master node will be available."
Answer: 23778.0

User story: "Add Gaussian Process to Piff to figure out how that part of the package works."
Answer: 138006.0

User story: "Add a Kolmogorov PSF model to Piff in order to figure out how this part of the code works."
Answer: 69560.0

User story: "Once the new {{FitSipDistortionTask}} introduced on DM-3549 has been fully vetted, it should be set as the default.  The task it replaces ({{FitTanSipWcsTask}}) and the C++ code it uses (namespace {{meas::astrom::sip}}) should then be removed."
Answer: 1849455.0

User story: "This refactors {{validate_drp}} to use the {{validate_base}} API (DM-7042).    Main features are:    # All JSON serialization code is now in {{validate_base}}; {{validate_drp}} exclusively uses that API.  # The {{validate_base}} API is slightly different from the version originally included in {{validate_drp}}. A significant change is the use of astropy quantities for serialized measurements.  # Refactored {{utility}} module to make it easier to follow computations. Functions directly associated with a measurement are included in that measurement's module. The calculations themselves are refactored into function independent of the measurement classes, again, to make it easier to follow the calculation.    Other features:    - pytest compatibility in tests  - summary pass/fail printout based on the {{--level}} argument  - remove unused functions  - improved documentation in the README"
Answer: 77820.0

User story: "Begin implementation of the components of NCSA Level 1 services monitoring."
Answer: 44927.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "In wdb/ResourceChunk.h reference counting occurs above the subchunck table level. It is probably worth it to trace the subchunck logic back to the czar, document it, and determine if it is adequate beyond the LSST schema use case. If needed, reference counting should be moved so there is one reference count per table."
Answer: 9910.0

User story: "Get a set of images to test the prototype pipeline on. Decide on the scope of the images (how many/which ones), copy/download them, ingest them, and do the same for the appropriate calibration products."
Answer: 139955.0

User story: "Identify which pieces of the AP system to link together. This also requires choosing a dataset on which to test the pipeline which necessitates each of those pieces.    Questions to consider: Will the pipeline do ISR? (Almost certainly yes.) Will it make a coadd template or just use science images as templates? What will it do with the identified set of sources (association)?"
Answer: 138569.0

User story: "Multiple series histogram display (not connected to table)    Show how multiple histogram series can be displayed. Display multiple histogram data in an API.    (This is needed to understand how to organize multiple series data)"
Answer: 2577.0

User story: "Refactor charts store to allow multiple data elements.  Generalize chart actions to work with any kind of chart data or chart parameters.     Example: histogram point is described by the number of bins, min and max, scatter plot point is described by x and y, etc.  For each chart data type we have a way to fetch the data, based on some parameters. But we want chart actions to be independent of chart type or chart data type: CHART_ADD, CHART_DATA_FETCH, CHART_DATA_UPDATE, CHART_OPTIONS_UPDATE, etc.    The implementation might be based on a simplified version of   https://confluence.lsstcorp.org/display/DM/Firefly+chart+design  Implementation notes:    Refactored chart actions and data to be able to support multiple chart elements connected to different data.    charts.data - is the store object with chart ids as the keys, the values are chart data object, which has chartDataElements field.    chartDataElements - object with chartDataElementId keys  and chartDataElement object as value    chartDataElement shape:  {id, options, defaultOptions, data, meta, tblId,  type - to get helper functions like  chartDataElements - object with chartDataElementId keys  and chartDataElement object as value    chartDataElement shape:  {id, options, defaultOptions, data, meta, tblId, type}  The 'type' is an id of a ChartDataType, two of them are predefined: 'xycols' and 'histogram'.  Each chart data type has fetchData function and fetchParamsChanged functions, and possibly other helper functions.  "
Answer: 11534.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: "Include in the Developer Guide a recommendation to set    {code}  [push]  default = simple  {code}    to defend against force-pushing with pre-v2.0 versions of Git. See https://community.lsst.org/t/the-dangers-of-git-on-lsst-dev/1216?u=<USER>for reference.    This will be moot once RFC-121 is *implemented*."
Answer: 163.0

User story: "The DRP data flow diagram (https://confluence.lsstcorp.org/display/~<USER>DRP+Data+Flow ) from early May (DM-6098) has become outdated from the new changes. Update it. "
Answer: 1546.0

User story: "This is the implementation ticket for RFC-230. I believe the work required to be as follows:    # delete newly-created obs_base package from github.  # change daf_butlerUtils->obs_base in all table files that reference it.  # change all {{lsst.daf.butlerUtils}}->{{lsst.obs.base}}  # rename github product from daf_butlerUtils->obs_base  # replace daf_butlerUtils in repos.yaml with obs_base and it's github link    If there are any extra steps I'm missing, please add them below. This may be briefly disruptive to jenkins (we cannot test the renames until the package is renamed, but that can't be done on a branch). If we've ever done a package rename like this before, I'd be interested in seeing a link for anything else I may have missed.    I want to take care of this ASAP, so I can move the new testing code that had been pushed to the obs_base repo I created, into the package to-be-formerly-known-as-daf_butlerUtils."
Answer: 7070.0

User story: "Three things need to happen:     -  I want to change plotId the data structure to itemId   -  there are a couple of utilities function that are specific to images but I don’t think that matters   -  I want to add a type for each viewer"
Answer: 2800.0

User story: "Emergent and System work for supporting the Chilean ITC Tiger Team."
Answer: 86711.0

User story: "Initial work to identify use cases and technical demarcations, and trace service catalog through layered service architecture. Prototyped schema for articulating logical design and service mapping in Enterprise Architect. Coordinated with Jeff K on EA articulation for best practices use of tool and so that our modeling will integrate with Chilean ITC Tiger Team modeling."
Answer: 43144.0

User story: "Operations planning and prep for November review:  * Non-labor costs  * Add to and refine conops  * Early ops FTE ramp  * Refine WBS  * DPP-specific review material  "
Answer: 43138.0

User story: "Participate in Operations Planning Review for DPP."
Answer: 86715.0