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: "This is a bug introduced by in DM-8367 line chart. The precision of the expression columns is not set when the values are saved to an IPAC table. When the table is read back and the first row happens to be 0.0, all values will be passed to the client with 1 decimal digit.    Test: load sample table, change y column to -count/time. Notice that all values in the point tooltip have 1 digit after decimal point and that highlighted points do not match the points on the line. (Highlighted values are calculated on client from the values of the table, plot points - on the server.)    https://github.com/Caltech-IPAC/firefly/pull/279"
Answer: 7681.0

User story: "Expect to field responses from candidates and finalize hiring this month."
Answer: 40326.0

User story: "Includes time for scheduling & preparing for interviews, communicating with candidates, answering questions, etc."
Answer: 1.0

User story: This example, in {{$IP_ISR_DIR/examples}}, is not running with {{w_2017_5}}, and currently exits with the error below (tested on py 2 [by me] and 3 [by Josh] ).      {code}  Traceback (most recent call last):    File "runIsrTask.py", line 50, in <module>      exposure = runIsr()    File "runIsrTask.py", line 33, in runIsr      output = isrTask.run(rawExposure, dark=darkExposure, flat=flatExposure)    File "/tigress/HSC/LSST/stack_20160915/Linux64/pipe_base/12.1-5-g06c326c+5/python/lsst/pipe/base/timer.py", line 121, in wrapper      res = func(self, *args, **keyArgs)    File "/tigress/HSC/LSST/stack_20160915/Linux64/ip_isr/12.1-5-g9b15cd5+7/python/lsst/ip/isr/isrTask.py", line 464, in run      raise RuntimeError("Must supply a linearizer if config.doBias True")  RuntimeError: Must supply a linearizer if config.doBias True  {code}
Answer: 1815535.0

User story: With a new Calib object to contain the fit results and a better understanding of the meas_mosaic model, implement a better photometric model in jointcal. This should not be a "final" model (e.g. full focal plane/multi-component), but rather a "better enough" model (e.g 2d 3rd-order chebyshev per ccd). The model should be good enough to replace meas_mosaic's fit.
Answer: 362810.0

User story: "In preparation for implementing a better photometric fitter in jointcal, we need to investigate the photometric model used by meas_mosaic. That should help guide the implementation of the new jointcal model and possibly the new Calib interface."
Answer: 29864.0

User story: "Jointcal needs to fit a more complicated photometric model in order to be able to replace meas_mosaic. In order to do so, we need a better Calib object to hold the results of such a fit. This design will go into an RFC."
Answer: 10184.0

User story: "This ticket is for the implementation of the BoundedField-based Calib redesign that will be proposed in an upcoming RFC. The details of the design will be given below once they are settled."
Answer: 125110.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: "Use the checklist from DM-9182 to clean up code in all packages not covered by DM-9182 or DM-9188.  Most work will probably be ip_diffim and meas_modelfit, as most other packages have relatively little wrapped C++."
Answer: 93581.0

User story: "When ingestImages.py is run, a series of filesystem links are created pointing from the data repo to raw image files.  If the raw image files are subsequently compressed (e.g., gzipped), then the links no longer point to the data.  This is despite the fact that the Butler would perfectly happy to read the gzipped files.    This ticket is to extend the Butler search routine so that if a link pointing to foo.fits can not be resolved to a file, then foo.fits.gz is tried as a fall back.  Presumably other common compression extensions could also be checked (foo.fits.bz2, foo.fz) (though my use case at the moment is just .gz).    Also, if someone with more experience in this area wants to come and clean up my very non-expert description in this ticket, please do!"
Answer: 1795231.0

User story: "Use the checklist from DM-9182 to clean up code in the packages listed in the components field.    Unlike DM-9182, I have not reviewed these packages for specific issues in advance; now that the common problems have been identified it'll be easier to review and fix at the same time."
Answer: 44511.0

User story: "Jointcal's python interface is currently SWIG-based. Now that most (all?) of the dependencies are converted, it's time to convert jointcal to pybind11."
Answer: 64569.0

User story: "I have some unusual data (HSC pinhole filter images) for which I'd like to run only very basic Isr tasks (overscan subtraction and bias subtraction), which is tricky to manage with processCcd.py.  This ticket is to create a subaruIsr.py command line executable to accomplish this."
Answer: 1430.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: Following the review of DM-9063, I've put together a list of fixes to make for most of afw and its dependencies, which I have attached to the ticket.  I have *not* looked at afw::table, as that will be reviewed and fixed independently on DM-8716.    First, a list of *generic* issues that weren't worth capturing on a file-by-file basis (though I did start by doing that).  This is essentially a checklist that should be used by all pybind11 cleanup issues:  - Move trivial Python extensions to C++.  - Use continueClass decorator in remaining Python files.  - Reorganize/rename files as per RFC.  - Address any TODOs  - Remove commented-out headers.  - Make sure pybind11 header is included first (because Python.h needs to be included first).  - Remove (or otherwise address) commented-out code  - Remove any use of ndarray/converters.h (redundant with ndarray/pybind11.h)  - Make sure all functions that should have kwargs do.  - Replace py::arg("foo") with "foo"_a (with using pybind11::literals)  - Make sure shared_ptr holder type is used for all but trivial classes  - Look for comment headings that are unused or disrupt readability  - Make sure {{py::is_operator}} is used on binary, non-in-place operators, and is not used anywhere else.  - Look for lambdas with non-const reference arguments; could they be const references?  - Look for getters that should be using reference_internal  - Remove spurious (empty) wrapper files.  - Determine whether enums are used as enums or integer constants, and adjust wrappers accordingly.  - Check for anonymous namespace and `static` usage.  - Check for worthless module docstrings.  - Define typedefs for py::class_ instantiations, or otherwise ensure they're not repeated.  - Don't use ::Ptr (here, or anywhere).  - Run clang-format?  Some of indentation is really terrible at definitely not conformant, and clang-format improves it.  - Delete trailing whitespace.    
Answer: 50475.0

User story: "Review astshim to see if it is suitable to use as the basis of WCS and transforms for the LSST stack.    I think it is ready, other than one known annoyance: when an error occurs a message is printed to stderr (I think) and then an exception is raised. I hope at some point to figure out how to redirect the error message(s) to become the text of the exception. Meanwhile things work, but the unwanted printout is a nuisance and the exception messages could be better."
Answer: 656938.0

User story: "Read up on:    - Proximal operators  - [~<USER>'s deblending code"
Answer: 12801.0

User story: "Produce test cases for deblender operation on simulated data, including:    - Correctness of SED;  - Overall flux;  - Degenerate templates.    This should include comparison against the current LSST deblender as a baseline."
Answer: 79143.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> will supply a pseudocode algorithm for this (which either he or [~<USER> will make available on this ticket).    Code will take in the peaks, constructs symmetry matrices, construct monotonicty matrices, apply constraints as appropriate, make these available to the proximal operators. This ticket includes defining the interfaces by which that information will be made available to the proximal operators, but not implementing those operators themselves, which are created in DM-9143 (monotonicity), DM-8959 (symmetry) and DM-9170 (PSF convolution)."
Answer: 79047.0

User story: "[~<USER> will supply the 1D version of this.    Work should be done based on a PSF image supplied by the stack."
Answer: 69262.0

User story: "Provide high stellar density fields for deblender testing."
Answer: 43200.0

User story: "Identify deblender test cases in PSF matched coadds from HSC (as provided by DM-9035) which include:    - Line of sight projections as blends, where colour information is available;  - Cluster cores, where colour information is not helpful;  - Large extended galaxies with internal structure in blends;  - Extreme colour artefacts."
Answer: 38823.0

User story: "This ticket captures the changes needed in SQUASH during implementation of DM-9034.  The metrics api endpoint must accept the upload of multiple itens at once.  pypi jsonfiled 1.0.3 was replaced by django-json-field 0.5.7 because an improper validation error that was preventing the metrics definition upload, see:   https://github.com/bradjasper/django-jsonfield/issues/119"
Answer: 426.0

User story: "Help [~<USER> to load LSST processed data inside Qserv.  "
Answer: 325384.0

User story: "The old firefly's API 'addCoveragePlot' will overlay the coverage image with the searched position given by the 'OverlayPosition' parameter.  This feature is missing from the new showCoverage function.  Also, catalog search results should also have the searched position overlaid as well.  Please confirm."
Answer: 15439.0

User story: "Need to add links to point to documentation.  Mock up here:  http://web.ipac.caltech.edu/staff/<USER>working/tsvdocs/helpplacement/"
Answer: 43065.0

User story: "The preview phase folded curve in the period finding layout is showing the magnitude axis in increase order but it should be in decrease order as the result layout to be consistent."
Answer: 35586.0

User story: "{{PeakCatalog}} has an ID field and so probably ought to be a sorted catalog (inherit from {{SortedCatalogT}})."
Answer: 2.0

User story: "An investigation into the possibility of 'runtime working directory recovery'  (for forensics purposes in the event of error)  by Pegasus workflows was initiated.  A goal is to determine whether Pegasus middleware can support such a mechanism, or whether lsst data backbone or process middleware would need to attempt this support.  [ This is listed in this epic with the lack of data backbone emergent work epic.] "
Answer: 9.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: "Compile & distributed (e.g. to CLO) notes describing the user-visible changes in the pybind11 port."
Answer: 51945.0

User story: "We should add metadata readers with object constructors as per DM-9060 for a few more Exposure components:     - {{filter}}: {{afw.image.Filter}} has a {{PropertyList}} constructor, so the exact same pattern used for {{Calib}}, {{Wcs}}, and {{VisitInfo}} ought to work.  There's also a {{CameraMapper._setFilter}} method that seems to provide some sort of fall-back implementation; I'm not sure how that gets invoked.     - {{bbox}}: All the information we need to construct an {{afw.geom.Box2I}} is in the metadata {{PropertyList}}, but there's no existing function to create one from a {{PropertyList}}, and in this case there it wouldn't be appropriate to add it as a constructor, I think.  We should add a free function to do this to {{afw::geom}} (in Python would probably be fine).  We can get width and height from the {{NAXIS1}} and {{NAXIS2}} keys, respectively, and the minimum point from {{lsst.afw.image.getImageXY0FromMetadata}}.     - {{detector}}:  CameraMapper already does some magic to attach a {{Detector}} object to many {{Exposure}} datasets.  I'm not sure what invokes it, but the relevant implementation for calexp seems to be in {{CameraMapper._setCcdDetector}}; there's at least one other implementation for other {{Exposure}} datasets that correspond to an amplifier rather than a CCD, and there are also some {{Exposure}} datasets for which there is no detector.  Ideally we'd like to have {{<dataset>_detector}} do the same thing as the code that attaches all of those to full-Exposure loads, but the priority is probably getting calexp_detector working.    "
Answer: 252129.0

User story: "The configuration of the GPFS system at NCSA seems to waste a lot of space relative to the NFS configuration.  This is possibly due to a difference in block size showing up when many small files are in the file system.  In my experience this is a fairly common problem.  The stack has lots of small files and the reduction system produces many small files.    I don't have anything very concrete, but the anecdotal evidence is that my {{/home}} took up 571GB on NFS, but is > 1TB on the GPFS system (I ran out of disk quota so don't have an exact number)."
Answer: 91916.0

User story: "Make sure actual full archive copy transfers without error. Correct invalid design assumptions."
Answer: 34641.0

User story: "Integrate GSISSH code into the backup software to authenticate with Globus using certificates and for creating and monitoring transfer tasks."
Answer: 34645.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 current storage system on GPFS at NCSA isn't set up in a way that supports a common pattern in the project.    As I understand it, the current system is set up to support some amount (1TB currently) of backed up data in {{/home}}, highly curated data (RFC required to change it) on {{/datasets}} and purely ephemeral storage on {{/scratch}}.    A common pattern is to have data that need not be backed up, but that is not purely ephemeral.  Examples include, test data from algorithmic experiments, results from mini-data challenges, user copies of the stack, datasets that are share among a group (e.g. AP).  These should not reside in {{/home}} or {{/datasets}}, but are not purely ephemeral, so should not be purged.  This use case was handled perfectly by the old NFS mounts at e.g. {{/lsst8}}.    This ticket is to request a system that will support the usage pattern described in the previous paragraph."
Answer: 120726.0

User story: "<USER>and <USER>(NAOJ) have put together a sky subtraction code (based on the HSC pipeline) that performs better for large objects than what we are currently using.  Their approach creates sky frames from many observations and subtracts these from the data, with additional large-scale subtraction to deal with any small residuals.  I need to:  1. Understand the details of the approach taken.  2. RFC this addition to the processing.  3. Implement the code on the LSST side.    Their code is on the [{{koike/global-sky-subtraction}} branch of hscPipe|https://github.com/HyperSuprime-Cam/hscPipe/tree/koike/global-sky-subtraction]."
Answer: 416191.0

User story: "Several key aspects (3) identified here within in regard to the API documentation in imgserv (applicability to other DAX services to be considered):    1. The API definitions, functions, and associated workflows  should follow closely if not precisely the guidelines in the SIA IVOA recommendation.    2.  The official technical documentation needs to reflect the current state of the API implementation and versioning, through following the Sphinx guide in LSST, in same  spirit as in the documentation for numPy.    3. Implemented APIs should support an introspection (or discovery) mechanism for the user to query status/availability and the metadata of the current version, via 'root' method.  Each method upon query to provide function signature and example(s) of usage.    #1 - 3 above likely prove to be too wide of a scope for a single implementation task, so an iterative implementation approach is to be expected, particularly when applying the same solutions outlined here to other DAX services.    Thanks to <USER>for supplying lots of the context, input, and content for this ticket.   (any omissions/errors are mine)                "
Answer: 217730.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 most prominent failure case of the NMF deblending algorithm (see DM-8959) is when two or more objects have similar colors. The most likely way to solve this problem is to create an operator that penalizes peaks whose intensity profile is non-monotonic.    This involves modifying code provided by [~<USER>."
Answer: 14446.0

User story: *This story is about fixing the requested periodogram to IRSA API so we probably need to add a validator to the input field and each option should have a corresponding label.*    Lately, i've noticed that when doing a periodogram from both part of the dev version of LC, one (from the 'period finding' layout) is behaving differently than the other (from the old tab panel). The result is different.     I've found that in the 'Period finder' layout, the periodogram panel option has a 'step size' value not empty, set to 0.3 (i think this is coming from the cutout size field!) which overwrite the default empty value and in some cases it fails (if 'exponential' option is selected).    Actually, the 'step method' option is associated to different input meanings (not always 'fixed step size') and valid ranges.    Taking the mapping from NExSci, when 'step_method' is {{X}}, then label should say {{Y}}, with range valid [ ] and default value {{D}}, such as:    - {{X}}: Fixed Frequency, {{Y}}: Fixed Step Size, [ > 0.0000001 ] , {{D}}: ?  - {{X}}: Fixed Period, {{Y}}: Fixed Step Size, [ >  0.0000001 ], {{D}}: ?  - {{X}}: Exponential, {{Y}}: Oversample, [ 1, 1000 ], {{D}}: ?  - {{X}}: Plavchan, {{Y}}: Period Step Factor, [ > 0.001 ], {{D}}: ?    Default value for fixed period and frequency COULD come from a calculation on the original table that we are currently missing and would need to be specified in a different ticket because that involves an intermediate calculation on the original table that is currently missing.     For now, i would suggest to leave blank the field and no validation. Just make the labels meaningful with the step method option selected.    We need to get feedback on how to use the IRSA API about default values.  Need input at least from [~<USER>, [~<USER> and Angela Zhang <<EMAIL>> ).    For the ticket, do the following (approved by Luisa/Vandana/Harry/Steve):    1. Remove exponential and plavchan    2. Leave blank input fields and add a note to the UI panel that says "Leave the following fields blank to use default values", followed by a context-sensitive help link to the documentation that contains the formulae for the defaults (DM-9164)    
Answer: 19931.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: "Our current pybind11 workflow makes it easy to accidentally discard implementations of {{\_\_str\_\_}} and {{\_\_repr\_\_}} that were located in Swig {{.i}} files. While we can (and should) try to transfer these methods to pybind11 as we wrap their classes, we will probably need a dedicated pass through the code base if we want to make sure we haven't missed any.    This ticket is not blocked by [Methods for Stringification|https://community.lsst.org/t/methods-for-stringification/1578/5] or any resulting RFCs, because it concerns only existing code."
Answer: 58948.0

User story: "The automated processing worked fine on January CTIO .9-m run.    Here are some results on the analysis, from satisfying to less satisfying :  1 - The automated processing of the images is fine. A comparison of Ronchi 200 and Ronchi 400 is attached.  The Ronchi 400 enable a better resolution on the bluer lines. But it doe not do so well in the red part. Maybe because of the enhancement of optical distorsions (ronchis.pdf).    2 - Comparison of various attempt to calibrate the telescope throughput :  - Manufacturer spreadsheet  - CBP run 5  - Monochromatic flats run 1  - Template = star SED * model Tatmo    I would say that the background light (high) in the monochromatic attempt and (very high) in the CBP attempt is an issue."
Answer: 7075.0

User story: "While wrapping {{pipe_tasks}} for pybind11, I found a cosmetic bug in which a method's docstring reported some parameter types in C++ style and others in python style:    bq.     1. (self: lsst.meas.base._sdssCentroid.SdssCentroidTransform, inputCatalog: lsst.afw.table._source.SourceCatalog, outputCatalog: lsst.afw.table._base.BaseCatalog, wcs: lsst::afw::image::Wcs, calib: lsst::afw::image::Calib) -> None    The problem was fixed by [importing {{Wcs}} and {{Calib}}|https://github.com/lsst/meas_base/pull/62] before importing the pybind11 wrapper, but I've since seen the same problem in other methods. We should audit the pybind11 wrappers to ensure that their types are always reported in python terms."
Answer: 1920093.0

User story: "Boot from USB, repartition and reinstall ESXi. Reconfigure ssh server and client. Copy backed up VM directories and thin vmdks."
Answer: 18712.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: "Per [LCR-581|https://docushare.lsstcorp.org/docushare/dsweb/Get/Version-37829/LCR-581CalibrationHardwareRequirementsUpdateApproved.pdf]:    {quote}  To be added to LSE-30 (OSS):    Beam Projector Coordinate Relationship    Specification: Coordinate system transformations shall be measured  and/or computed relating the collimated beam projector position and  telescope pupil position to the illumination position on the telescope  optical elements and focal plane, and a software interface shall be  developed to represent these relationships, including their possible  evolution in time.    Justification:    This is necessary to facilitate the data acquisition and reduction. The  user shall be able to specify an LSST pupil and focal plane position for  a given spot, then have the CBP and telescope offset accordingly.  Similarily, the spot positions should be predictable based on the CBP  and telescope position.    This requirement will need to be flowed down appropriately to the Data  Management and Observatory Control System requirements documents. It is  assumed that Data Management will develop a Python interface that  represents the relationships, and that the Observatory Control System  will use those in the construction of the control system functions  relating to the collimated beam projector.  {quote}    Note the requirements on DM above. These should be reflected in LDM-151."
Answer: 92423.0

User story: Jointcal currently uses very non-standard, non-stylistic, and/or non-helpful variable and method names (e.g. {{void FittedStar::SetRefStar(const RefStar *R)}}). I've been cleaning them up piecemeal as I go, but that results in confusing commits and can be a pain. The clang format package provides "clang-rename" which might help take care of most/all of these in one foul swoop. Other suggestions are welcome (SublimeText's smart selection isn't quite smart enough, particularly for single-character variable names).
Answer: 187194.0

User story: "Move the single python script in sgs, fromDbToTruth into the sgsupervised repository and merge it with makeTrainSet.py"
Answer: 30270.0

User story: "The design of astshim is that the objects are thin wrappers around a pointer to an AST object. The initial design had astshim holding these objects by shared_ptr and being freely copyable, but this led to a design that was not const safe, had a constant need to cast objects and was not very idiomatic C++.  "
Answer: 5663.0

User story: "Had a chat with Robert and Zeljko on Thursday Jan 26th, and a few requests for additions and tweaks to the CPP section of LDM-151 came up which were not already included in John's list. These will be done at the same time for efficiency, but it's extra work, so it gets its own ticket."
Answer: 92519.0

User story: "Having applied Robert's first round of corrections, a second marked-up pdf with many few comments exists which should be applied during this iteration on LDM-151."
Answer: 92521.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "After initial system is set up and available, tune configuration based on user needs."
Answer: 15760.0

User story: "Configure the server for external use. Includes general configuration, networking, account creation and communication with user(s), etc."
Answer: 5.0

User story: "[~<USER> reported on slack that the {{qserv:dev}} container is unable to setup the {{qserv}}.    Demonstration of issue:    {code:java}  [master] ~ $ docker run -ti qserv/qserv:dev  qserv@f405e3798cb4:~$ . /qserv/stack/loadLSST.bash   qserv@f405e3798cb4:~$ setup qserv_distrib -t qserv-dev  qserv@f405e3798cb4:~$ eups list -s | egrep ^qserv  qserv_distrib         1.0.0+664   b2666 qserv-dev setup  {code}    Expected result:    {code:java}  [master] ~ $ docker run -ti qserv/qserv:dev  qserv@ab194158b222:~$ . /qserv/stack/loadLSST.bash   qserv@ab194158b222:~$ setup qserv_distrib   qserv@ab194158b222:~$ eups list -s | egrep ^qserv  qserv                 12.1-27-gc42959c  b2531 current b2541 w_2016_51 setup  qserv_distrib         1.0.0+652   b2531 current b2541 w_2016_51 setup  qserv_testdata        12.0+79     current b2541 qserv-dev w_2016_51 b2531 setup  {code}    This appears to be caused by this changed commited on Dec 19th as part of DM-8256:    https://github.com/lsst/lsstsw/commit/49acd3e33364d0b4b67a7900d910fe121a0ac8fb  "
Answer: 4205.0

User story: "In order to test the makeRachelPlots function, a new HSC database dump is required."
Answer: 30143.0

User story: "The DAX team occasionally needs to update the {{qserv_latest}} EUPS distrib tag and {{eupspkg}} s more frequently than the [automated] weekly tag cycle.  This requires chaining together the {{release/run-rebuild}} and {{release/run-publish}} jenkins job, which may not be particularly intuitive to an end user that needs to perform this task on an infrequent basis.    It should be simple to streamline this process by creating a new {{release/build-publish}} jenkins job that chains together the two jobs needed to create new {{eupspkgs}}.  This could be further simplified with a wrapper job that bakes in all the job parameters needed cut a {{qserv_latest}} release."
Answer: 4324.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "I'm finding linking pybind11 modules to be extremely slow on my system (Arch Linux; gcc 6.3).  A -j4 afw build takes approximately two hours, spending the vast majority of its time linking.  This is very much in conflict with [~<USER>'s much faster timing of afw builds, and I can think of two possible reasons why:   - different compiler/linker/OS (I assume [~<USER> was using clang on OS X)   - different optimization (I think [~<USER> was using {{-O0}}, while I was using the default of {{-O3}}).    If the slow part was compiling, I'd be very worried it was the latter, but I don't think optimization level is likely to affect linking much (though I don't know enough about the details of linkers to be sure).  I'm going to run some benchmarks on my machine with clang and with different optimization options, and hopefully on some other linux machines with different versions of gcc.  I may try the new {{gold}} linker, too.    [~<USER>, could you try builds on your system with -O3?  "
Answer: 27764.0

User story: "Change the Python wrapper for astshim from SWIG to pybind11"
Answer: 1301.0

User story: "Various issues arose due to unexpected data volume needs as well as differing storage characteristics. Investigate and propose solution(s). May impact data management policy.  "
Answer: 90632.0

User story: [~<USER> and myself have both observed the jenkins {{run-publish}} job failing on {{qserv_distrib}} since the "move" to lsst-dev01 with this error message:    {code:java}  eups distrib: qserv_testdata is not setup  {code}    Which is quiet odd since {{qserv_testdata}} is masked out in {{manifest.remap}}.  This issue does appear to be reproducible in a docker container:    {code:java}  [root@95058fcddb8a distserver]# publish -b b2646 -t meh qserv_distrib   eupspkg.create: package contents created for 'qserv_distrib-1.0.0+661', sources will be fetched via 'git'.  eups distrib: qserv_testdata is not setup  [root@95058fcddb8a distserver]# publish -b b2646 -t meh qserv_distrib  eupspkg.create: package contents created for 'qserv_distrib-1.0.0+661', sources will be fetched via 'git'.  Adding tag 'meh' at the distribution server.  {code}    
Answer: 75.0

User story: "In the CP MaterCal bias products, the filter in the header can be anything.  Currently the ingest code updates the validity range for each filter, which can result in more than one bias at one time. "
Answer: 314.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 Butler uses {{daf.persistence.ReadProxy}} to support lazy reading, returning these objects in place of things like {{SourceCatalog}} and {{Exposure}}.  In Python, these proxies behave *almost* entirely like their subjects, because they forward all attributes, but they can't be converted to their C++ counterparts through pybind11's type conversion system.  This worked with Swig essentially due to luck: Swig stores its C++ instances in a {{this}} attribute that's publicly accessible from Python, so it automatically invokes the proxy's attribute forwarding when trying to do conversions.    I think there are essentially three approaches to dealing with this in pybind11:   - We could remove {{ReadProxy}} entirely.  A few of us have long been annoyed with them, and we're not yet getting any use out of the lazy loading functionality.  We do anticipate needing lazy loading someday, however, and it looks like an RFC to do this would be more contentious and more work (to design a replacement interface for lazy loading) than I originally anticipated.   - We could live with the conversion failure, making Python code that calls wrapped C++ routines call {{ReadProxy.\_\_subject\_\_}} directly (or via a new convenience function) and making the error message when conversions fail much more helpful (e.g. by changing {{ReadProxy.\_\_repr\_\_}}.  I really don't have a good sense for how much Python we'd have to modify if we take this approach.   - We could add a pybind11 {{type_caster}} that does the dereference for any types that could be proxied.  If it's possible to add a new {{type_caster}} for a class that's already by wrapped with {{pybind11::class_}}, and to delegate within it to the original converters defined by {{pybind11::class\_}}, this will be easy and the course we should take.  I'm hoping [~<USER> knows if it's possible (my best guess is that it is, but it will require using some undocumented and possible internal parts of pybind11).    This ticket is for exploratory work and making a decision (at least with the story points it has now).  It should be updated or a new ticket spawned if we identify an approach that will require significant further work."
Answer: 40521.0

User story: "Ticket DM-5503 made space for rotator information in VisitInfo, but didn't add an implementation, at least for HSC, due to lack of clear documentation.  (See PR comments [here|https://github.com/lsst/obs_subaru/pull/37].)    I have a use case for this information now though - fitting out-of-focus donut images on HSC.  In particular, the fitting model needs to know what the projection of the spider onto the focal plane looks like.  "
Answer: 77662.0

User story: "Investigate the issue discovered in DM-9109, namely the systematic offset between the model psf trace radii (at the single frame processing stage) between the HSC and LSST stacks."
Answer: 8112.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 ellipticity residual comparison and quiver plots in the analysis script, including:    *Intra-stack:*  scatter/histogram/sky plots for *psfUsed* stars of  > residual e1 & e2 ellipticities between the source and model psf at the position of the source (for both SDSS and HSM measurements), where:  {code}  e1 = (shape_xx - shape_yy)/(shape_xx + shape_yy)  e2 = 2*shape_xy/(shape_xx + shape_yy)  {code}  > residual ellipticity, δe, between source and model psf at source position quiver plot where:  {code}  δe = sqrt((e1_src - e1_psf)^2 + (e2_src - e2_psf)^2))  {code}    *Inter-stack:*  scatter/histogram/sky comparison plots for;  > comparison of the trace radii of the sf models at the position of *psfUsed* stars matched between the two stack catalogs, where:  {code}  traceRadius = sqrt(0.5*(shape_xx + shape_yy))  {code}"
Answer: 192481.0

User story: "Include plots showing the distribution of footprint sizes in the analysis script (starting with those coming out of single frame processing).  Check that they look consistent between the HSC and LSST stacks."
Answer: 1301.0

User story: "Check that the isotropic footprint growing/dilation is consistent between stacks."
Answer: 1103.0

User story: "Sqrbot should @-mention whoever invoked it when replying."
Answer: 78.0

User story: "Expand the flatten and unflatten methods of SpanSets such that they can operate on multi-dimensional ndarrays. This work involves making the template parameters for these functions, and the getter classes more generic."
Answer: 9715.0

User story: "In the PUB JIRA system tickets never get into the RESOLVED state. This makes it hard to filter for active tickets and means that default dashboard listings include lots of open tickets that are now dealt with. Please make the GREEN stats in PUB resolved states."
Answer: 7.0

User story: "The FileInfo class was updated and moved to a new location.  It triggered LSSTFileGroupProcessor failing.  The LSSTFileGroupProcessor should be modified to import from the new location."
Answer: 9.0

User story: "The developer guide mentions HipChat in a couple of places. These should be replaced by Slack."
Answer: 269549.0

User story: "This ticket is primarily intended to capture blockers for the final merge of the pybind11 branch to master.  It also includes a bit of effort to account for the final round of rebasing and testing.  "
Answer: 59463.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 intended just to capture blockers for starting a full-stack cleanup of the pybind11 branch prior to merge.  That phase will involve two kinds of work we don't want to start too early:   - *Small*, minimally disruptive changes to existing Python or C++ APIs that greatly improve the pybind11 wrappers (generally in terms of code simplicity or performance).  We don't want to make these changes without having very good test coverage in place.   - Global changes to how we define wrappers that we don't want to make twice.    Therefore, before that cleanup phase begins, we want to:   - have our coding conventions for pybind11 fully settled so we don't need to revisit files again later;   - have any utility code required by the conventions in place;   - have as many contributed-upstream pybind11 features in place as possible;   - have enough of the stack wrapped to handle high-level integration testing (particularly ci_hsc).  "
Answer: 42028.0

User story: "Experimentation with latest MariaDB containers shows indications of significant performance improvements.  We'd like to update MariaDB and client to latest versions before undertaking our upcoming qserv KPMs  "
Answer: 1378.0

User story: "https://github.com/lsst-sqre/lsst-sphinx-bootstrap-theme is on PyPI, but the current v0.1.0 distribution is missing the {{templates/}} directory. Could have been human error in setting up the package, or a problem with wheels.    This ticket will fix the PyPI distribution, and possibly set up automated continuous delivery with Travis to PyPI."
Answer: 295.0

User story: "Wrap package {{geom}} with pybind11 instead of Swig."
Answer: 8534.0

User story: "For first release of TSV in March, we will have only LS as an option.   This story is about adding other algorithm, such as BLS, which will be available in IRSA.    Adding a new algorithm to the application means:  - changing UI periodogram option panel  - updating the server side (search processor) and match the IRSA api available"
Answer: 1745527.0

User story: "Attend the LSST calibration workshop at Harvard 2/1-2/3.  Present on the Forward Global Calibration Method (FGCM) and discuss applications to LSST and associated improvements.  Discuss LSST auxiliary data necessary for precision calibration."
Answer: 18380.0

User story: "Create a simplified workflow of DM-8339 for [~<USER>"
Answer: 11454.0

User story: "learn about how to setup and use Kubernetes"
Answer: 3.0

User story: "A couple changes need to be made here to satisfy objections in the PR."
Answer: 3219.0

User story: "After the pybind11 merge is complete, it will represent a large fraction of our source and a major item for developers.  Documentation on how to do it should be in the main developer guide, not a separate technote.    Content from the technote should be ported, along with any additions to developed before the merge is complete (e.g. RFC-279 or those TBD on DM-8577)."
Answer: 59671.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: " Move the packages gradle, node.js, and Tomcat  into repos.yaml and making them buildable in Jenkins (with the eventual aim of adding eups firefly to Jenkins).    "
Answer: 787937.0

User story: "Implements most of RFC-279 (all but the part that goes in the pybind11 guide)."
Answer: 68882.0

User story: "For instance, adding a technote needs to register it with keeper.  We need a generic plugin mechanism to do it for arbitrary processes.  Fortunately, we have just the thing...."
Answer: 14831.0

User story: "I am unable to complete copying the doxygen builds from the old NFS home dirs or make new builds as it looks like we've hit a filesystem quota:    {code:java}  -bash-4.2$ git clone https://github.com/lsst/lsstsw.git  Cloning into 'lsstsw'...  error: copy-fd: write returned Disk quota exceeded  fatal: cannot copy '/usr/share/git-core/templates/hooks/pre-rebase.sample' to '/home/lsstsw/lsstsw/.git/hooks/pre-rebase.sample': Disk quota exceeded  {code}    "
Answer: 1617883.0

User story: "Update community.lsst.org to support RFDs. This includes at least creating an RFD sub-category of DM."
Answer: 1794.0

User story: "RFC-277 has decided that JIRA should no longer be used for RFDs. Remove the RFD option.  "
Answer: 43519.0

User story: "Following RFC-277 it has been decided that RFDs should no longer use JIRA but should be moved to community.    This ticket relates to the updating of the decision making process documentation.  "
Answer: 1794.0

User story: "Right now, changing the cuout size value doesn't trigger the images to update.    Only clicking a different row in the table will change the image size but not the cached one either.    Please, make the cutout size field to trigger the images to refresh after 'unfocus' event or hitting enter key (?)."
Answer: 14423.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 lsst-dm-mac.lsst.org server is experiencing hard drive errors that need to be fixed through Apple Care.    See the first and last lines in the dmesg log snippet:    {code}  2017-01-23T21:43:31.534Z cpu3:33107)WARNING: VFAT: 3237: hostd.log: Possible FAT corruption!: offset not found: 0x10000, length 2560, seekOffset 0x0. File length: 67809, status: Not found. FS check will run during shutdown.  2017-01-23T21:43:32.412Z cpu15:33677)VC: 3551: Device rescan time 7 msec (total number of devices 5)  2017-01-23T21:43:32.412Z cpu15:33677)VC: 3554: Filesystem probe time 16 msec (devices probed 4 of 5)  2017-01-23T21:43:32.412Z cpu15:33677)VC: 3556: Refresh open volume time 0 msec  2017-01-23T21:43:32.492Z cpu0:33686)<6>usb passthrough enabled; all eligible devices will be unclaimed by kernel drivers  2017-01-23T21:43:32.582Z cpu10:33698)VC: 3551: Device rescan time 6 msec (total number of devices 5)  2017-01-23T21:43:32.582Z cpu10:33698)VC: 3554: Filesystem probe time 16 msec (devices probed 4 of 5)  2017-01-23T21:43:32.582Z cpu10:33698)VC: 3556: Refresh open volume time 0 msec  2017-01-23T21:43:32.643Z cpu8:33712)ScsiScan: 836: Path vmhba0:C0:T0:L0 supports REPORT LUNS 0x11  2017-01-23T21:43:32.914Z cpu3:33913)Config: 681: "SIOControlFlag1" = 0, Old Value: 0, (Status: 0x0)  2017-01-23T21:43:33.168Z cpu10:34158)VisorFSRam: 700: hostdstats with (0,553,0,0,755)  2017-01-23T21:43:33.168Z cpu6:33064)LVM: 15173: One or more LVM devices have been discovered.  2017-01-23T21:43:33.168Z cpu10:34158)FSS: 7383: Mounting fs visorfs (4302231a43d0) with -o 0,553,0,0,0,0755,hostdstats on file descriptor 43022a83c5a0  2017-01-23T21:43:33.618Z cpu12:33107)WARNING: VFAT: 3237: hostd.log: Possible FAT corruption!: offset not found: 0x10000, length 2560, seekOffset 0x0. File length: 67809, status: Not found. FS check will run during shutdown.  {code}    Actions to address this problem:  1. Backup lsst-dm-mac VM directory.  2. Send it an Apple Care to get the hard drive fixed.  
Answer: 5784.0

User story: "Update the periodogram panel option so is only reflect LS algorithm and keep as single option for now.   Others doesn't make sense with the current API and there won;t be time to make progress on that until March release."
Answer: 10409.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: On a ci_hsc run, I noticed the following errors being repeated multiple times:  {code}  forcedPhotCcd.measurement WARN: Error in base_GaussianFlux.measure on record 775958096257221935:     File "src/SdssShape.cc", line 905, in static lsst::meas::base::FluxResult lsst::meas::base::SdssShapeAlgorithm::computeFixedMomentsFlux(const ImageT&, const lsst::afw::geom::ellipses::Quadrupole&, const Point2D&) [with ImageT = lsst::afw::image::MaskedImage<float, short unsigned int, float>; lsst::afw::geom::Point2D = lsst::afw::geom::Point<double, 2>]      Center (1372,-1) not in image (2048x4176) {0}  lsst::pex::exceptions::RuntimeError: 'Center (1372,-1) not in image (2048x4176)'    forcedPhotCcd.measurement WARN: Error in base_CircularApertureFlux.measure on record 775958096257222342:     File "src/image/Image.cc", line 91, in static lsst::afw::image::ImageBase<PixelT>::_view_t lsst::afw::image::ImageBase<PixelT>::_makeSubView(const Extent2I&, const Extent2I&, const _view_t&) [with PixelT = float; lsst::afw::image::ImageBase<PixelT>::_view_t = boost::gil::image_view<boost::gil::memory_based_2d_locator<boost::gil::memory_based_step_iterator<boost::gil::pixel<float, boost::gil::layout<boost::mpl::vector1<boost::gil::gray_color_t> > >*> > >; lsst::afw::geom::Extent2I = lsst::afw::geom::Extent<int, 2>]      Box2I(Point2I(-336,36),Extent2I(0,0)) doesn't fit in image 15x15 {0}  lsst::pex::exceptions::LengthError: 'Box2I(Point2I(-336,36),Extent2I(0,0)) doesn't fit in image 15x15'  {code}    Scanning the code, I think there are several instances of regular exceptions (i.e., not {{MeasurementError}}) being thrown, which produce the chat.  Errors that are expected for common situations (e.g., centroid off image, bounding box off image, singular matrix) should be converted to throw {{MeasurementError}} to silence them.
Answer: 1784588.0

User story: "Travis CI for {{lsstsw}} is failing this morning with this error message.  The last build was 3 days ago and passed without this error, so it seems likely that these package versions were removed from the public conda repos.    {code:java}  PackageNotFoundError: Package not found: '' Packages missing in current linux-64 channels:       - fontconfig 2.12.1 0    - glib 2.50.2 0  {code}  "
Answer: 212.0

User story: "Igor is complaining that data loading takes much longer time for ForcedSources data than for Sources even though their total size is compatible. This can be related to the number of records (ForcedSources is narrower and should have more records than Sources), though there is nothing in data loader which should depend on this. Opening this ticket to investigate."
Answer: 2338.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Currently, ChartsContainer is only displaying the default chart viewer. In future, we want to add a tbl_group property and logic that ties a chart container to a given group.    When table group property is provided, the Chart Container would create a chart viewer for the given table group (if does not yet exist), and display the charts related to the active table in that table group.   "
Answer: 460834.0

User story: "Add a chatbot front end to the cookiecutter microservice, so we can create technotes by talking to sqrbot.  (and also, stretch, microservices)"
Answer: 7425.0

User story: "lsst-dev[-old] was officially retired yesterday.  Jenkins needs to be update for the new-ish lsst-dev."
Answer: 16038.0

User story: "A schema used in the persistence layer of SpanSets needs to be marked as persistent or it causes a memory leak. Mark the schema as such."
Answer: 12.0

User story: "During the pybind11 porting work, temporary solutions have been adopted in some places to enable us to make rapid progress. Particularly in parts of the codebase which we expect to be performance critical, these need to be cleaned up and, if necessary, replaced with something better. [~<USER> has volunteered to audit the work, identify likely problem areas, and file tickets for clean-up."
Answer: 17285.0

User story: "I have created LSST-style and astrometry.net-style catalogs from the Pan-STARRS1 3pi survey.  These need to be copied to the appropriate places in {{/datasets}}, pending RFC approval."
Answer: 8717.0

User story: "This is regarding the recent discussion in the science-pipelines room where there has been discussion about using composites to get components of a calexp.     In {{CameraMapper}}  we will add metadata readers with object constructors for wcs, calib, and visitInfo.    The API to get the components and entire calexp would be     {code:}  wcs = butler.get(‘calexp_wcs’, dataId={…})  calib = butler.get(‘calexp_calib’, dataId={…})  visitInfo = butler.get(‘calexp_visitInfo’, dataId={…})  calexp = butler.get(‘calexp’, dataId={…})  {code}    (note: we were originally going to use butler composites for this, but decided this is a better way to go)  "
Answer: 41149.0

User story: "pipe_drivers currently does not have a test suite (for a number of reasons), but it needs one to prevent breakage.  We could take some inspiration from the tests in pipe_tasks, and put something together in pipe_drivers.  An alternative approach would be to modify ci_hsc to use the pipe_drivers scripts; that might allow us to break it out the scons mold that seems to annoy some people."
Answer: 1396540.0