ISIS Application Documentation
cnetsplit | Standard View | TOC | Home |
The application cnetsplit splits the input control network into user specified number of control networks.
Description
Categories
Groups
Examples
History
The input control network keyword values for Description, NetworkId, and Target Keywords will be copied to each output control network. The DateTime and UserName keywords will be created new for the output control networks. The output control networks are filled from smallest to largest output file name from the first points in the input control network to the last.
We can denote the number of control points in the input file by n and the number of output files to be created is by k. Then, denote the remainder of n/k by R . If R is not zero, then, the first R files will have one more point than the last k-R files. Otherwise, if R = 0, i.e. if the number of output files evenly divides the number of points in the input control network, then each of the output files will have the same number of points.
Errors thrown by cnetsplit will include the following:
Name | Description |
---|---|
CNET | Input control network to be split. |
ONET_PREFIX | The output file name pattern string containing question marks where the file number should be placed. |
Name | Description |
---|---|
NUM_OUTPUT_FILES | The number of output files that will be created by cnetsplit |
The input control network whose control points will be divided among the output control networks. This file is not modified by cnetsplit.
Type | filename |
---|---|
File Mode | input |
Filter | *.net |
This string will be used to create unique output file names. It should contain a set of question marks ("?") where the file number will be placed. The string should not have question marks anywhere else. For each output file, the question marks will be replaced with a number from one to the number of output files. For example, if the user sets the pattern to ONET_PREFIX="ControlNet????" and NUM_OUTPUT_FILES=999, then cnetsplit will create 999 files with file names "ControlNet0001.net" through "ControlNet0999.net". Note: If there are not enough "?"s for the number of output files to be created during this run, the user will be thrown an error .
Type | string |
---|
The control points from the input control network will be split among this number of output files.
Type | integer |
---|---|
Minimum | 2 (inclusive) |
Split a control network with 8 points into 3 control networks.
Screenshot of GUI command.
|
Example GUI for cnetsplit. Screen shot of GUI for cnetsplit. This run of the program will split the file controlNet.net into 3 output files with name pattern outputNetSplit??? |
PVL of the Input control network, (controlNet.net). | This is the input control network with 8 control points that will be divided among 3 output control networks. This file is not changed by cnetsplit. |
---|---|
PVL of the first output control network, (outputNetSplit001.net). | This is the first of the output control networks created by cnetsplit. It contains the 1st, 2nd, and 3rd control points from the input control network. |
PVL of the second output control network, (outputNetSplit002.net). | This is the first of the output control networks created by cnetsplit. It contains the 4th, 5th, and 6th control points from the input control network. |
PVL of the third output control network, (outputNetSplit003.net). | This is the last of the output control networks created by cnetsplit. It contains the 7th and 8th control points from the input control network. |
Sharmila Prasad | 2010-11-03 | Original version |
Sharmila Prasad | 2010-12-21 | Updated to make the app compatible for binary cnet |
Sharmila Prasad | 2011-07-29 | changed ONET_FORMAT to ONET_PREFIX |
Jeannie Backer | 2011-10-03 | Added appTests, improved error message, added documentation. |
Jeannie Backer | 2016-04-22 | Modified to set the new control net's target and radii by using the input control net's values. References #3892 |
Jesse Mapel | 2018-07-06 | Removed calls to set control net target radii because they are no longer needed by the control network. Fixes #5457. |