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 came up in HipChat.  Here is the transcription: {quote} [6:29 AM] <USER> @<USER>Since we are working on newinstall.sh anyway, is it worth re-evaluating whether it should be asking to install git?  Compiling git in the absence of libssl (absent on many distros by default) causes the build to fail when fetching https repos. [6:29 AM] <USER> is there any reason not to simply make git a prereq and have people install it using whatever package manager they have? Or are you still supporting operating systems that have a git that is too old?    6:30 AM   <USER>joined the room [6:30 AM] <USER> I think the idea was the latter.   I think at one point the installer needed git 1.8, but I don't think that's the case anymore. [6:31 AM] K-T Lim: It's not clear to me that users (as opposed to developers) should have to have git. [6:31 AM] <USER> I imagine Snow Leopard comes with an ancient git but I also imagine you don't want to be supporting Snow Leopard anyhow   are we talking users or people building the software from source? [6:32 AM] <USER> This is for anyone using newinstall.sh [6:32 AM] K-T Lim: Right now, users are a subset of the people building the software from source   Because eups distrib install does the latter [6:33 AM] <USER> so it's building the software. So they need developer tools anyway. Why not git. It's trivial to use rpm or whatever to install git. [6:33 AM] K-T Lim: Many things are less trivial for people without root [6:33 AM] <USER> That's true.   Don't all distros come with git by default? [6:34 AM] <USER> I suppose it depends what "default" means. OS X does. If you spin up a ubuntu digital ocean minimalist VM does that have git? [6:35 AM] <USER> We're really just talking about distros that are too old to have a modern git.  Since we are only supporting Mountain Lion and newer, I don't see why we can't draw a line somewhere reasonable for CentOS too.   @timj That's a good point, but we already have a laundry list of prereqs that have to be installed on minimal distros anyway. [6:36 AM] K-T Lim: Anyway, I think the bottom line is that Simon is probably right and we should remove the git install from newinstall.sh [6:36 AM] <USER> Yes. That's what I meant about my earlier comment. You already aren't trying to install everything from scratch [6:37 AM] K-T Lim: We should test the install without any git available   For developers, git should be a "system dependency" with a minimum version. [6:37 AM] <USER> As an aside, I'd really like eups to be able to "git clone" the repos during the build rather than download tar balls. It would make it a lot easier when I'm sitting in a build tree wondering whether a certain patch was installed or not. {quote}
Answer: 1361123.0

User story: "It'd be good to add some information about creating new repo to the DM Developer Guide. See relevant discussion in comments for DM-1491."
Answer: 2883888.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: pex_config seems to split out this confusing error message when trying to enable (i.e. append to .names) a registry item that doesn't exist: {code:hide-linenum}   File "/home/lam3/tigress/LSST/obs_subaru/config/processCcd.py", line 51, in <module>     root.measurement.algorithms.names |= ["jacobian", "focalplane"]   File "/tigress/HSC/LSST/lsstsw/anaconda/lib/python2.7/_abcoll.py", line 330, in __ior__     self.add(value)   File "/tigress/HSC/LSST/lsstsw/stack/Linux64/pex_config/9.0+26/python/lsst/pex/config/configChoiceField.py", line 72, in add     r = self.__getitem__(value, at=at) AttributeError: 'SelectionSet' object has no attribute '__getitem__' {code}
Answer: 58782.0

User story: "Learn Docker basics and then package a Qserv mono-node instance."
Answer: 2219815.0

User story: "Learn Docker basics and then package a Qserv mono-node instance."
Answer: 12980.0

User story: Installing Qserv on a cluster without internet access requires newinstall.sh to run in batch mode without installing Anaconda (whose install requires internet access). So Anaconda should have a {{-anaconda=yes|no}}. Usefulness of git {{-git=yes|no}} option, against full batch option answering "yes" everywhere could also be studied.
Answer: 2243359.0

User story: "Modify czar code: it should interact with the query metadata (store information for long running queries, retrieving)."
Answer: 1530775.0

User story: "Fine-tune the design outlined in DM-1251 (metadata for capturing information about running queries in Qserv.)."
Answer: 328029.0

User story: "While working on DM-1361 Mario committed a change that I was supposed to remove, but I didn't. This ticket is to fix that up."
Answer: 54.0

User story: "The Terminator thread is unnecessarily complex.   There's a simpler way to do what it does using Timer."
Answer: 7221.0

User story: "I'm seeing an issue in the ArchiveDMCS where the number of threads continue to increase until the limit is exhausted, and I get:  error: can't start new thread  "
Answer: 60563.0

User story: "Firefly uses clientsidegchart at https://code.google.com/p/clientsidegchart/ for XY plot. This package has not been updated since 2010. We need to find out more about other plotting packages and consider if we need to switch. The candidates are:  1. flot plotting library for JQuery. http://www.flotcharts.org/ 2. Highcharts JS at http://www.highcharts.com/"
Answer: 164159.0

User story: "Attend the annual  ADASS conference to keep up with the software development in the astronomy community.  <USER> <USER> Xiuqin Wu plan to attend the ADASS 24."
Answer: 12819.0

User story: "http://www.fig.sh/  coordinate with @GregDaues who is also investigating fig."
Answer: 2227193.0

User story: "MySQL password in written in multiple file during configuration procedure. One single file (QSERV_RUN_DIR/tmp/my.cnf) should be used, and removed at the end of configuration procedure. qserv-meta.conf also contains MySQL password and should be also secured (move password to qserv-configure.py cmd line?)."
Answer: 2381519.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: "Testing and improving the deblender is something that really needs to be done on real data of approximately LSST quality, and that makes HSC data a good choice.  But first we need to fix the bitrotted obs_subaru package so we can use the LSST stack (not its HSC fork) to process that data."
Answer: 2824.0

User story: In DM-1431 we demonstrated processing of sample data within Docker containers within an OpenStack instance.  Data was processed for containers based on CentOS6.5, Ubuntu 13.10, Ubuntu 14.10.  We consider a multi-platform "testing" scenario, where we process the sample data in numerous containers based on various platforms/OSs all simultaneously on an OpenStack instance.   This scenario entails starting up and managing multiple Docker containers.  Fig (http://www.fig.sh) is a new tool for starting up and managing services via Docker containers.   It is a common use case with Docker to have individual components of an application each run separately in a container (resulting in numerous  containers running on a node or cloud env, i.e., a 'Docker stack'), with the containers having linkages/dependencies to be managed. Fig may be used to encode the relationship between the containers in the Docker stack, and to start up such a set of containers.  We install and examine Fig, and apply Fig to our multi-platform "testing" scenario.   
Answer: 304784.0

User story: "I want to use obs_test to test processCcd, but it contains no imaging data. I will replace the current data with new imaging data (a portion of one LsstSim CCD), add a camera and rewrite the mapper (subclassing CameraMapper).  This also requires rewriting the unit tests in obs_test and in one other package that uses obs_test."
Answer: 22923.0

User story: "QSERV_RPC_PORT value must be checked in mysql-proxy instead of in init.d scripts. Same thing for QSERV_UNIX_USER, if doable."
Answer: 2250540.0

User story: Test the reverse mirror for beta-testers.  Straw man:  1. Break the mirror for anybody beta-testing github workflow 2. Mirror back to new gitolite area: "mirror")  Method:  https://help.github.com/articles/duplicating-a-repository/  
Answer: 122923.0

User story: "Write up the design developed on DM-829 and push it through review."
Answer: 14328.0

User story: "The code we ported from meas_algorithms sets the maxShift to 2 without regard to the config item which is supposed to set that value."
Answer: 44185.0

User story: "The test of PixelFlags in measureSources.py (from measAlg) requires a check to be sure that the center inputs are not NaN."
Answer: 3354.0

User story: "Additions to Jim's redesign to make it easier to define custom results."
Answer: 15696.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: This is a catch-all issue for any unit tests which got left in meas_algorithms.  It is hard in some cases to tell if a given test is intended to test something in meas_base (an algorithm or the framework), or something in meas_algorithms.  DM-1162 converted most of the obvious tests to meas_base, with the know exception of the "forced" tests in measureSources.py.
Answer: 2950.0

User story: <USER>at SLAC points out that we should expect to need to iterate quickly in Commissioning and early Production as we refine algorithms to meet the Science Requirements.    He feels these iterations are likely to involve publishing results to the community and obtaining feedback (including code fixes).  Trading off coverage in area or time and "certification-level" SDQA in favor of more and faster iterations on unofficial data subsets may be worth it, even to the extent of giving up a DR or two.
Answer: 3060635.0

User story: "<USER>at SLAC brought up the issue of completeness and systematics maps: how are they to be generated, how are they to be stored (compressed, since per-pixel values would be much too large)?  We have a little bit of a mention of fake objects in the [difference imaging|https://confluence.lsstcorp.org/display/DM/Level+1+Difference+Imaging+and+Moving+Object+Processing] design, but a detailed treatment of this is needed."
Answer: 1912383.0

User story: (K-T writing for Jacek) There will be multiple distinct (sometimes interacting) services running in the Archive and DAC to provide access to image data, other data files, catalog data, and metadata.  Should these live in individual repositories or be grouped together?  Note that they will definitely live in separate products/packages; this is only about git.  Arguments for individual: * Simultaneous changes across multiple services will be rare. * Tagging each service individually is desirable. * History is "cluttered" with changes irrelevant to the service being worked on. * More frequent rebasing is necessary as master merges happen faster.  (Could be ameliorated by working mostlly in a fork and having less-frequent pull requests, but poses a greater threat to system integration.) * Repo == product/package is easier to manage and understand.  Arguments for combined: * Fewer repos to track and manage. * Clear top-level structure for LSST code. * See [Winter2015 Package Reorganization Planning|https://confluence.lsstcorp.org/display/DM/Winter2015+Package+Reorganization+Planning] and recent [SAT meeting notes|https://confluence.lsstcorp.org/display/DM/SAT+Meetings]
Answer: 5572.0

User story: "Track versions of data inside zookeeper, and detect from Qserv code if Qserv code is compatible with given format of data."
Answer: 37805.0

User story: "Components of the AP simulator need to have their timing adjusted in a way that accurately reflects the running system.   This includes simulated processing time for jobs and the cadence at which messages are set."
Answer: 10056.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: "For now, Qserv databases are the same on the master and on the worker. It means that czar tables are created on the worker and vice-versa.  This ticket aims at creating the right tables at the right places, and also at sharpening permissions on these tables.  This is done by splitting configuration script qserv-czar.sh, which configure a mono-node instance, in two scripts: - qserv-czar.sh, for configuring the czar - qserv-worker.sh, for configuring workers.  see https://confluence.lsstcorp.org/display/DM/LSST+Database+Hangout+2014-10-29  Please note that this code can't be validated with mono-node integration tests (whereas it doesn't break them): indeed it requires a mono-node installation with 2 MySQL instance, one for the worker and one for the master. Updating the mono-node configuration and integration tests with such a feature would make them far more complex.  A quick and dirty, hard-coded, testbed is available in u/fjammes/DM-1446-test. It has been used successfully to test this ticket.  This ticket will also be validated during next Qserv install on in2p3 clusters."
Answer: 20353.0

User story: "Test absence of individual components of the AP simulator.  Bring each down, run the system, and restart just those components to see if the system still operates as expected"
Answer: 37622.0

User story: "Store review comments / PR discussion into relevant git repositories  Code & process to do this on a continuous basis post-transition will be a different issue, "
Answer: 180203.0

User story: "Extract comments from Atlassian Stash made during pull requests /code reviews and their associated SHA1s if it all possible.   "
Answer: 180205.0

User story: "Github currently has fixed 100MB per blob or 1GB per repo limits. Sims has at least one file in its repo whose history exceeds this (sims_meas) and this has been raised as an issue before.  Obtain a decision on a suitable way forward for the time being that would allow the upload of the repositories on Github. Experienced to be reviewed in a few months time to consider whether has proved satsifactory."
Answer: 180210.0

User story: "The Simulations team has requested that repos in general and the numerous DM repos in particular are prefixed in a way that would make fitering them out of searches and display easy (for example, their repos are prefixed sims_*)  This would be an evident useability aid to DM developers and outside contributors too.   Obtain a decision on how to allow users to quickly isolate repositories they are interested in. "
Answer: 131118.0

User story: "The afw package  uses a file named: test.fits in multiple testers.  If the user sets up the build to use multiple CPU (-j #), then there is the risk that the shared filename will be affected by more than one tester at a time.   In the case which provoked this Issue, the tester: testSimpleTable.py, reported that the file was missing.  A simple rerun managed to get past the error.  I recommend that the different testers use uniquely named demo files."
Answer: 34610.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: "Build a state diagram showing job progress throughout a run."
Answer: 430908.0

User story: "Install Qserv and test DB in local hosts.  Enable SUI team members to access the catalogs. "
Answer: 25132.0

User story: "We need have Qserv and the test DB in IPAC to do development and test locally, to access the  data through Qserv APIs."
Answer: 164.0

User story: "Process sample sdss data, starting with the lsst_dm_stack_demo, with LSST Stack in a Docker container in an OpenStack instance. "
Answer: 4326.0

User story: "Based on input from review of DM-1338, and discussions at hangout https://confluence.lsstcorp.org/display/DM/LSST+Database+Hangout+2014-10-29: implement -keepdata option.  * --keepdata will preserve qserv_meta.conf and my.cnf. Regarding the latter, this is necessary because user might have customized data_dir. * The structure of qserv_meta.conf and my.cnf must remain the same between existing version of Qserv and the to-be-configured version of Qserv. It is users's responsibility to ensure the structure did not change. Note in particular, the template files (with the exception of my.cnf) should not be customized"
Answer: 265821.0

User story: "DM-1338 may allow to switch Qserv or dependency version using eups, without having to re-configure Qserv (i.e. without any change in QSERV_RUN_DIR).  There may have conditions for this to work. That's why it's reasonable to get some user feedback on DM-1338 before documenting this feature."
Answer: 2436735.0

User story: "We create a persistent volume of Cinder block storage and attach to working instance.  When it was created, the instance does have a specified amount of ephemeral disk, but this disk will be destroyed with the instance.  We want to test that we can create a persistent volume of block storage, attach it to an instance, format the storage with a file system, and mount the volume for use with processing, where data/output can be retained after the instance is destroyed. "
Answer: 8744.0

User story: "I just ran into an issue with include guards when working in a package with both afw and [GalSim|https://github.com/GalSim-developers/GalSim] --- both use the same include guard names (e.g., {{IMAGE_H}}, {{ANGLE_H}}), which means some headers I needed weren't being included.  I suggest that these should be prepended with the package name and path (e.g., {{AFW_IMAGE_IMAGE_H}}, {{AFW_GEOM_ANGLE_H}}) or something similar to ensure they are distinguished.  This might be something for the SAT to discuss and set a policy on.  See [GalSim #608|https://github.com/GalSim-developers/GalSim/issues/608] for the flip side."
Answer: 184.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: "Qserv packaging procedure requires to often rebuild Qserv and relaunch integration tests.  IN2P3 Openstack platform offer next virtual machines :  {code:bash} [fjammes@ccage030 ~]$ nova flavor-list {code} | ID | Name              | Memory_MB | Disk | Ephemeral | Swap | VCPUs | RXTX_Factor | Is_Public | | 1  | m1.tiny           | 512       | 0    | 0         |      | 1     | 1.0         | True      | | 15 | cc.windows.small  | 4096      | 20   | 0         |      | 2     | 1.0         | True      | | 16 | cc.windows.xlarge | 8192      | 50   | 0         |      | 4     | 1.0         | True      | | 2  | m1.small          | 2048      | 10   | 20        |      | 1     | 1.0         | True      | | 3  | m1.medium         | 4096      | 10   | 40        |      | 2     | 1.0         | True      | | 4  | m1.large          | 8192      | 10   | 80        |      | 4     | 1.0         | True      | | 5  | m1.xlarge         | 16384     | 10   | 160       |      | 8     | 1.0         | True      | | 6  | cc.lsst.medium    | 4096      | 20   | 40        |      | 2     | 1.0         | False     | | 7  | cc.lsst.large     | 16384     | 20   | 160       |      | 8     | 1.0         | False     | | 9  | cc.lsst.xlarge    | 40000     | 20   | 160       |      | 20    | 1.0         | False     |  cc.lsst.xlarge would allow a quick build/test of new Qserv release."
Answer: 2266983.0

User story: "Building on issues DM-1317 and DM-1375 where initial images and Dockerfile's were constructed, we can now use these Dockerfile's as prototypes to extend the set of Dockerfiles & images.  We observe that by making  simple (scriptable) edits to the initial Dockerfile, we can run 'docker build' to make docker images for several combinations of OS and base compiler gcc version."
Answer: 69757.0

User story: "meas_modelfit provides a unit test written in fortran and and the build fails on MacOS if gfortran is not available. I don't believe gfortran is a permitted dependency. Certainly it does not show up on <https://confluence.lsstcorp.org/display/LSWUG/Prerequisites> for MacOS.  On the other hand, it does show up as a dependency for all the unix variants, which is odd.  If gfortran is permitted, then this ticket should probably be against that web page. If it snot permitted, please fix the package so that the package can be built without gfortran. Several options come to mind, including: - Convert that code to C code - Skip the test if gfortran is not available - If possible, pre-compute the output from the fortran test, instead of building and running it as part of the build"
Answer: 259.0

User story: "Please add meas_modelfit to the list of components"
Answer: 353.0

User story: "Use of the Git repo: contrib/demos/lsst_dm_stack_demo  by Buildbot should acquire that repository from a user specified branch. Currently it acquires the repo only from the master branch."
Answer: 479185.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: Need to implement deleting databases. Deliverable: a design of the system that will be capable of deleting a distributed database including all copies of that database on all workers, all replicas of all chunks are deleted. It should be possible to "create database x" at any time later.
Answer: 542211.0

User story: "The v1 implementation (DM-1249) transitions the zk access from the c++ layer into python, with code that understands how to unpack json-encoded data. This can coexist with the existing qserv_admin zk schema. v2 applies packing/unpacking logic in the creation/manipulation code in qserv_admin. v2 scope will be defined further, once DM-1249 enters review.  Update: Phase 2 includes removal of c++ zk code and unification of Qserv css modules into a single place."
Answer: 57467.0

User story: "Create an LCR, including a summary of changes, for LSE-68."
Answer: 18335.0

User story: "Once we've detected Sources in multiple bands we need to merge the positions to generate Objects.  This is a little complicated (or at least messy):  - The positions have errors  - If the seeing is different in different visits, objects may be blended in some but not all exposures  - If we use more than one detection pass (e.g. smoothing when looking for faint objects, not smoothing for bright) this has similar-but-different consequences (but we should probably deal with in the per-band processing)  - Objects move, so even if the positions are within the errors the motion may still be detectable "
Answer: 148123.0

User story: "The current concept of the deblender assumes that the inputs are  - A merged set of Footprints that define which pixels are part of the blend  - A merged set of Peaks within that merged Footprint  Please generate these merged Footprints (which will be defined in (x, y) coordinates in the tract/patch coordinate system). "
Answer: 148123.0

User story: "(Cf. [HSC-1024|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1024])  One poor-man's approach to deblending multiple bands and visits is  - Deblend in one band (or a combination, e.g. chi^2 band)  - Fit models in that band  - In all bands separately fit those models simultaneously to all object in the blend, allowing only a minimum of coefficients to float (ideally only amplitudes, but given the realities of real galaxies the bulge and disk will need to both be fit, or the Sloan Swindle components, or the Lensfit Swindle, or ...).  The correct PSF for each image would be used.  It will probably be necessary to include undetected objects in this fit (cf. [HSC-1023|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1023]), using point-source models.  It is not clear how much of a poor-man's solution this actually is, or whether it will work quite well."
Answer: 148152.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: "(See also [HSC-1025| https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1025])  One poor-man's approach to deblending multiple bands and visits is - Deblend in one band (or a combination, e.g. chi^2 band) using an SDSS-like algorithm that produces templates for each child - Take the templates (or possible model fits to those templates) and use them to deblend the objects in all other bands  It will probably be necessary to include undetected objects in this fit (cf. [HSC-1023|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1023]), using point-source models.  Note that this does not allow for the different seeing in each band.  This is not obviously catastrophic for reasonably wide blends as the total flux in each pixel is conserved, and if only one template is important near an object's centre the exact form of the template is unimportant."
Answer: 148191.0

User story: This ticket has been split off from DM-1358 which was usurped by a bug fix embedded within the story details.  That bug fix was already pushed into the devenv/buildbot/DM-1358 branch.  So this totally separate task is being moved to this new Issue.   _______________________________________________________  The output of demo2012 results in an output file which is compared against a benchmarked file. Currently the comparison allows a deviation from the benchmark based "on the the number of digits in the significands used in multiple precision arithmetic"; that number is currently set to 11.    An example using that setting is:  {code}  @ Absolute error = 5.9973406400e-1, Relative error = 9.1865836000e-4  ##2566 #:25 <== 29.7751550737  ##2566 #:25 ==> 29.7478269835  {code}  Additionally, the current use returns: a 'Fatal' error if the code itself fails to execute correctly; a "Warning' error if the any of the benchmarked quantities do not meet the comparison criteria; 'Success' if the comparison meets all criteria.    It is recommended that the comparison 'should be set to zero tolerance until we get some breakages and people discover what level of changes occurs as part of "everyday" development.    Those breakages should be on branch builds, of course, not on master.'    This Issue will:    *  reset the comparison metric to EQUALS.  
Answer: 1222771.0

User story: "The LSST buildbot infrastructure recently changed to building everything with --std=c++0x, which broke the partition package, and hence automated Qserv builds. While debugging this, I discovered that the partition package does not build on OSX 10.9, and considering how minimal its dependencies are, it really should. The OSX issue can be fixed by avoiding {{using boost::make_shared}}.  The partition package should be cleaned up to avoid all use of {{using}}. If we decide to use C++11 in Qserv, then the codebase should also be modernized (in particular, there are use-cases for static_assert, nullptr, etc... ). "
Answer: 122019.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: "Make a Dockerfile for systematic generation of docker images using a Centos6.5 base image  containing the LSST Stack (v9_2 at the moment) and library dependencies."
Answer: 12.0

User story: afw unit test background.py fails when using anaconda 2.1.0 as follows: {code} tests/background.py  .......F.............. ====================================================================== FAIL: testBadPatch (__main__.BackgroundTestCase) Test that a large bad patch of an image doesn't cause an absolute failure ---------------------------------------------------------------------- Traceback (most recent call last):   File "tests/background.py", line 602, in testBadPatch     self.assertEqual(np.mean(bkgdImage[0:100, 0:100].getArray()), defaultValue) AssertionError: 10.000002 != 10  ---------------------------------------------------------------------- Ran 22 tests in 4.373s  FAILED (failures=1) {code}  (For the record, I think this is why the test fails on tioga ~<USER>lsstsw: I updated the anaconda to fix an fftw build failure)
Answer: 1127.0

User story: "sconsUtils state.py tests a compiler for C++11 support and sets a compiler flag accordingly. Unfortunately it sets CCFLAGS instead of CXXFLAGS (my foolish error)."
Answer: 2.0

User story: "The current lsstsw installs anaconda 1.8.0, which is so old that pip doesn't work with it (due to a security vulnerability in openssh). Can we update to the current version of anaconda?"
Answer: 1394.0

User story: In file build.py a variable named "eups" is used, but that code also needs access to the package named eups. Please rename to the variable to avoid confusion and shadowing.
Answer: 365.0

User story: A recent change to eups (not exporting the setup and unsetup functions, 119236b) broke lsst_build: in particular, the build file "_build.sh" that it creates will not work because "setup" is undefined.  To see this, use lsstsw to try to build a stack. It fails on cfistio.  Robert suggests that _build.sh source setups.sh
Answer: 58.0

User story: "When running vanilla lsstsw on MacOS it uses all available cores. This make the compute unusable for anything else (even simple text editing). Would you consider using all but one or two cores, instead? I've been manually configuring the latter for scons. That leaves the machine unresponsive while building external packages, but its usable while building scons packages."
Answer: 2525477.0

User story: SdssCentroid has a "bad data" flag that doesn't actually convey any information about what went wrong.  This should be replaced with one or more flags that provide more information.
Answer: 244606.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: "See https://jira.lsstcorp.org/browse/DM-1258?focusedCommentId=29230&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-29230.  {{~/.my.cnf}} is used by css watcher, an optional tool used for monitoring css. It is a symlink to $QSERV_RUN_DIR/etc/my-client.cnf.  The css watcher could use MySQL credentials located in ~/.lsst/qserv.conf (used by integration tests wich are a Qserv/MySQL client)"
Answer: 2285020.0

User story: Deliverable: circulate a Word-based draft of LSE-68 in which the "push" interface is removed, and the "pull" interface is refined to include the guider and other Summer 2014 work.  Note that the use of "pull" for the guider applies whether or not the proposed guider redesign is accepted.
Answer: 26697.0

User story: "This ticket is for changes to our build system so that C++11 is used by default, rather than as an option  Necessary changes include: - boost must be built with C++11 - sconsUtils must always build with C++11 (right now it is an option)  This ticket allows us to make the necessary changes and test them, then merge to master. A fancier alternative is to create a way to tell the whole build system which C++ standard we want to use (one that would apply to packages built using bjam and perhaps make) and then modify sconsUtils to use that. However, I suspect that's too much work and would likely be fragile unless we could figure out a way to enforce a rebuild of all necessary packages when the setting was changed.  A centralized way to get the desired CXXFLAGS for the user's compiler would be helpful."
Answer: 5797.0

User story: "Some of the more minor issues raised in comments from DM-199 were left undone prior to merging. This ticket addresses them.  For more information, please see:  https://github.com/LSST/qserv/pull/2 . "
Answer: 1505.0

User story: "While using it as an example for the redesign of DM-829, I came up with some ideas for how to improve PsfFlux's handling of edge/bad pixels:  - Add a flag indicating that at least one pixel was rejected  - Add thresholds (number? fraction of PSF model size?) for how many non-rejected, non-edge pixels we need to even attempt a fit."
Answer: 119268.0

User story: "When we need to make modifications to the demo script and/or its expected results to account for a change in the pipeline, it'd be nice to be able to test that with buildbot on a branch before merging to master.  Currently, however, buildbot always uses the master branch of the demo package, rather than the branches provided when starting the build."
Answer: 1951718.0

User story: setups.sh assumes that you can export a shell function.  Not only is this not in posix, it's also unnecessary.  Please modify mksetups to remove the "export -f ..." statements.  Also, switch the [[ ... ]]] statements to use standard shell syntax.   Once these changes are made, setups.sh should work with all posix-compliant bourne shells (sh, bash, dash, ksh, zsh, ...) 
Answer: 1217.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 already touched question about installation directory structure at a meeting, maybe we can improve things by re-arranging how things are installed      we are currently installing stuff into four directories: cfg, bin, lib, proxy     to make it look more standard and to avoid clash with qserv source directories we could move cfg and proxy to a different location (something like share/qserv to make it more root-install-friendly in case we ever want to install under /usr)     this change (if you want to do it) deserves separate ticket, do not do it in this ticket "
Answer: 836116.0

User story: "Install docker 1.1.2 in an ISL OpenStack CentOS 6.5 instance, and perform  basic checks such stopping and starting the docker daemon, changing default settings such as size limit of containers/images,  pulling  standard images from docker hub, starting containers from these images, etc. "
Answer: 22807.0

User story: An RFC email I sent to lsst-data proposing a change in how flags are handled in catalog slots generated more calls for a wider redesign than I anticipated, and I think this reflects broad (but perhaps not acute) problems in how we currently approach "substitutable" algorithms.  I'd like to have a review of our current approach and brainstorm new ones, and I think the SAT is the right venue for that.  Mandatory participants include at least [~<USER>, [~price], and [~<USER>.
Answer: 149610.0

User story: "The ORIGINATORID is a 64-bit word consisting of an IPv4 host address, 16-bit process id, and 16-bit local value.   In addition to the 16-bit process id not being standard across platforms (Mac OS >Leopard goes to 99999), the churn rate for the local value should be much higher than just 16 bits.  This could be fixed to changing ORIGINATORID to a 32-bit process id and a separate value for the local value, which would be specified together in the DM event selector.   I have to look into this more to see if this is a viable solution.  This might need to go to three separate values to future proof it (i.e., ipv6)."
Answer: 159846.0

User story: I'm seeing two unit test failures in ctrl_events on MacOS with clang 6. K-T diagnosed this as assuming process IDs are only 16 bits when in fact they can be longer.  {code} tests/DestinationId.py  Traceback (most recent call last):   File "tests/DestinationId.py", line 59, in <module>     assert processId == os.getpid() AssertionError {code}  and  {code} tests/OriginatorId.py  Traceback (most recent call last):   File "tests/OriginatorId.py", line 56, in <module>     assert processId == os.getpid() AssertionError {code} 
Answer: 227.0

User story: "There are some obsolete classes and code in the ctrl_events package that needs to be removed and/or updated.  PipelineLogEvent, for example.   That not only is no longer used, but it is applications specific, and should have been part of another package in the first place, subclassed from this package."
Answer: 253106.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 marshaling code for non-standard (i.e., non-filterable) components of messages is custom and not standard.  Change this to use JSON."
Answer: 92195.0

User story: "The tests for this package predate the unit test framework that other package use.  Update the tests to uses the unit test framework and get rid of any duplicate  or obsolete tests."
Answer: 159899.0

User story: "The current Event.cc base class needs to be refined to remove and old-style data release terms that aren't used anymore.  Plus, it needs to be easily extensible to allow other types of dictionaries of terms that will be used in the message headers to make them filterable on the server side."
Answer: 159901.0

User story: "Write some example programs to get familiar with the OCS middleware software. The OCS middleware will later be integrated with the AP, in the base dmcs and replicator jobs."
Answer: 70262.0

User story: "Attend OCS Middleware workshop.  This will probably have be done remotely because I have a personal conflict with that time that will prevent me from attending in person."
Answer: 64558.0

User story: "Define gather/scatter mechanism for tasks with generic API.  This will use event services (DM Messages) initially, but we would like to support MPI or other communication mechanisms as well.  This will involve consulting with Paul about how the existing code is structured. "
Answer: 1304345.0

User story: "Write unit tests for DM message appender class.  This might also require some tests for a configurator class, if that class is created."
Answer: 211509.0

User story: "Write DM message appender class to be used with log.git package.   This might entail writing a configurator class as well;  that depends on the investigation of how configurations/appenders are used."
Answer: 272093.0

User story: "In order to be come more familiar with how to use the log.git package, write some tests to see how existing configurations and appenders are used by the log.git package."
Answer: 205634.0

User story: "Read through the log4cxx documentation and become familiar with how the log.git package is set up."
Answer: 171026.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: Ticket related to Mario email (subject: [QSERV-L] Some points/actions from the discussion today) :  Making your "qserv data" directory independent of where qserv is installed   I think this is a big one, and largely independent of EUPS. You have a problem where you want to use one set of test data potentially with different qserv binaries (not at the same time, of course). I'd argue you should refactor the scripts generated by qserv-configure to either:   * get _all_ their information about various paths from a _single_ file, for example, from etc/paths.cfg.sh. Then you can easily regenerate just that file when you need to switch to a different qserv (or zookeper, or what not), or... * refactor the generated scripts to learn from the environment which binaries to run. I.e., if $QSERV_DIR is defined, use that qserv, etc. This will let you switch binaries by simply setup-ing the new one with EUPS.   The two are not mutually exclusive -- e.g., all of this logic could be in etc/paths.cfg.sh, and depending on whether this is a development build or a "non-EUPS" build, it can either pick up the paths from the environment or hardcode them.   Assuming you did that, your development loop may look something like this:   {code}     # assuming that qserv-configure.py has already been run     # in ../qserv-run       # do something with qserv-a clone     cd qserv-a     setup -r .     ... do some edits ...     scons       # now do the tests     cd ../qserv-run     ./bin/qserv-start.sh     ... do tests ...     ./bin/qserv-stop.sh       # now switch to qserv-b clone     cd ../qserv-b     setup -r .       # and do the tests again     cd ../qserv-run     ./bin/qserv-start.sh     ... do tests ...     ./bin/qserv-stop.sh  {code}  that is, as qserv-start picks up the relevant products from the environment, there's no need to rebuild/reconfigure the qserv-rundirectory each time. 
Answer: 40977.0

User story: "get a draft Project Office detail plan consistent with the level of devleopment of the master plan. (ephiphian). Draft a data classification plan, refer to plan and classes of data in drat materials. Obtain some central place in LSST documentation framework to hold materials being drafted (if supported by the LSST system) Recieve feedback based on portion of plan submitted to LSST project office. Incorporate feedback. (if minor) re-plan (if major)"
Answer: 2827380.0

User story: Consult with M. Freemon on the sizing model given the generic description of the computing needed tier-3 and tier-2 support. Make a pass through the underlying data center standards doc for things  "any competent designer should know"  for example wall plugs on separate circuits form computer circuits.  add that to the document, and call meeting of working group for review in late Oct.
Answer: 2827385.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 see that in working with the Horizon GUI, it is fairly straightforward to give an instance a public IP address by associating a Floating IP with the current local IP.    However, we will want to be able to accomplish this task both remotely and programmatically within workflow.  As a step towards this, we target the solution of this via the nova CLI."
Answer: 160775.0

User story: "A new version & implementation of the ISL OpenStack testbed is up and running. The new cloud is using IceHouse, the ninth OpenStack release. We get started on this platform by verifying that basic instance creation is working.  We target the creation of an instance through the (Horizon) GUI interface,  and via the nova CLI. "
Answer: 13.0

User story: After changing the implementation of GaussianFlux to use the shape slot rather than estimate the shape itself by re-running the SdssShape code, Perry saw a 5-15% difference in the fluxes (I'm not sure of the sign).  The new behavior (using the shape) is consistent with what we'd have gotten with the old code when the little-used "fixed" config option was enabled (not surprising, as that just looked up the SdssShape measurement by name, instead of via slots).  I suspect the difference is coming in because of the factor of two between SdssShape's "raw" measurements - the actual Gaussian-weighted moments - and the factor of 2 it applies to make its measurements equivalent to ideal unweighted moments.  The correct weight function to use for GaussianFlux includes this factor of 2 (i.e. it's larger than the "raw" moments), and it's likely either the old code wasn't including this or the new code isn't.  We need to determine which one, and if necessary, fix the new code.
Answer: 167092.0

User story: "GaussianFlux relies on the shape slot, and puts noisy warnings in the logs when the shape slot fails.  However, we probably don't want to add a new flag for GaussianFlux to indicate this failure mode, because it'd be entirely redundant with the shape slot flag.  We should figure out some other way to squash this warning - how we do that may depend on whether this is addressed before or after the C++ redesign.  We should also consider having GaussianFlux add an alias to the schema to point back at the shape slot flag, creating what looks like a specific flag for this failure while actually just being a link back to the shape slot flag.  That's probably not worth doing within the current C++ interface, however, as it'd require some unpleasant mucking around with ResultMappers."
Answer: 23728.0

User story: "SdssCentroid doesn't trap exceptions that are thrown due to being too close to the edge, resulting in noisy warnings in the logs.  Instead, it should catch the low-level exception and re-throw as MeasurementError, after defining a flag field for this specific failure mode."
Answer: 9908.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "This is a task of deciding the new client mounts for the 3 new NFS servers.  These should match up with the new storage hierarchy and classification <https://wiki.ncsa.illinois.edu/display/LSST/Storage+Structure>."
Answer: 172844.0

User story: "We are waiting on the UIUC Business Offices to provide us a new account number for ordering these servers.  As soon as we get that account number we need to order the hardware from KOI Computing."
Answer: 172861.0

User story: "Replicator jobs that receive no data specifically for the visit, raft, and exposure sequence ID within a certain amount of time should self expire to prevent future jobs from running.  If this is not done, jobs will back up in the HTCondor queue."
Answer: 31645.0

User story: "This would be configuring to work vSphere, setting up permissions and groups, adding datastores, and testing the use of the new setup."
Answer: 2333890.0

User story: "In instances where the files the worker expected to get never arrive, there should be a way of the worker to recognize this (say, a timeout after waiting for the Archive DMCS for some time), and exit."
Answer: 31449.0

User story: "Once the new VM compute nodes arrive, the hardware needs to be installed, ESXi installed, and networked for use by vSphere."
Answer: 2333893.0

User story: "We expect the primary datastores will be local to the VM compute node, but this NFS datastore will allow us to live migrate a handful of VMs between compute nodes.  We may also use this or another datastore as place to create backup snapshots of particular VMs."
Answer: 2333895.0

User story: "Update the expected outputs in the SDSS DM stack demo repo to match what we expect from the new meas_base framework."
Answer: 5581.0

User story: "Create an installation of the LSST Stack v9_2  within a Docker Image for ubuntu for easing the import of LSST software into an OpenStack instance,  We create  the image utilizing a Dockerfile to make systematic  the creation of such images. "
Answer: 10422.0

User story: "Deploy the LSST Stack within OpenStack instances within the ISL testbed -- this could be for multiple flavors CentOS, Ubuntu, etc, and this could be done by pulling Docker Images to the instances.   There will also likely be some initial debugging of starting instances within the ISL platform as a new installation has been stood up Sept 2014. "
Answer: 161356.0

User story: In order to publish this version please tag Qserv master tip with "2014_09.0" and then run: {code:bash} ssh lsstsw@lsst-dev # command below can't be runned in buildbot, as it doesn't support qserv_distrib build rebuild -t 2014_09.0 qserv_distrib # bXXX is provided by previous command publish -t qserv -b bXXX qserv_distrib publish -t 2014_09 -b bXXX qserv_distrib {code} 
Answer: 14452.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: "LSE-69 declares that there are two categories of Conditions data (telemetry) required by DM from the Camera: those items that are needed for Alert Production (for which the AP components at the Base will need a whitelist, and for which the Camera has a tighter latency requirement), and those that are not (but are then presumably needed in DRP or other deferred productions).  It states that the subset needed for AP should be enumerated in LSE-130.  The action here is to create an initial version of that list."
Answer: 473867.0

User story: "Brian Selvy is producing a SysML version of the LSE-72 updated edited by [~<USER>.  The action here is to proofread the docgen of that version once it is ready."
Answer: 157431.0

User story: "Covers entering the contents of the LSE-69 update into EA as SysML, with associated updating of diagrams, and the creation of a docgen'ed version for CCB action."
Answer: 55397.0

User story: "Create a change request to bring LSE-69 up to date and capture the Summer 2014 work."
Answer: 32153.0

User story: "A meeting around 9/26/2014 agreed on a set of revisions to LSE-69, with some language still needed from [~<USER>.  This action is to edit the tracked-changes Word version of LSE-69 containing the notes from that meeting into a final copy that can be reviewed by the Camera team and used as input to editing the SysML version of the ICD."
Answer: 32154.0