Size: 1814
Comment:
|
Size: 3147
Comment:
|
Deletions are marked like this. | Additions are marked like this. |
Line 25: | Line 25: |
Line 35: | Line 33: |
Troubleshooting/FAQ * double check your data files and make sure the POP and BRD codes are correct - make sure to use the -v flag and check the log files carefully (look for files with 0 records, for example) - if python crashes with an error message: - if any "import" statement causes an error, Python or one of the modules is not correctly installed - if the gtconvert.py program crashes with an error message that says something about invalid 'utf8' characters, try specifying the '-e iso-8859-1' option (or some other encoding listed on the web page indicated in the --help message) - you may(!) be able to identify input data problems by looking at the program in the area of the line number printed by the error message - otherwise, please prepare a zip file with all the inputs and partial outputs (including screen outout from gtconvert.py) and email it to mn@slu.se(?) , clearly showing the exact command line used to launch the program, and pasting in the error message too - if bulls seem to be missing or in excess in the candidate or test groups, use -v -m options, but not -C, and check the merged files ... [more details needed in wiki (eg. file format...)] |
GEBVtest Software
The GEBV test is a validation procedure described in the Interbull Code of Practice, Appendix X.
This software consists of two programs (gtconvert.py and gebvtest.py) and little utility module used by those programs (ibutils.py).
Some sample data is also provided to test the correct functioning of the programs.
Note: In the future, organizations may prefer to prepare the data for the gebvtest.py program directly, bypassing the creation of the legacy file formats and the gtconvert.py program.
Installation
The programs have been tested under Python 2.6, 2.7 and 3.2. As a minimum you will need to have these extra python modules installed on your system: NumPy and, just for Python 2.6, argparse.
Download the attached gebvtest20130129.zip file.
Create a working directory and unzip the zip file in that directory. Two subdirectories will be created, programs and sample data. Typing
python gebvtest.py --help
from a command line prompt, from within the programs directory, should print a brief help message if the installation has been successful.
User manuals:
Sample data for program testing
Some sample data for breed HOL and population ABC are available in the sample_data directory. The two programs can be run from the programs directory as follows:
python gtconvert.py -v hol abc ../sample_data python gebvtest.py -v -m hol abc ../sample_data
The outputs should match those in the source zip file.
- Troubleshooting/FAQ
- double check your data files and make sure the POP and BRD codes are correct
- - make sure to use the -v flag and check the log files carefully (look for files with 0 records, for example) - if python crashes with an error message:
- - if any "import" statement causes an error, Python or one of the modules is not correctly installed - if the gtconvert.py program crashes with an error message that says something about invalid 'utf8' characters, try specifying the '-e iso-8859-1' option (or some other encoding listed on the web page indicated in the --help message) - you may(!) be able to identify input data problems by looking at the program in the area of the line number printed by the error message - otherwise, please prepare a zip file with all the inputs and partial outputs (including screen outout from gtconvert.py) and email it to
mn@slu.se(?) , clearly showing the exact command line used to launch the program, and pasting in the error message too
- - if any "import" statement causes an error, Python or one of the modules is not correctly installed - if the gtconvert.py program crashes with an error message that says something about invalid 'utf8' characters, try specifying the '-e iso-8859-1' option (or some other encoding listed on the web page indicated in the --help message) - you may(!) be able to identify input data problems by looking at the program in the area of the line number printed by the error message - otherwise, please prepare a zip file with all the inputs and partial outputs (including screen outout from gtconvert.py) and email it to
- - make sure to use the -v flag and check the log files carefully (look for files with 0 records, for example) - if python crashes with an error message: