Thanks, François! I'll look forward to getting your suggestions. Julie
Francois Fortin wrote: > Hi Julie, > > From now on we will do a reply to [EMAIL PROTECTED] This way our > discussion will be broadcast to other develloper. > > I would prefer method 1 or 2. If you prefer method 3 its not a problem > but maybe we can add method 2 also to force a particular file type. > > We would like to integrate it in METRo. It would be a great feature to > have. > > I will look at the source code a bit before sending you my suggestion. I > will try to do that by the end of the week. > > Thanks > François > > Julie Prestopnik wrote: >> Hi François. I working on the design right now. My plan was to use the >> python debugger to step through the METRo modules from the very >> beginning of program execution to see what modules would need to be >> modified/added. >> >> My co-workers and I discussed the various options for letting METRo know >> that it is being given a new type of input/output file and we came up >> with three possible ways: >> >> 1. Changing the command line options. For example, having >> "--input-forecast-csv filename" instead of "--input-forecast filename" >> (Note the addition of the -csv at the end of the option) >> >> 2. Adding another option to METRo. For example, "--input-file-format >> filetype" and "--output-file-format filetype", with filetype being >> either "xml" or "csv". >> >> 3. Pushing the check further down. For example, once the filenames are >> loaded in, check for a .xml or .csv extension and proceed as necessary. >> >> I don't think we really have a preference on which one to use. >> Personally, I'm somewhat fond of the third option, because the interface >> to METRo would not change, however, then it restricts the user in their >> choice of input and output filenames. Do you have a preference? >> >> Regarding your question of knowing exactly what to do to allow for the >> different input format, like I said, I've started using the debugger to >> step through the code and have been making notes along the way of what >> code appears to need modification. Then, I was going to dive in, start >> making changes, and hope for the best. ;) >> >> Any suggestions from you would certainly be appreciated. Is this >> something you would consider integrating into and maintaining in >> MetSurface if I get it working? >> >> Thanks, >> Julie >> >> Francois Fortin wrote: >> >>> Hi Julie, >>> Do you have an idea how to do that? I have one but I will need some time >>> to look at that. >>> >>> Julie Prestopnik wrote: >>> >>>> Hello METRo developers. >>>> >>>> We (NCAR) are considering adding an option to allow for a new input >>>> format (CSV) to METRo, since the XML I/O consumes most of the >>>> processing >>>> time. We'd like to add an option, either by adding to or changing the >>>> command line interface or by pushing the check further down (e.g. >>>> checking for file extension: .xml or .csv). >>>> >>>> We wanted to run this by everyone to see if you might have any input, >>>> suggestions, or objections. >>>> >>>> Thanks, >>>> Julie >>>> >>>> _______________________________________________ >>>> METRo-developers mailing list >>>> [email protected] >>>> https://mail.gna.org/listinfo/metro-developers >>>> >> >> > _______________________________________________ METRo-developers mailing list [email protected] https://mail.gna.org/listinfo/metro-developers
