- Do not edit or alter the 'info' file - it is processed automatically after verification.
- All requests not submitted by the Contact Person may be discarded by our automatic system.
- Note that the access_prod program does not work properly if the set-up of the computer operating system is not consistent. The most common problems are discussed here.
The license key file, cr_info, needs to be present in the /usr/local/lib directory in order for the HKL/HKL-2000 programs to run. One cr_info file may contain information about many computers and detectors. The program looks through the cr_info file for the right combination of fields that matches the given detector family and computer information, other fields are ignored.
The cr_info file will look like the following:
To obtain the license key, you need to run the access_prod program on each machine that you plan to use for running any of the HKL programs. Executing the access_prod results in the following dialog (example answers in red, comments in italics):
enter the name of your institution: State University
enter the name of PI: John Doe (Principal Investigator or Group Leader)
enter the name of the person responsible for HKL maintenance: Jane Doe
enter names of all frame formats (detectors) you want to use: mar345 raxis4 (see below)
enter the number of detectors in your lab which are
currently supported by HKL package: 2
enter the name of the company from which you received
your license: HKL Research, Inc. (Other Possible Software Providers: Rigaku, etc.)
enter HKL version number: HKL-2000_720
if this is a temporary license, enter the number of days you request,
for a permanent license enter 'noexpir': noexpir
do you want to send an automatic e-mail to email@example.com
in order to activate your license (y) ? n
If the answer is y (yes), the access_prod program may automatically send an e-mail with a request for an access file: cr_info. It may not always work, though. If the answer is n (no) the program will produce the following info file. You may save the info file and afterward 'manually' send it to firstname.lastname@example.org.
An example of the 'info' file created by the access_prod program is given below (comments in italics) :
|HOST-NAME: vp4.med.state.edu||(extracted by the program - do not edit!)
NOTE: the field is limited in length to 30 characters
|HOST-ID: -2035379618||(extracted by the program - do not edit!)|
|HOSTNAME: state.edu||(extracted by the program - do not edit!)|
|HW_PROV: linux||(extracted by the program - do not edit!)|
|CPU-SERIAL: linux,eth1,001762854231||(extracted by the program - do not edit!)|
|INSTITUTION: State University||Licensee's Institution name|
|PI: John Doe||Principal Investigator or Group Leader|
|CONTACT: Jane Doe||Contact Person|
|DETECTORS: mar345 raxis4||Detector Families|
|NO-OF-DET: 2||Number of Detectors at Home Facility|
|PROVIDER: HKL Research, Inc.||License Provider: Rigaku, HKL, etc.|
|VERSION: HKL-2000_722||Requested Version of the Program|
|EXPIR: noexpir||example: 60; Jan 1, 2023; noexpir|
The following are detector families that may be used in the above 'questionnaire':
raxis2 - RAXIS-II
raxis4 - RAXIS-IV
raxis5 - RAXIS-V
mar345 - MAR345 detector
This is only a partial list. You may also just simply write a description of the detector format, for example, Pilatus 6M, ADSC Q315, etc.
You should receive the cr_info file from us by return mail. Usually, it should take no more than 48h to receive cr_info. The cr_info file should be placed in the directory:
You need system privileges to do so. In case of an emergency you may put this file into your home directory, but remember to ask a system administrator to copy cr_info into /usr/local/lib. Otherwise, nobody else will be able to run the HKL programs.