Hey Guys, I am going to take a crack and the task of mapping A1 -> B1 that Chris mentioned since I have been making JIRAs and wishing for some other components in the list. Since the new OCW refactoring introduces some new software modules/components i think it makes sense to align JIRA issues with each area of the code. This helps map issues to modules in the code, items tasks that touch large sweeping parts of the code should go under 'general' and they need a closer look since they are probably taking on too much work and need sub-tasks or should be broken into smaller chunks.
rcmed -> data_source (this would also relate to ESG work or developing an interface to OpenDAP moving forward) rcmet -> None (just drop this from the OCW issue tracker. RCMET is a JPL project that is built on OCW) rcmet ui -> webapp (The 'ui' is basically AngularJS and Bottle. Webapp is generic enough that we can change to Ember.js and CherryPy if we like) regridding -> dataset_processor (map to the module that does this function) visualization -> plotting (map to the module that does this function) documentation -> NEW Component dataset -> NEW Component A note about rcmet above: Here are 14 open issues with rcmet as the component and what I think a reasonable mapping could be: (general) CLIMATE-261 Consolidate Code that converts a String into a Datetime Object (general) CLIMATE-259 Create branch to refactor updates to ui/services to support multiple metrics/plotting (documentation) CLIMATE-258 Improve Evaluation documentation (dataset) CLIMATE-219 Add name attribute to Dataset (metrics) CLIMATE-218 Update metric handling in Evaluation to coincide with new Metric definition (general) CLIMATE-217 Add metrics.py for OCW refactoring (general) CLIMATE-214 Add evaluation.py to OCW (dataset_processor) CLIMATE-179 Add support for Observation/Reference option when doing Spatial Regridding (general) CLIMATE-137 OCW refactoring code (general) CLIMATE-50 RCMET needs to use a logger instead of prints (general) CLIMATE-49 Add the 'obs' regrid option into toolkit.do_data_prep.prep_data function (REMOVE) CLIMATE-47 precipFlag attribute within the Model class needs to be refactored - Not an issue with OCW Dataset Class (general) CLIMATE-8 CLIMATE-7 SubRegions Support (metrics) CLIMATE-7 Refactor the metrics.metrics_plots function Thanks for allowing me to bump this thread to top of your inbox. -Cam On Fri, Aug 16, 2013 at 11:09 AM, Mattmann, Chris A (398J) < [email protected]> wrote: > Perfect > > Sent from my iPhone > > On Aug 16, 2013, at 10:49 AM, "Michael Joyce" <[email protected]> wrote: > > > If people need to catch up on the refactoring that's been occurring they > > can find the original proposal for refactoring at [1]. The full thread > > where this was discussed can be found in the mail archives at [2]. The > wiki > > entry that Mazi made detailing proposed package layouts (including the > one > > we ultimately went with) is available at [3]. > > > > To summate: > > > > The old code (which was called RCMET) is being refactored into the ocw > > package with the intention of making the code base more maintainable and > > the API nice and pretty. > > > > Hopefully this is sufficiently verbose. I don't have the time to go into > > more detail at the moment. If anyone is confused feel free to ask away > and > > I'll try to elaborate later!! > > > > Thanks > > Mike > > > > > > [1]: http://s.apache.org/RKI > > [2]: > > > https://mail-archives.apache.org/mod_mbox/incubator-climate-dev/201306.mbox/browser > > [3]: > > > https://cwiki.apache.org/confluence/display/CLIMATE/Open+Climate+Workbench+API+summary > > > > > > -- Joyce > > > > > > On Fri, Aug 16, 2013 at 10:12 AM, Mattmann, Chris A (398J) < > > [email protected]> wrote: > > > >> Can you detail "the refactoring" so everyone on the list here knows what > >> you are talking about? > >> > >> A few paragraphs would be great, Mike, thanks. > >> > >> Cheers, > >> Chris > >> > >> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > >> Chris Mattmann, Ph.D. > >> Senior Computer Scientist > >> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA > >> Office: 171-266B, Mailstop: 171-246 > >> Email: [email protected] > >> WWW: http://sunset.usc.edu/~mattmann/ > >> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > >> Adjunct Assistant Professor, Computer Science Department > >> University of Southern California, Los Angeles, CA 90089 USA > >> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > >> > >> > >> > >> > >> > >> > >> -----Original Message----- > >> From: Michael Joyce <[email protected]> > >> Reply-To: "[email protected]" > >> <[email protected]> > >> Date: Friday, August 16, 2013 10:07 AM > >> To: dev <[email protected]> > >> Subject: Re: JIRA component names > >> > >>> The 3 that caught my eye were: > >>> > >>> rcmet > >>> rcmet ui > >>> rcmet > >>> > >>> As to what they should be instead I don't know. 'rcmet ui' could > easily be > >>> 'ocw ui' without loss of clarity. With the refactoring I don't know > what > >>> we > >>> want to call 'rcmet' and 'rcmed' doesn't seem like it needs to be > there at > >>> all, so I don't know if we need to think of an alternative. > >>> > >>> > >>> > >>> -- Joyce > >>> > >>> > >>> On Fri, Aug 16, 2013 at 9:46 AM, Mattmann, Chris A (398J) < > >>> [email protected]> wrote: > >>> > >>>> Can you be more specific and propose e.g., : > >>>> > >>>> A1->B1 > >>>> A2->B2 > >>>> .. > >>>> > >>>> Where A is the set of "JPL/RCMES centric" names and B is the new > >>>> proposed one? > >>>> > >>>> Cheers, > >>>> Chris > >>>> > >>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > >>>> Chris Mattmann, Ph.D. > >>>> Senior Computer Scientist > >>>> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA > >>>> Office: 171-266B, Mailstop: 171-246 > >>>> Email: [email protected] > >>>> WWW: http://sunset.usc.edu/~mattmann/ > >>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > >>>> Adjunct Assistant Professor, Computer Science Department > >>>> University of Southern California, Los Angeles, CA 90089 USA > >>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> -----Original Message----- > >>>> From: Michael Joyce <[email protected]> > >>>> Reply-To: "[email protected]" > >>>> <[email protected]> > >>>> Date: Friday, August 16, 2013 9:31 AM > >>>> To: dev <[email protected]> > >>>> Subject: JIRA component names > >>>> > >>>>> Some of our JIRA components are very JPL/RCMES-centric. What does > >>>> everyone > >>>>> think of switching these over to something more generic? Ideas on > >>>> names? > >>>>> > >>>>> -- Joyce > >> > >> >
