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: "It might be nice to have tests that verify significant data files and executables exist and are in the correct location before running the salgenerator builds."
Answer: 488067.0

User story: "Add build job for sal-sciplat-lab."
Answer: 27653.0

User story: "Work with Josh to install a Foreman instance to test deployment to the summit machines, test  with new EFD servers, and setup to start ingesting all available topics."
Answer: 347537.0

User story: "When a config {{Field}} is deprecated, and is equal to the {{default}} value or otherwise unset in the case of optional config fields, then it should not be persisted.    This will ensure that persisted configs can be used with later versions of the stack after the end of the deprecation period and the field has been deleted.      As discussed in RFC-628, this does not address what to do with future versions of the stack when a deprecated config parameter has been set.  "
Answer: 579.0

User story: "Clone the old EFD machine using a copy of the disk. Install and setup in  EFD machine at the summit. Support the test activities."
Answer: 19975.0

User story: "We're running and older version of cert-manager on Roundtable because the new version has a validation webhook component that Argo CD is not deploying correctly.    However Let's Encrypt has sent us a message saying that older cert-manager instances will be blocked from access starting November 1, 2019.    We've been working with Jetstack, the authors of cert-manager, on a  series of fixes to the client. Cert-manager sometimes falls into a   traffic pattern where it sends really excessive traffic to Let's   Encrypt's servers, continuously. To mitigate this, we plan to start   blocking all traffic from cert-manager versions less than 0.8.0 (the   current semver minor release), as of November 1, 2019. Please upgrade   all of your cert-manager instances before then.    We're sending this email because this is the contact address of your    cert-manager instance at:    35.192.78.228 .    Version 0.8.0 is much better but we still observe excessive traffic in  some cases. We're working with Jetstack to improve these cases. As new   versions of cert-manager are released, we will add the non-current   versions to our block list after 3 months. We strongly encourage   cert-manager users to stay up-to-date with new versions.  Also, there is an opportunity to help both Jetstack and Let's Encrypt.    Once you've upgraded, please check the logs for your cert-manager   instances from time to time. Are they making excessive requests to Let's   Encrypt (more than, say, 10 per day over multiple days)? If so, please   share details at [https://github.com/jetstack/cert-manager/issues/1948] .  {quote}    I think Argo CD v1.3 (upcoming) will have a better chance of successfully installing the latest cert-manager because it has better Helm hook support."
Answer: 65136.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "While investigating the (now-resolved) inconsistency in sizes between meas_modelfit and MultiProFit (DM-21124), I decided to look into whether they result from differences and/or bugs in the implementations of approximate Sersic profiles in both packages."
Answer: 31632.0

User story: "In Jenkins HOME is not available to tests so the Astropy cache directory is not shared between processes.  This leads to IERS table files being downloaded every single time a tests are run. Sometimes the download fails and that usually causes test failures that waste developer time. Forwarding HOME to the test environment would fix this but we are concerned that this may introduce side effects into the test environment. Astropy provides another mechanism via the XDG_CACHE_HOME environment variable.    If this variable is not set we should set it to {{~/.lsst/}} and create an {{astropy}} directory for the cache.  Do not forward XDG_CONFIG_HOME since that might affect tests using astropy."
Answer: 6863.0

User story: "New BOT runs will have approximately 5 times more data volume than previous run.  A single rsync process will not be able to keep up on large volume days.  Implement a new data transfer (e.g., maybe simultaneous rsync processes) to be used for the upcoming BOT runs."
Answer: 31588.0

User story: "[~<USER> pointed out that we should probably be testing the {{AvsIdentity.DeviceStatus}} field returned by {{AVS_GetList}} for values other than {{1}}. The vendor docs don't say enough about under what conditions the {{0,2,3}} states can be set, so I'll just have to play with the device some to see if I can get any of them to trigger. If I can, I'll add some tests of those states, so that the controller can provide useful error messages if it encounters them."
Answer: 21702.0

User story: "The newly promote LOVE CSC is basically only a listener that sends Events.  It does not stream Telemetry nor define any Commands.  The SAL expects every CSC to have a minimal set of Commands, but this is no longer the case.  SAL needs to be updated to account for this condition.     This really only affects the LabVIEW build step and the RPM packaging, but there are probably other gotchas, as well."
Answer: 9997.0

User story: "This repo contains all the misc scripts used as part of the L1 deployment.  This includes things like systemd scripts, etc."
Answer: 349.0

User story: "Using DM-21271, generate some data and try to extract the reference wavefront; i.e., the piece that doesn't vary visit to visit.  This should hopefully consist just of fitting out some low-order polynomials (maybe 2nd degree) for each or several Zernike coefficients and then combining the residuals.  Do it without rotation first, since adding rotation will probably make this quite a bit more complicated.    Add effects progressively, including:    [x] - rigid body perturbations    [x] - M1M3 bending modes (M2 too if these are available)    [ ] - permanent figure errors    [x] - chip-to-chip gaps"
Answer: 93201.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 batoid to simulate LSST optics wavefronts.  The purpose is to 1) See if we can extract a reference wavefront from donut fits of individual exposures and 2) using said reference wavefront, infer the optical state of a given exposure.    Include:    [x] Rigid body degrees of freedom    [x] M1M3 bending modes    [ ] M2 bending modes    [x] permanent figure errors    [x] rotator    [x] chip-by-chip surface height variation         Eventually we'll want to use donuts instead of wavefronts and add an atmospheric simulation, but for now just use Gaussian noise on Zernike coefficients."
Answer: 90526.0

User story: "Use batoid's Bicubic surface together with information from [https://github.com/<USER>M1M3_ML] to probe effects of M1M3 bending modes on wavefronts. "
Answer: 90538.0

User story: "Update the middleware code by Moog to use the latest SAL version. At this moment, the ts_sal 4.0 is unavailable. Therefore, the latest version of ts_sal and ts_xml will be used. The code update might be needed for the possible DDS/ xml interface changes. This task will also try to find a way to test the code even though the hexapod/ rotator cRIO controller and hardware are unavailable."
Answer: 18574.0

User story: The output of the spectrograph is currently going to be stored in the Large File Annex (LFA) as FITS files. The CSC needs to be able to push data to the LFA after it is read out and packaged: this ticket is for the work to manage that communication.    My goal here is to make this flexible enough that it is easy to swap it out if we decide we want to use some other storage method (e.g. direct to database).    Where do I find documentation about how to communicate with the (an?) LFA? How should we handle testing of that communication? I can obviously stand up a mock as I'm doing for the spectrograph itself, but it would be good to have a "real" system I can talk to for validation.
Answer: 48939.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 are sometimes running into test failures on Jenkins relating to IERS lookups in Astropy. The failures look a bit like:  {code}  ValueError: zero-size array to reduction operation minimum which has no identity  {code}  and come from the {{\_combine_a_b_columns}} method when it is processing the IERS_A table.    I can trigger this problem locally by setting {{$HOME}} to a directory that doesn't exist and disabling the astropy cache.   This matches the Jenkins conditions where I believe we still run all the jobs without caching enabled: this is a worst case scenario for astropy since it means that every product that is built that uses the IERS tables (which now means everything that uses astro_metadata_translator) is having to download a new copy of the IERS file. The problem I think is that pytest forks multiple processes to run the tests in parallel and sometimes those threads try to download the IERS tables simultaneously. In my tests I am finding that failures occur when the table is truncated (it reports different number of lines) suggesting to me that astropy is downloading the file to the same place in each test subprocess and the file is being overwritten as an earlier process reads it.    Outside of Jenkins this is barely noticed since the caching will be in use and the file will only be downloaded at most once per build."
Answer: 1620.0

User story: "'SELECT COLUMNS' queries are not working in multi-czar as the czar is trying to get the information from local databases and it is only available from the master. The integration tests for columns need to be reinstated.(qserv_testdata/datasets/case04/queries0020_showColumnsFromDeepForcedSource.FIXCODE) "
Answer: 57494.0

User story: "The traceability matrix in LDM-639 maps a list of LVV/DMS-REQ to their corresponding LVV-T in Jira. It would be useful to add a third column to this table to link to the parent LVV/REQ "
Answer: 10476.0

User story: While working on ingest and especially gen2convert, I've found it frustrating to need to pass a collection/run to Butler at construction, rather than later, when calling get/put/ingest.  We often need an object that represents the combination of a Registry and a Datastore _without_ specifying a collection/run.    I think we should add optional "run" kwargs to all Butler write operations and "collection" kwargs to all read operations, and make the corresponding construction arguments an optional way to provide defaults for these.    As a side note, I think I'd like to eventually move to having Butler support lookup with ordered sequence of collections rather than just a single one.  We could anticipate that by making the new kwargs for read operations a "collections" sequence rather than than a "collection" scalar, even if we don't implement support for more than one yet, but I'm also willing to defer that for later.
Answer: 203216.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: "Document all firewall port numbers, including which systems need to talk to each other.  This is for:    https://confluence.lsstcorp.org/display/LSSTCOM/Firewall+Information+for+Auxiliary+Telescope+Systems#/"
Answer: 253568.0

User story: "Document all fault codes can be used by IIP components."
Answer: 10477.0

User story: "The Python k8s API documentation and the observed behavior of k3s with containerd (no docker) runtime differ.  Adding an ENTRYPOINT to the container should make it consistent and not cause any change in behavior."
Answer: 8595.0

User story: For individual obs packages, we are using "translators" to convert metadata from raw files into internally consistent conventions (as many telescopes have different sets of conventions and header naming).  Our convention for boresight rotation angle is:   {code:python}  At boresightRotAngle = 0, the focal plane pixels are alligned:  +x: E->W (-ve RA), +y: S->N (+ve Dec)  {code}  (and see  the [documentation|http://doxygen.lsst.codes/stack/doxygen/x_masterDoxyDoc/namespacelsst_1_1afw_1_1image.html#a7ea6a783e80a6f548b3fb535f0bd9fb7]).    Accordingly, the {{imsim}} translator in {{obs_lsst}} should reflect that:  {code:python}  boresightRotAngle = 90 deg - ROTANGLE  {code}  (where the ROTANGLE is the FITS card in the raw data).    The reason data is currently being processed properly is due to a compensation (prior to the translator functionality) for this 90 deg shift in the {{lsstCamMapper}} [here|https://github.com/lsst/obs_lsst/blob/master/python/lsst/obs/lsst/lsstCamMapper.py#L164-L166].  This latter "correction" should be removed from there and accommodated in the {{imsim}} translator.    This change will be validated by running a visit of DC2 data before and after and checking that we get consistent results.
Answer: 2993.0

User story: "DM-21186 didn't quite finish the job and some config files still refer to auxTel."
Answer: 85.0

User story: "The option {{convolveTemplate=False}} in image differencing is broken: it convolves the science image instead of the template as intended, but it then subtracts the convolved science image from the *science image* instead of from the template. See lines 647-659 of {{imagePsfMatch.py}}. Note that in the below code, {{results.matchedExposure}} is the convolved template image if {{convolveTemplate=True}} and is the convolved science image if {{convolveTemplate=False}}.    {code:python}  subtractedExposure = afwImage.ExposureF(scienceExposure, True)  if convolveTemplate:      subtractedMaskedImage = subtractedExposure.getMaskedImage()      subtractedMaskedImage -= results.matchedExposure.getMaskedImage()      subtractedMaskedImage -= results.backgroundModel  else:      subtractedExposure.setMaskedImage(results.warpedExposure.getMaskedImage())      subtractedMaskedImage = subtractedExposure.getMaskedImage()      subtractedMaskedImage -= results.matchedExposure.getMaskedImage()  {code}"
Answer: 4488.0

User story: "status.lsst.codes died yet again"
Answer: 250.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: "Week 4 of M1M3 functional testing"
Answer: 61977.0

User story: "Week 3 of M1M3 functional testing"
Answer: 44746.0

User story: "Week 2 of M1M3 functional testing"
Answer: 44746.0

User story: "This is the second half of the big registry overhaul (the big part being DM-17023).  Plans have been described in detail at [https://docs.google.com/presentation/d/1KxVmRN_8S4GskyGxEkeoX7tn5c8b9xViy73JU4dkXOA/edit?usp=sharing.]         Goals include:   * Normalizing the dataset table into different tables for each dataset type.  This should improve query performance and give us flexibility in how we store metadata associated with datasets (possibly including regions and timestamps that are currently restricted to dimensions).   * Restructuring the registry codebase towards supporting eventual chained-schema registries.   * Enabling bulk inserts of datasets during ingest.  This will require changes to Datastore as well (particularly its relationship with Registry).   * Addressing performance and concurrency problems in our usage of transactions.    Whenever possible, I'll try to split this up into smaller tickets.  The sheer size of DM-17023 has become a problem of its own, though I'm not sure how much I could have split it up.  Happily this ticket should have a much smaller effect on public interfaces, though it will still involve some broad breaking changes."
Answer: 550141.0

User story: Generate a new complete {{ap_pipe}} run of HiTS data, using both {{CompareWarp}} and {{DCR}} coadds. Define the skymap with 0.2"/pixel resolution, as opposed to previous 0.333"/pixel resolution, generate warps, and calculate both types of coadds. Run {{ap_pipe}} with HiTS 2015 as the science images for both, and make a new notebook to compare the results. The results should also be compared to previous runs using the low resolution templates.
Answer: 15538.0

User story: "Building coadds and running {{ap_pipe}} with many different settings revealed some inconsistent behavior. In summary, the PSF FWHM used to compare the template and science image appears to still be based in pixel units in some places, which is a bug when they don't have the same platescale. There are also bugs in the option to convolve the science image rather than the template, which you would want to do if the seeing of the science image was better than that of the template. One is that the kernel attributes appear to still be calculated for the case where the template is convolved. The other appears to be an incorrect noise threshold, but that will require further investigation.    This ticket covers the work spent investigating these issues, and the initial bug fixes."
Answer: 21233.0

User story: "Migrate the test jobs on Jenkins from DM to TSSW. The following repositories will be moved: ts_wep, ts_ofc, ts_phosim, and ts_MTAOS."
Answer: 5561.0

User story: "Week 1 of M1M3 functional testing"
Answer: 25451.0

User story: "Implement heartbeat messages to archive controller."
Answer: 4399.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: "Implement the timeout task to wait for the expected ack from the archive controller."
Answer: 4402.0

User story: Goal: The PTC task should calculate a linearity model, in whatever form is necessary for isrTask's linearity correction to be able to run and use it.    This ticket captures the thinking and algorithmic work necessary to generate linearity models, but isn't concerned with how they are persisted, or passed from task to task.      This ticket used to say:  {quote}  In talking with Andrés, it was decided that the _de facto_ title for this ticket is actually "{color:#1d1c1d}Write a task that creates a linearity model, which could either be the PTC task itself, a wrapper around the PTC task, or a separate task which uses the output of the PTC task{color}", but that's a bit long to actually change it to, so keeping the title the same, but this encodes the essence of the ticket.  {quote}
Answer: 211678.0

User story: "MultiProFit Parameters can return derivatives of their Transform, in order to transform Gaussian parameter Jacobians into actual fit parameter Jacobians. get_transform_derivative has a verify flag, which verifies the return value by comparing it to a finite difference. Setting this to False by default and only setting it to True when validating the Jacobian should improve performance significantly."
Answer: 46384.0

User story: "DM-21071 found that MultiProFit is 1-2 orders of magnitude slower than meas_modelfit at fitting the same models (e.g. just exp/dev). Running cProfile on a few cases should reveal whether there are any obvious, low-effort ways to improve the performance and/or cut down on overhead."
Answer: 86429.0

User story: "Create CWFS notebook for AuxTel on-sky testing to assist in collimation activities."
Answer: 46209.0

User story: "DM-21213 identified an issue with the current implementation of Gauss's method that needs to be solved.     In summary, the initial estimate of position at the second observation is off by as much as 10,000 km. This needs to be investigated and solved (with unit tests!). "
Answer: 542677.0

User story: "Baseline IOD and OD package will likely be pyoorb / oorb but we need to validate some of its basic functionality so having a python implementation of IOD is useful. To that end, we need an implementation of Gauss's method to get an estimate of an initial orbit from a linkage.     Enhancing Gauss's method with different methods to find the velocity at the time of the second observation is necessary especially when dealing with different observing arcs. Supporting velocity methods include Gibbs and Herrick+Gibbs.           "
Answer: 271961.0

User story: "Although MultiProFitTask should never fail, if it does (e.g. by interruption), it will not generate any output. This ticket is to modify the Task's Config to specify an output file and interval to write to disk."
Answer: 48612.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 telemetry generated by HVAC control software. Organize the telemetry into XML files and generate updated version of MQTT publication software."
Answer: 14490.0

User story: "In DM-21065 we deprecated the use of Policy as an API argument in ip_diffim and meas_algorithms and announced they would be removed after release 19.0.    This ticket is to remove those deprecated APIs (retaining the PropertySet implementations) and to remove pex_config.makePolicy."
Answer: 316692.0

User story: "build xml and sal with rob. There will be no errors and everything will go smoothly."
Answer: 14408.0

User story: "retrieve telemetry from chiller and publish it (along with the kiloarc telemetry)"
Answer: 29937.0

User story: "Currently OCS controller data and CCS controller data end up with the same gen 2 butler registry entries because the OBSID or controller is not part of the gen2 schema. To allow ingest of both sources of data into the same repository I think we have to change the visit calculation.  I propose generating the visit as if CCS data have seqNum 100,000+ as the base.    This needs to be checked though since it will mean that you will not be able to retrieve data using the dayObs and seqNum combination since that might not be unique any more. Visit would always have to be provided. We could also change seqNum to 100,000+ to fix this as well but I'd need some feedback on this.    I believe Gen3 will have the same problem since even though OBSID will be ingested it still requires that an exposure_id be unique."
Answer: 118268.0

User story: "Using SQLAlchemy with SQLite, Oracle, and PostgreSQL backends, write a Python snippet that bulk-inserts into a table with an autoincrement field and returns to Python the values of the autoincrement field.  This operation must be safe in the present of concurrent inserts into the same table.    My understanding is that:   * PostgreSQL can do this via INSERT ... RETURNING, and SQLAlchemy already supports that syntax.   * Oracle can do this via INSERT ... RETURNING, but the way those results are returned is different from how the PostgreSQL native Python driver does it, and SQLAlchemy does not support that syntax, at least for bulk inserts.   * SQLite cannot do this for bulk inserts at all, unless you either:   ** rely on exclusive locking and do arithmetic on the last inserted ID and the number of rows (scary, to say the least - and I'd really like to stop using exclusive locking)   ** select from the sequence in advance and then use those values explicitly in the insert (at least, I think this ought to work - but it definitely needs to be tested).    I don't think this operation needs to also include the conflict-resolution options of DM-21201, but it's possible we'll identify a need for that in the future.    I do think we'll want a guarantee that the order of returned IDs match the order of the rows provided, or have some other way to connect them if that's not true.     "
Answer: 70663.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: "Using SQLAlchemy with SQLite, Oracle, and PostgreSQL backends, write a small Python snippet that bulk-inserts into a table with a primary key or other unique constraints and, depending on an option provided by the caller, either:   * aborts when the constraint is violated (as usual)   * ignores new records that conflict with old records   * replaces old records with new records when conflicts appear.    This operation needs to be safe in the presence of concurrent inserts into the same table (though in that case we don't care who wins if one or more writers are attempting to replace).    I am fairly confident all three RDBMSs provide a syntax for this, but it's not the same, and SQLAlchemy support is uneven, so this will in general involve asking SQLAlchemy's connection object for the lower-level RDBMS-specific connection object (or equivalent)."
Answer: 46284.0

User story: "The current script {{csc_send_to_state}} fails to transition {atHeaderService} at the Tucson test stand. Tiago Riviero suggest to add an {await} to the {Remote.start_task}"
Answer: 208.0

User story: "The lsst_obs metapackage contains obs_comCam and obs_monocam packages. obs_comCam is known to be a partially implemented package that has been superseded by obs_lsst.  obs_monocam was written for a prototype CCD that never produced good data. The obs package is known to be broken because some afw APIs changed in the last couple of years and the fixes were never applied because tests were never run. [~<USER> informs me that there is no benefit to trying to rescue the package.    On this ticket I will remove the two packages from the lsst_obs package and move them to lsst-dm org and in legacy mode. I will also rename lsst-dm/obs_auxTel to legacy.  "
Answer: 24644.0

User story: "DM-21070 and DM-20728 required a workaround to get the likelihood for models with non-linear vs linear fits. This all stems from the fact that multiprofit.objects.Modeller.fit returns a results dict with a likelihood item that is sometimes a scalar log likelihood and sometimes a tuple with the log prior as well. That function should be updated to return a consistent structure in every case."
Answer: 68614.0

User story: "Currently, if the start_task is not run (and awaited) then it is possible to use a remote and it will timeout (or not respond) until it comes alive. This ticket is to implement the functionality that will raise an exception if it is not completed, and provide an error message to use the start_task to avoid the exception"
Answer: 361381.0

User story: "Once I have the the complete FiberSpectrograph code written in DM-21188, I should lift the {{unittest.Mock}} system into a separate importable class ({{FiberSpectrographSimulator}}?), so that it can be used by the CSC and any CSC unittests. The simulator should have a way to disable the patches as well, to restore the real spectrograph communication."
Answer: 10038.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: "Read the documentation on the M1M3 provided by [~<USER> before he left the project.  This task also covers the travel to Chile."
Answer: 31301.0

User story: "This task covers the time to release v4.2 (or whatever it gets tagged with) of the XMLs, as well as work with [~<USER> to train him to cover this work when I am unavailable."
Answer: 11591.0

User story: "This task covers the time to release v4.0.0 of SAL, update the tests accordingly, as well as work with [~<USER> to train him on the SAL release process."
Answer: 15952.0

User story: "{{kafka-connect-manager}} was implemented in DM-21042, we need a Helm chart for its deployment. "
Answer: 1725.0

User story: "I put DM-21139 in review before I had implemented the exposure start/stop commands, because there was already >400 lines of code on that ticket (which is at the limit of what is reasonable to review). The {{expose}}-related commands are going to be my first real taste of asyncio, and I plan to implement them using the asynctest framework, as a trial run for DM-21130. This ticket is for that implementation and its tests."
Answer: 8821.0

User story: The generated camera YAML files always have "lsstCam" as the name of the camera. This is not true for AuxTel or test stands.  This needs to be fixed.
Answer: 17102.0

User story: "The name of the camera on AuxTel is LATISS.  Unfortunately we call the camera AuxTel in obs_lsst. It would be much clearer to use the proper name.    I think so long as AuxTelMapper class is still called the same name (so existing gen2 repos don't need to change) that everything else can be changed to LATISS and Gen3 (see DM-16297) can use the correct name."
Answer: 1652.0

User story: "intermittent unit test failures."
Answer: 125.0

User story: "DM-21171 needs access to the local calibration from PhotoCalib. No currently exposed function within PhotoCalib takes a point and returns the local calibration and error. This ticket will create such a function and expose it within python."
Answer: 12822.0

User story: "It looks like something changed and qserv logs (and only those) weren't getting ingested.  But now looking at it...         It looks like the helm chart was changed, so that the values.yaml interface was different.  This was a silent and annoying failure.  So the qserv config parts for fluentd weren't being put in the config map, and therefore weren't being put in the pod, and therefore fluentd wasn't looking there.    This change was a breaking change but I must have missed when we took this update.  We're running 3.0.0 now, although I think this might have been updated globally, and not by me.  Although maybe it was me.  Hard to tell.  But either way, the values were out of sync with the chart.    Here's the commit where this changed on the upstream chart:    [https://github.com/kiwigrid/helm-charts/commit/c539ea63e9b234953b6bd34a58e9c1714d45b553]"
Answer: 2.0

User story: "Remove or reduce the log level of extraneous log messages."
Answer: 8626.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: "So there's a list in the TAP service, found here:        [https://github.com/lsst-sqre/lsst-tap-service/blob/master/src/main/java/org/opencadc/tap/schema/ALMATapSchemaDAO.java]         But that doesn't have some things that are in this list:         [https://lsst-web.ncsa.illinois.edu/schema/sciSQL/]         So all those functions need to get into that list.  Otherwise you won't be able to use them, and TAP won't pass them down."
Answer: 178772.0

User story: The ADLink consultant we hired suggested that we use a single DDS cache shared between the script queue and scripts in order to speed up starting up scripts (apparently it will greatly reduce the time required to wait for historical data).    [~<USER> suggests adding the following to the ospl.xml file pointed to by OSPL_URI  (ie the global configuration):    {code}  <DurabilityService name="durability">        <Network>           <InitialDiscoveryPeriod>0.1</InitialDiscoveryPeriod>           <Alignment>              <TimeAlignment>false</TimeAlignment>              <RequestCombinePeriod>                 <Initial>1.0</Initial>                 <Operational>0.1</Operational>              </RequestCombinePeriod>           </Alignment>           <WaitForAttachment maxWaitCount="1">              <ServiceName>ddsi2</ServiceName>           </WaitForAttachment>        </Network>        <Persistent>           <StoreDirectory>/data/persist/</StoreDirectory>           <StoreMode>XML</StoreMode>         </Persistent>        <Tracing>           <Verbosity>NONE</Verbosity>  <!--          <OutputFile>durability.log</OutputFile> -->        </Tracing>        <NameSpaces>           <NameSpace name="defaultNamespace">              <Partition>*</Partition>           </NameSpace>           <Policy alignee="Initial" aligner="true" durability="Durable" nameSpace="defaultNamespace"/>        </NameSpaces>     </DurabilityService>  {code}    I think the relevant bit is:  {code}      <Persistent>          <StoreDirectory>/data/persist/</StoreDirectory>          <StoreMode>XML</StoreMode>      </Persistent>  {code}
Answer: 73279.0

User story: "As part of the ScienceDataModel we need to have calibration products available for use in the Functors in the SDM code. One solution to making these products available is to compute their local values and store them per row in the afw tables output by various SciencePipelines tasks. This ticket will implement a task to perform this operation."
Answer: 28835.0

User story: "Wait for initial scan to complete before showing new images."
Answer: 47941.0

User story: "Setup integration tests for ncsa teststand and add ScriptQueue to teststand as well."
Answer: 41872.0

User story: "Remove pervious code in ap_association that produces static and time-series features and replace them with the new DiaCalculation measurement pluggin system created in DM-18494"
Answer: 73121.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, several static and time-series features are implemented in ap_association. This ticket will replicate the behavior and values calculated in the current code within the DiaCalculation framework created by DM-18494."
Answer: 60199.0

User story: "Extend the notebook produced in DM-21067 to show more complicated investigations.  Examples would be:    * Correlating series from different measurements in the EFD: current vs. temperature or similar  * Show how to investigate annotations in a notebook.  * Log entries with telemetry streams."
Answer: 14106.0

User story: "Create RFC,  and issue new version of LDM-639"
Answer: 34.0

User story: "Check the Middleware code by Moog. This task will try to do the followings:   # Create a new private repository for middleware code by Moog.   # Clone the repository to the personal account on the management PC.   # Try to build the code by make.   # Rearrange the files and update the Makefile for the files.   # Write the README.md for the build process and code details.   # Begin to add the test framework."
Answer: 14144.0

User story: "This task is to update the M2 cell control system in cRIO to use the LabVIEW 2018 sp1 32 bit version. It is using the LabVIEW 2015 sp1 32 bit at this moment. The followings are the steps:   # Install the LabVIEW 2018 sp1 32 bit version and related toolboxs in the windows laptop.   # Fix the M2 cell projects for the possible interface changes between the LabVIEW 2015 sp1 and 2018.   # Deploy the M2 cell code to cRIO.   # Test the connection between M2 controller and cell."
Answer: 18749.0

User story: "Since RFC-625 is now adopted, this issue is to implement the design outlined there.  Specifically, this will define an on disk representation for QE curves including a butler dataset for retrieving them.  It will also require implementing a free function for evaluating the curves at various points in wavelength and position on the detector."
Answer: 122389.0

User story: "The merge of DM-20692 changed the call signature of {{AssembleCoaddTask.processResults()}}, which is used in {{DcrAssembleCoaddTask}}.  The breaking change was not caught by existing unit tests."
Answer: 3627.0

User story: "Once DM-21065 merges there are very few places outside of gen 2 butler that depend on pex_policy.   Remove those final places and replace them with use of YAML and PropertySet."
Answer: 4237.0

User story: "Spend Friday with the movers"
Answer: 2934.0

User story: "Create python based sqlite alert generator. Based around  https://github.com/lsst-dm/alert_stream  But uses actual alerts from L1 Processing."
Answer: 292563.0

User story: "Modeled on   https://gerardnico.com/dit/kafka/connector/sqlite_standalone  Set up routine to read output sqlite from L1 processing and send to kafka server. Reliance on confluent and lack of cutout suggest it is not reasonable model going forward."
Answer: 13.0

User story: "Update the developer guide as proposed in RFC-623."
Answer: 541473.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 a chat with Tony it appears we should consider items to name the Jim Gray X ... this should be written up."
Answer: 23548.0

User story: "DU the FY 20 reqs Princtone NCSA UW IPAC"
Answer: 135433.0

User story: "[~<USER> reports on installing the LSST stack with numpy 1.17:  {quote}  This line needs modifying https://github.com/lsst/ip_diffim/blob/master/python/lsst/ip/diffim/diffimTools.py#L88 as:  {code}  -intNoiseArr = rand.poisson(imArr)  +intNoiseArr = rand.poisson(np.where(np.isfinite(imArr), imArr, 0.0))  {code}  in order for ip_diffim's tests to pass. I think this is because I am using numpy 1.17, in which {{numpy.random}} changed largely. {{rand.poisson()}} no longer accepts {{lam >= 9.223372006484772e+18}} or {{lam = nan}}.  {quote}"
Answer: 36626.0

User story: "Now that I have a working test framework, implement the {{status}}, {{expose}}, and {{stop_exposure}} commands. As part of this work, I plan to also pull most of the code from {{fibspec.py}} into {{FiberSpectrograph.py}}, as I don't think the extra layer of indirection is helpful."
Answer: 11227.0

User story: "Check the M2 MATLAB tools with functions provided by Harris. The attached files ([^FunctionsForLSST.zip]) are the missing functions provided by Harris. This is a follow-up task of [DM-21014|https://jira.lsstcorp.org/browse/DM-21014]."
Answer: 31573.0

User story: The forwarder should register it's information to the redis database.   Please add a yaml string of  {noformat}   {"hostname": HOST, "ip_address": IP_ADDRESS, "consume_queue": CONSUME_QUEUE"}  {noformat}    to the list named "forwarder_list" on redis database 15.   This can be added with LPUSH, and retrieved with BRPOP. This information will be used as a rendezvous point for the ATArchiver.
Answer: 20237.0

User story: "SalObj 4 Bootcamp"
Answer: 38969.0

User story: "participate in salobj boot camp, put together a skeleton CSC for the rotator "
Answer: 10000.0

User story: "Please add the https://github.com/Martiusweb/asynctest package to Docker containers used for Python T&S software. This adds some useful support to unittest, including the ability to write asynchronous test cases directly, e.g.:  {code}  async def test_foo(self):      # code  {code}  instead of  {code}  def test_foo(self):      async def doit(self):          # code        asyncio.get_event_loop().run_until_complete(doit())  {code}  (which silently does nothing if one forgets the event loop call)"
Answer: 55956.0

User story: "It's only an attempt to add a tmpdir nested under the testdata directory, but that's enough to cause a failure when the testdata repo is read-only."
Answer: 37553.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-20493 re-made plots including flux-size relations for COSMOS/HST galaxies. These initially revealed inconsistent sizes between true Sersic fits and GalSim catalog values, as well as between true and multi-Gaussian Sersic fits, both by a factor of ~1.13 (the ratio of R_eff to sigma for a Gaussian). These bugs were likely introduced after the switch from fitting axis ratios/position angles to the correlation ellipse parameters."
Answer: 82231.0

User story: "DM-15909 introduced a notebook deriving optimal weights for a Gaussian mixture approximation to a Sersic profile. The plots therein needed some minor updates, mainly to show the profiles of each contributing Gaussian (not just their sum)."
Answer: 11882.0

User story: "So, the landing page needs some work.  We should get rid of the things that we don't need, and add configurability for the things we do (like what URL is used to load the actual markdown with the motd, which is static)."
Answer: 40175.0

User story: "The Confluent Platform is the set of services needed to run SQuaRE Events (the implementation of Kafka for Roundtable-based applications). Confluent Platform was previously deployed for the SQuaRE Events demo (DM-16932) and subsequently for the EFD. This ticket is to follow in the steps of that work and deploy the Confluent Platform into the Roundtable cluster.    - Deploy using Helm  - Document the deployment and operation of the cluster"
Answer: 50079.0

User story: "The developer guide should reference the usage of {{@sqrbot-jr create project}} and {{@sqrbot-jr create file}}:    - To create technotes  - To create new repositories  - To create license boilerplate and preambles  - To create documentation topics"
Answer: 10054.0

User story: "Create a decentralized help system for SQuaRE Bot Jr. The idea is that a user can type {{@sqrbot-jr help}}, and then individual backends can receive that Slack event via Kafka and decide to send a help message back to the user. Right now templatebot is the only user-facing backend app, so we'll enable the help feature there.    Write documentation to help developers implement help in their sqrbot backends."
Answer: 98099.0

User story: "Deploy and document the initial Kubernetes cluster for the Roundtable platform. Size the cluster to make it easy to deploy Confluent Kafka.    Also:    - Document the cluster configuration and deployment pattern in roundtable.lsst.io  - Research any configuration options that impact things like logging and use of DBs (VPN or not, for example)."
Answer: 22065.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 Roundtable platform needs an ingress service to make applications available to the internet. The service should let applications provide their own Ingress resources so that they can control their own endpoints. The service should also integrate with Let's Encrypt to provide auto-renewing TLS certificates. The main contenders are:    - [nginx-ingress|https://kubernetes.github.io/ingress-nginx/] and [cert-manager|https://github.com/jetstack/cert-manager/] (this was used for the square-events pilot project)  - [traefik|https://docs.traefik.io/user-guide/kubernetes/] (which natively integrates with Let's Encrypt)    In this ticket:    - Decide between nginx-ingress and traefik based on team feedback  - Deploy the ingress control using Helm  - Document the deployment and operations of the controller"
Answer: 22090.0

User story: "In order to make service deployment to Roundtable more transparent, while also helping developers adhere to Git Ops-based best practices, let's pilot the usage of [Argo CD|https://argoproj.github.io/projects/argo-cd/]. With Argo CD, developers can use the Argo dashboard to initiate new deployments, and monitor version upgrades.    The purpose of this ticket is:    - Deploy Argo CD into the roundtable cluster using Helm  - Document the deployment and operation of Roundtable using Helm  - Provide developer-level docs for using Argo CD (as much as is practical given how well the developer-facing story is at this point)."
Answer: 22096.0

User story: The SAL 4 branch is adding some fields to the revcode IDL that I suspect are not wanted. I don't know if older SAL also does this.    After all the command and events, but before the "ackcmd" topic I see these entries, which stand out because they are indented (just as shown here). One command with no name and one logevent with no name:  {code} struct command {     string<8> private_revCode;     double private_sndStamp;     double private_rcvStamp;     long  private_origin;     long   private_host;     long  private_seqNum;     long TestID;     string<32> device;     string<32> property;     string<32> action;     string<32> itemValue;     string<128> modifiers;   };   #pragma keylist command TestID   struct logevent {     string<8> private_revCode;     double private_sndStamp;     double private_rcvStamp;     long  private_origin;     long   private_host;     long  private_seqNum;     long TestID;     string<128> message;   };   #pragma keylist logevent TestID  {code}  I suspect these should not be present and am worried they may confuse code that tries to parse the IDL, such as the sal/kafka producer (it will parse IDL files to find descriptions and units).
Answer: 127846.0

User story: "Create a lsst-sqre/roundtable Git repository and an initial roundtable.lsst.io Sphinx-based documentation site.    The purpose of the doc site is to document how to operate/deploy roundtable, and how to deploy applications on roundtable. The site will also includes standards and specifications for developers."
Answer: 1742.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: "xfer_param message has global member variable that is reset every time a new xfer_param message comes in. That transfer info should be saved in some other place and reuse from database or data structure."
Answer: 13273.0

User story: "Please add a salgenerator command that just makes rev-coded IDL files (e.g. sal_revCoded_ATCamera.idl) -- the files used by dds salobj.    The main purpose is to speed up generation of these IDL files, since there would be no need to create C++ or other source code."
Answer: 127978.0

User story: "Make helm charts for the other services, which should be simpler than nublado.    This includes:   # TAP service   # Firefly   # Landing page   # SODA service    Then tie it all together with .a deployment script to install those charts with reasonable values."
Answer: 41601.0

User story: "Update the ci_hsc workflow, image, and data to newer stack (w_2019_34/w_2019_35/w_2019_36)      And use them to debug running pipetask with the dev branch and the RDS registry. "
Answer: 34464.0

User story: "The tutorial notebook that ships with the notebook aspect is now raising deprecation warnings for {{geom}} objects like {{Point2D}}."
Answer: 356865.0

User story: "{{lsst.verify.MetricTask}} as written based on an alpha release of the Gen 3 framework, and borrows its {{PipelineTask}} API to let subclasses seamlessly transition from Gen 2 to Gen 3. However, the final Gen 3 framework does not have two of the methods assumed by the original {{MetricTask}} design, namely {{adaptArgsAndRun}} and {{getInputDatasetTypes}}. While these methods are acceptable in {{gen2tasks.MetricTask}}, which will eventually be removed, subclasses that are supposed to be Gen 2/Gen 3 agnostic must not be required to implement these methods and must not depend on them for functionality.    This ticket covers the following work:  * Rewrite {{PpdbMetricTask}} to no longer have a custom {{adaptArgsAndRun}}, while leaving the API seen by subclasses unchanged.  * Replace all calls to {{adaptArgsAndRun}} in the metrics test suites of {{ip_diffim}}, {{ap_association}}, and {{verify}}, as well as in the common test code provided by {{verify}}, except where the code is only applicable to Gen 2.  * Remove references to overriding {{adaptArgsAndRun}} in the {{MetricTask}} and {{MetadataMetricTask}} documentation.  * Replace all calls to {{getInputDatasetTypes}} in test code.  * Remove references to {{getInputDatasetTypes}} from the documentation of {{PpdbMetricTask}}"
Answer: 58829.0