Context Navigation

Changes between Version 3 and Version 4 of ProcCmd

v3	v4
4	4	In the case of pvoconvert, it records the command-line statement that produced the fits file. For instance "pvoconvert filename" for simple conversion of a single file.
5	5
6		To facilitate conversion of lots of the survey files, pvoconvert has a "pvoconvert -D directory" option, where you can just give a directory and all files therein will be converted. This has been created as an alternative to using "pvoconvert directory/*", as the latter was writing the following to the proc_cmd column in the history table: "pvoconvert directory/file1 directory/file2 directory/file3 ..." and so on. This rapidly filled up the space allocated in that table column.
	6	To facilitate conversion of lots of the survey files, pvoconvert has a "pvoconvert -D directory" option (see ConversionSoftware), where you can just give a directory and all files therein will be converted. This has been created as an alternative to using "pvoconvert directory/*", as the latter was writing the following to the proc_cmd column in the history table: "pvoconvert directory/file1 directory/file2 directory/file3 ..." and so on. This rapidly filled up the space allocated in that table column.
7	7
8	8	This raises the question of what information do we want recorded in the proc_cmd column. Is it more important to show the actual command as typed, or to show the file where the data in the FITS file came from? [[BR]]