> Title of Software:

Pharos

 > Name, Department and System Component of each Author:

Patrick R. Michaud
Professor of Computer Science, Texas A&M Univeristy-Corpus Christi
Division of Nearshore Research, Texas A&M Univeristy-Corpus Christi

Jonathan Scott Duff, Senior Systems Analyst II
Division of Nearshore Research, Texas A&M Univeristy-Corpus Christi

Jessica Tishmack, Systems Programmer
Division of Nearshore Research, Texas A&M Univeristy-Corpus Christi

 > 1. Briefly describe the software program and its current level of
 >    development.

The Pharos software package accomplishes 3 separate tasks primarily but not exclusively for coastal and ocean environmental data sets: 1) data collection, 2) data archival/decoding 3) data disemmination. Pharos has been in constant development since its initial creation by Dr. Patrick Michaud (pmichaud@pobox.com) in 1990. The software has been operational since 1991 and has been progressively augmented and imporved. It is currently maintained and improved by Jonathan Scott Duff at the Division of Nearshore Research (duff@lighthouse.tamucc.edu)

 > 2. Describe the closest known software programs or methods which perform
 >    functions similar to the disclosed software, and indicate
 >    differences.

The National Ocean and Atmospheric Administration has proprietary software for collecting and archiving environmental data sets. More information can be found at http://www.nesdis.noaa.gov/. This includes the software system used for NOAA Physical Oceanagraphic Real-Time System (PORTS) http://www.co-ops.nos.noaa.gov/d_ports.html. Also, other universities have developed proprietary software for similar purposes.

An example of commercial software that accomplishes tasks similar to Pharos is the Meteostart LEADS system. This system differs from Pharos in that it contains both hardware and software components whereas Pharos is purely software.

 > 3. State the advantages of the disclosed software over existing methods,
 >    problems solved by the software, and new applications achieved.
 >    Identify features which are believed to be new, unexpected or
 >    critical.  Indicate any disadvantages or limitations and explain how
 >    they might be overcome.

One of the primary advantages of this software is that it's robust and built from open source components which allows for easily adding other external components or creating new specialized components. For instance, new output documents can be created by aggregating existing data within the database. This is how our forecast models are built. As new models are developed they can easily be incorporated into the system.

 > 4. Describe technical specifications for the software: hardware
 >    requirements, third-party programs required, programming
 >    language, etc.

The majority of the software is written in Perl and the bash shell. There are currently two C programs, one for importing data into the Pharos database, and one for retrieving data from the Pharos database. The system currently runs under the RedHat^? 9 version of the linux operating system but should easily port to any unix-like system with little or no difficulty.

Software Requirements:

	bash
	Perl			- most of the software is written in Perl
	Perl Modules
		DBI 		- database interface
		DBD::mysql	- specific database driver
		PDL 		- Perl Data language for complex math operations
		GD		- Perl graphics package
	Apache			- Web server
	MySQL?			- Relational Database
	gnuplot			- graphics package


 > 5. Briefly describe the level of support provided with this software.
 >    Is there a manual or list of instructions?  What level of user
 >    support would be required?

Support is currently provided via web pages located at http://lighthouse.tamucc.edu/Pharos and via email to dnr-is@lighthouse.tamucc.edu or duff@lighthouse.tamucc.edu. There is no manual or list of instructions.

 > 6. Describe potential users of the software, as well as any information
 >    on promotion, marketing, or distribution which may be valuable in
 >    realizing full potential of the program.

Potential users of Pharos include scientific organizations that would like to collect, store, process, disseminate and do research with environmental data sets. Presently we are working in collaboration with Mexican universities (UNAM, IPN), the United States National Ocean Service and other organizations. We plan to share and codevelop Pharos with these organizations.

The promotion, marketing and distribution of Pharos will be accomplished within the user group of collaborating institutions.

We do NOT plan to market Pharos as a commerical product.

 > 7. For copyright/legal purposes, please provide responses to the
 >    following:
 > 
 >  (a) Year in which creation of work was completed.  If the work has been
 >      published, provide the date and nation (if other than U.S.) of the
 >      first publication.  If possible, please provide copies of any
 >      formal publications for the file.

Pharos is continually being added to and modified, it will never be "completed".

TODO: I'm not sure which publications to list here. Should we just list all of the publications at DNRPublications that even use our software? Should we list only those that are specifically about the software?

 >  (b) List the names and dates of persons or individuals of organizations
 >      which have received copies of the software.

Eustorgio Meza Conde (emezac@ipn.mx), Instituto Politécnico Nacional (http://www.ipn.mx/), March 2004.

 >  (c) If you wish to seek copyright registration for the work, please
 >      submit along with this disclosure: 1) a representative 50 pages of
 >      code, 2) three copies of the software on disk, and 3) three copies
 >      of any manual or instruction package that accompanies the software.

We wish to seek copyright registration. See attached.

 > 8. Identify the grants, contracts, or other sources of funding that
 >    directly contributed to the conception and development of the
 >    invention as herein disclosed.  Please provide the grant number,
 >    granting entity, as well as the name of the Office and contact person
 >    that manages each grant.  Indicate if the invention was made as part
 >    of one's assigned duties or with the use of The Texas a&m University
 >    System facilities or services.

This invention was made as part of assigned duties within the Division of Nearshore Research at Texas A&M University-Corpus Christi.

 > 9. Joint authors should briefly describe each of their contributions to
 >    the conception of the invention and the percentage of effort for each
 >    (totaling 100%).

Patrick R. Michaud 60%
Jonathan Scott Duff 30%
Jessica Tishmack 10%