Validates master and grandmaster snippets by using the parsing code of the HCAL Function Manager.
The xmlValidator can parse either master or grandmaster snippets intended for the HCALFM. In the case of master snippets, it creates a copy of the xml file to validate in a temporary directory. For grandmaster snippets, it is does not need to make such a copy.
When parsing a master snippet, this script creates the CfgCVS structure for master snippets that the HCALFM is used to seeing; i.e. if your master snippet is called my_xml_file.xml, this script will create a copy of it with the structure my_xml_file.xml/pro. By default, this copy will be made in the /tmp directory, but you can specify a different location (see the Advanced Usage section below.)
To validate an xml file,
./xmlValidate.sh my_xml_file.xml
You can also validate an xml file like this:
java -jar hcalfmXMLvalidator.jar my_xml_file.xml
To specify that the temporary directory should be somewhere else besides /tmp,
java -jar hcalfmXMLvalidator.jar my_xml_file.xml my_tmp_directory
On a machine where RCMS and the HCALFM are installed,
cd /home/daqowner/TriDAS
git clone [email protected]:HCALRunControl/xmlValidator.git
cd xmlValidator
ant
The executable jar file will appear in the jars directory. It should be able to run on any machine that has Java installed.
Note that it should always be recompiled against the FM code if/when the relevant FM code changes. To update the HCALFM jar that the xmlValidator gets built against, it must be changed in line 41 of build.xml.