[OpenMadrigal-developers] new global search report (fwd)

[William Rideout]

Shunrong and I discussed his needs for global searching, and we decided 
that what he needs is a global search application.  The present global 
search web interface is designed to be interactive, with the assumption 
that its not done often enough to require automation.  Shunrong needs an 
automated approach to global searching, so there's no need for any web 
interface.

So my plan is to write a new application called globalIsprint.  It will 
have a command line very similar to isprint's, except that instead of 
specifying a single file, there will be extra arguments to limit 
instruments, kindats, seasons, and Madrigal sites to search.  Unlike the 
present global search, which returns quickly and the user later receives 
an email when things are done, this application will be synchronous 
(since it is assumed the user is running it in batch mode).  As 
requested by Shunrong, one of the report formats will be pure data, 
without any blank lines or metadata.

Implementation:  It seems natural to use the new web services described 
below to implement this application, since we want it to work seamlessly 
across all Madrigal sites. No new web services are required - the 
application would simply call isprintService for every file that meets 
the selection criteria.  Even when searching a local Madrigal site, 
there is not a large performance difference when using isprintService 
via http and using isprint directly.  I'll write the application in 
python, not Matlab, since there is really not much in the Matlab API 
except kludgy parsing that can be done in python in 4 lines or less. 
This should be a pure python application, which means it should run 
anywhere python is installed (Windows or Unix).

Please let me know your thoughts.  If this idea seems okay, I'll send 
out a complete description of the command line arguments.

Bill


Shunrong Zhang wrote:
> Bill,
> 
> When you update Hyperion with the newest version of Madrigal, could you
> consider also update the output format issue for the global search that I
> mentioned sometime ago (see below)? Thanks!
> 
> Shunrong
> 
> ---------- Forwarded message ----------
> Date: Thu, 23 Oct 2003 15:36:40 -0400 (EDT)
> From: Shunrong Zhang <shunrong at haystack.mit.edu>
> To: William Rideout <brideout at haystack.mit.edu>
> Cc: John Holt <jmh at haystack.mit.edu>
> Subject: new global search report
> 
> 
> Hi Bill,
> 
> I've checked the new global search and shown the new report format to
> John.
> 
> The 'assmued' characters issue, the UTH bug are nicely solved. The html
> scripts and the info between two experiments are removed. These are great
> for serious analyses. 
> 
> As the report will be used by Fortran programs, and maybe by matlab as
> well for data presentation, we tend to like a simpler format, although we
> can live with this current format that will add some comlexity for Fortran
> (and matlab) coding. It'd be better to remove the blank line between two
> experiment data blocks. The info before the parameter mnemonics table
> isn't necessary (In fact, it repeats what has been shown in the email
> informing the availability of the report) and makes difficult for
> automatic reading by Fortran without a common line of statements
> (characters) marking the start point of data. That may be the case for
> matlab too.
> 
> So it would be nice for the report file to have only one line for
> mnemonics (the first line), and others lines are simply data without blank
> line in between.
> 
> Thanks!
> Shunrong
> 
> 
> 
> 
> _______________________________________________
> OpenMadrigal-developers mailing list
> OpenMadrigal-developers at openmadrigal.org
> http://www.openmadrigal.org/mailman/listinfo/openmadrigal-developers
> 
> 


-- 
Bill Rideout
MIT Haystack Observatory
Email: brideout at haystack.mit.edu
Phone: 781 981-5624