<FONT face="Default Sans Serif, Verdana, Arial, Helvetica, sans-serif"
size=2><DIV>Ed,</DIV><DIV> </DIV><DIV>The code hash idea sounds useful for
huge codes. </DIV><DIV> </DIV><DIV>But I still think
the idea of stuffing the whole code into the</DIV><DIV>netcdf file will work
for many folks and be the most desirable</DIV><DIV>route. I
guess by your definition of "medium", the code I'm
using</DIV><DIV>(ROMS) is "small", for though it is about 100,000 lines of
FORTRAN code, </DIV><DIV>it compresses to less than 1 Mb! Since my
netcdf output </DIV><DIV>files are typically 300 -3000 Mb, I won't
even notice the difference.</DIV><DIV>How big is your
code?!</DIV><DIV> </DIV><DIV>For all the guys who are faithful to CVS
and the like, this </DIV><DIV>code embedding stuff is certainly not
necessary, but most of </DIV><DIV>the ocean modelers I know have 15 different
unofficial versions </DIV><DIV>of any particular official version number, and
they are are not keen </DIV><DIV>on giving any of them a finer grained
version number for some</DIV><DIV>pretty good reasons (can't put a fine grained
version number on</DIV><DIV>a
band-aid)!</DIV><DIV> </DIV><DIV>-Rich</DIV><DIV><BR>Dr. Richard P. Signell rsignell@xxxxxxxx<BR>U.S. Geological Survey (508) 457-2229 <BR>384 Woods Hole Road Fax: (508) 457-2310<BR>Woods Hole, MA 02543-1598 <BR></DIV><DIV><DIV><BR></DIV><FONT
color=#990099>-----owner-netcdfgroup@xxxxxxxxxxxxxxxx wrote:
-----<BR><BR></FONT>To: Rich Signell <rsignell@xxxxxxxx>,
netcdfgroup@xxxxxxxxxxxxxxxx<BR>From: Ed Hill <eh3@xxxxxxx><BR>Sent by:
owner-netcdfgroup@xxxxxxxxxxxxxxxx<BR>Date: 11/23/2004 05:41PM<BR>Subject: Re:
How to save a ZIP file within a NetCDF file<BR><BR><font face="monospace"
size=2>On Tue, 2004-11-23 at 14:08 -0500, Rich Signell wrote:<BR>> Folks,<BR>> <BR>> Here's a problem we encounter all the time in the<BR>> modeling business: we have a model run (netcdf output,<BR>> of course), and we can't quite figure out what version of<BR>> the code actually was used to produce it. Oh sure,<BR>> it says "version 2.1" but that was before we hacked<BR>> the code to fix X, or put in that special little patch<BR>> just for this run (or was it taken out)? Etc.<BR><BR><BR>Hi Rich,<BR><BR>It sounds like you could use a finer-grained version number. And/or a<BR>few more descriptive attributes that mention who is running the code and<BR>what they have or have not have done with it.<BR><BR>But getting back to your idea: for "medium" [1] and larger code bases,<BR>embedding the entire source code into the model output isn't necessarily<BR>a great idea. It doesn't scale.<BR><BR>Instead, have you considered embedding a hash of your model? For<BR>instance, during the model build stage you could easily create a list of<BR>the source files and their MD5SUMs and then embed that list into one or<BR>more output files (which may or may not be in a NetCDF format).<BR>Admittedly, it wouldn't tell you exactly what modifications were made to<BR>the code. But it would tell you which files had been modified and it<BR>would scale to work with much larger projects. And any hash(es) can be<BR>though of as a sort of "extended version number".<BR><BR>If you'd like, I'd be happy to work with you on writing up a quick pair<BR>of hash-list-embed and hash-list-extract utilities.<BR><BR>Ed<BR><BR>[1] lets define "medium" as "big enough to make the output<BR> file(s) unwieldy even when the source code has been<BR> compressed"<BR><BR>-- <BR>Edward H. Hill III, PhD<BR>office: MIT Dept. of EAPS; Rm 54-1424; 77 Massachusetts Ave.<BR> Cambridge, MA 02139-4307<BR>emails: eh3@xxxxxxx ed@xxxxxxx<BR>URLs: <A&NBSP;HREF="HTTP:
designtimesp="7808" ? eh3
web.mit.edu>http://web.mit.edu/eh3/</A> <A&NBSP;HREF="HTTP:
designtimesp="7809" ?
eh3.com>http://eh3.com/</A><BR>phone: 617-253-0098<BR>fax: 617-253-4464<BR><BR><BR><BR>***PRIVILEGED AND CONFIDENTIAL*** <BR>The information contained in this e-mail message (including any attached files) is intended for the use of the addressee(s) only and is privileged information. The information should neither be posted to the Internet, nor published in any other public domain, without the express permission of the sender. If you are not the intended recipient(s) or the recipient's representative, you are hereby notified that any use, disclosure, copying or distribution of this communication is prohibited. If you have received this communication in error please notify us immediately at postmaster@xxxxxxxxxxxxxxxxx, and remove this message from your system.<BR><BR><BR></font></DIV></FONT>