Difference between revisions of "MIPAV configuration files"
From MIPAV
m (→Analyze files) |
m (→What is its purpose?) |
||
| (12 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | + | == MIPAV configuration files == | |
| + | This section includes definitions and examples of the MIPAV configuration files: [[#PreferenceFile |preference]] and [[#MIpavLaxFile| LAX]].<br /> | ||
| + | |||
| + | <div id="PreferenceFile"></div> | ||
=== Preference file === | === Preference file === | ||
==== What is its purpose? ==== | ==== What is its purpose? ==== | ||
| − | + | The preference file (mipav.preference) contains either the default or customized settings for running MIPAV. These settings determine whether some features appear or how certain features look. See also: [[Customizing MIPAV#MipavOptions | MIPAV options]]. | |
| − | You can customize the settings in the file by selecting Help | + | You can customize the settings in the file by selecting Help > Program Options in the MIPAV window. For example, you can change whether the splash screen appears when you start the program, whether the scripting toolbar appears, the color of the crosshair cursor, whether the log mode is turn on, and so on. |
==== When and how is it created? ==== | ==== When and how is it created? ==== | ||
| Line 17: | Line 20: | ||
By default, MIPAV stores the preference file in your home directory. | By default, MIPAV stores the preference file in your home directory. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | However, if MIPAV is installed on a network and several users access it remotely, preference files are stored in the network home directory. | + | However, if MIPAV is installed on a network drive and several users can access it remotely, preference files are stored in the network home directory. |
| + | |||
| + | The system administrator for the network may select another directory on the network in which to store preference files. <br /> | ||
| + | |||
| + | ==== What does it look like? ==== | ||
| − | + | An example of the preference file appears in the figure below. For ease of discussion, line numbers appear on the left of each line in the figure, although they don't appear in the actual preference file. Your preference file may not have the same ordering of information as it shown below; as you customize MIPAV, your preference file changes to reflect the additional information. | |
{| border="1" cellpadding="5" | {| border="1" cellpadding="5" | ||
| − | |+ <div style="font-style: normal; margin-bottom: 3pt; margin-left: 0pt; margin-right: 0pt; margin-top: 9pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">'''<font color="#000000"> | + | |+ <div style="font-style: normal; margin-bottom: 3pt; margin-left: 0pt; margin-right: 0pt; margin-top: 9pt; text-align: left; text-decoration: none; text-indent: 0pt; text-transform: none; vertical-align: baseline">'''<font color="#000000"> An example of MIPAV.preference file <br /></font>'''</div> |
|- | |- | ||
| | | | ||
| Line 119: | Line 103: | ||
|} | |} | ||
| − | <br / | + | <br /> |
<div id="MIpavLaxFile"></div> | <div id="MIpavLaxFile"></div> | ||
| + | |||
| + | <div id="LaunchAnywhere"></div> | ||
== MIPAV LaunchAnywhere executable (LAX) file == | == MIPAV LaunchAnywhere executable (LAX) file == | ||
| − | What is it and what is its purpose? | + | === What is it and what is its purpose? === |
The LAX file is a LaunchAnywhere Executable (LAX) file that contains MIPAV's runtime environmental options. It may be helpful to access the file if you contacting the software developers during the debugging process. To contact MIPAV developers, use [http://mipav.cit.nih.gov/contact.php the MIPAV contact page]. | The LAX file is a LaunchAnywhere Executable (LAX) file that contains MIPAV's runtime environmental options. It may be helpful to access the file if you contacting the software developers during the debugging process. To contact MIPAV developers, use [http://mipav.cit.nih.gov/contact.php the MIPAV contact page]. | ||
| Line 132: | Line 118: | ||
The runtime environmental options in the LAX file are set during the development of the MIPAV software. If you install MIPAV on any Windows, UNIX, or MAC OS operating system, the LaunchAnywhere program copies a LaunchAnywhere Executable (LAX) file to the same directory as your other MIPAV software files. <br /> | The runtime environmental options in the LAX file are set during the development of the MIPAV software. If you install MIPAV on any Windows, UNIX, or MAC OS operating system, the LaunchAnywhere program copies a LaunchAnywhere Executable (LAX) file to the same directory as your other MIPAV software files. <br /> | ||
| − | + | == See also: == | |
| − | + | *[[Getting Started Quickly with MIPAV]] | |
| − | = | + | *[[Supported Formats]] |
| − | [ | + | **[[Supported Formats | Graphical and file formats supported by MIPAV]] |
| − | + | **[[Image formats descriptions | Image formats' descriptions]] | |
| − | + | **[[FAQ: Understanding Image Basics#FilesExtensions | Image files supported by MIPAV]] | |
| − | + | *[[Customizing MIPAV]] | |
| − | + | **[[Customizing MIPAV#MipavOptions | MIPAV Options dialog box]] | |
| − | + | **[[Customizing MIPAV#SplashScreen | Showing and hiding the splash screen on start-up]] | |
| − | + | **[[Customizing MIPAV#DebuggingMipav | Debugging MIPAV]] | |
| − | + | **[[Customizing MIPAV#ActionsHistory | Saving a history of actions on images]] | |
| − | + | **[[Customizing MIPAV#DefaultFileTypes | Choosing the default file types to display or save]] | |
| − | + | **[[Customizing MIPAV#AddingShortcuts | Adding Shortcuts]] | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | ' | + | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | [[Category: Help]] | |
| + | [[Category: Getting started]] | ||
Latest revision as of 15:20, 26 April 2012
Contents
MIPAV configuration files
This section includes definitions and examples of the MIPAV configuration files: preference and LAX.
Preference file
What is its purpose?
The preference file (mipav.preference) contains either the default or customized settings for running MIPAV. These settings determine whether some features appear or how certain features look. See also: MIPAV options.
You can customize the settings in the file by selecting Help > Program Options in the MIPAV window. For example, you can change whether the splash screen appears when you start the program, whether the scripting toolbar appears, the color of the crosshair cursor, whether the log mode is turn on, and so on.
When and how is it created?
MIPAV generates a preference file for all users when the program is run for the first time. Usually, the first settings recorded in the preference file are the memory setting, or maximum heap size, and the default image directory. When you first customize one or more of the settings in the Program Options dialog box, MIPAV adds those settings to the preference file as well as the default settings for those features you did not change. If you later make changes to those same preferences, the program adds those new settings to the preference file. In other words, the initial preference file is very small. It grows in size as you customize the program with the latest changes appearing last in the file.
Where is it stored?
By default, MIPAV stores the preference file in your home directory.
However, if MIPAV is installed on a network drive and several users can access it remotely, preference files are stored in the network home directory.
The system administrator for the network may select another directory on the network in which to store preference files.
What does it look like?
An example of the preference file appears in the figure below. For ease of discussion, line numbers appear on the left of each line in the figure, although they don't appear in the actual preference file. Your preference file may not have the same ordering of information as it shown below; as you customize MIPAV, your preference file changes to reflect the additional information.
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
|
# MIPAV preference file #Mon Mar 19 15:12:48 EST 2001 LightBoxGridRow=2 LightBoxBorderSize=3 EnableDICOMReceiver=true TRIM=0.4 DEBUG=true PlugInFile3=SpreadSheet PlugInFile2=GraphPanel PlugInFile1=Chart Swing=true LightBoxRowDependant=true PlugInView1=DrawTest PlugInAlgorithm1=GraphApplet Server1=MRIPS;MARS;137.187.26.152;104; Storage1=MIPAV;MIPAV;C\:\\images;3100 SplashGraphics=no LightBoxGridColor=000000 LightBoxBorderColor=960000 LightBoxGridSize=5 LightBoxMagnification=45.0 LightBoxGridCol=2 ImageDirectory=D\:\\Java\\jdk1.3\\demo\\applets\\SpreadSheet LightBoxLocation=813,23
|
|
1-2
|
Indicate the type of file and the date and time of the last update (comment lines).
|
|
3-4
|
Indicate default settings the light box image window.
|
|
5
|
Shows DICOM information and indicates whether the DICOM Receiver is on by default. If the DICOM Receiver is on, you can receive or retrieve DICOM image files.
|
|
6
|
Indicates the default trim parameter. The trim parameter is discussed in detail in Chapter 7.
|
|
7
|
Indicates whether MIPAV is placed in debug mode. If MIPAV is placed in debug mode and technical problems occur while you use the software, error messages are logged in the Output window.
|
|
11
|
Indicates whether the Swing-generated graphical user interface (GUI) is displayed. If the preference is set to false, the Advanced Windows Toolkit (AWT)-generated GUI appears instead.
|
|
12
|
Indicates default settings the light box image window.
|
|
13-14
|
Shows plug-in file information.
|
|
15-16
|
Shows DICOM information and shows hosts table entries. (The hosts table is located in the DICOM Communication Panel window.) Line 15 shows the server (device) entry. Line 16 shows a storage destination entry, which indicates where image files are stored when they are received or retrieved. If you indicate more than one storage destination entry, more lines appear in the preference file. For more information on MIPAV`s DICOM capabilities, refer to [MIPAV_DicomImages.html#1259465 "Working with DICOM Images" on page 85].
|
|
16
|
Shows DICOM information.
|
|
17
|
Indicates whether an introductory splash screen appears when you start MIPAV.
|
|
18-22
|
Indicates default settings the lightbox image window.
|
|
23
|
Shows the image directory.
|
MIPAV LaunchAnywhere executable (LAX) file
What is it and what is its purpose?
The LAX file is a LaunchAnywhere Executable (LAX) file that contains MIPAV's runtime environmental options. It may be helpful to access the file if you contacting the software developers during the debugging process. To contact MIPAV developers, use the MIPAV contact page.
LaunchAnywhere is a commercial program created by Macrovizion, Inc. and used to install and start the MIPAV software on your system.
The runtime environmental options in the LAX file are set during the development of the MIPAV software. If you install MIPAV on any Windows, UNIX, or MAC OS operating system, the LaunchAnywhere program copies a LaunchAnywhere Executable (LAX) file to the same directory as your other MIPAV software files.
