Main.Tutorial History

Hide minor edits - Show changes to markup

September 15, 2010, at 03:39 PM by 137.48.19.126 -
Changed lines 49-50 from:

Comgratulations!!ChemChains is now installed and ready for your first simulation!

to:

Congratulations!! ChemChains is now installed and ready for your first simulation!

December 05, 2009, at 04:26 PM by 137.48.19.42 -
Changed lines 294-295 from:
[@./ChemChains -ilogic inFiles/exts/CChain/logic/sampleNet.txt

-ispecs inFiles/exts/CChain/specs/sampleSpecs.txt

to:
[@./ChemChains -ilogic inFiles/CChain/logic/sampleNet.txt

-ispecs inFiles/CChain/specs/sampleSpecs.txt

Changed lines 355-357 from:
[@./ChemChains -ilogic inFiles/exts/CChain/logic/sampleNet.txt

-ispecs inFiles/exts/CChain/specs/sampleSpecs.txt -patterns -isettings inFiles/exts/exts/Patterns/settings.txt

to:
[@./ChemChains -ilogic inFiles/CChain/logic/sampleNet.txt

-ispecs inFiles/CChain/specs/sampleSpecs.txt -patterns -isettings inFiles/exts/Patterns/settings.txt

December 05, 2009, at 04:23 PM by 137.48.19.42 -
Changed lines 269-271 from:

-itables inFiles/exts/FileConverter/sampleNet@ -o outputFileName.txt]

to:

-itables inFiles/exts/FileConverter/sampleNet -o outputFileName.txt@]

December 05, 2009, at 04:22 PM by 137.48.19.42 -
Changed lines 268-270 from:

-iNodeList inFiles/exts/FileConverter/sampleNodeList.txt -iTables inFiles/exts/FileConverter/sampleNet@]

to:

-inodelist inFiles/exts/FileConverter/sampleNodeList.txt -itables inFiles/exts/FileConverter/sampleNet@ -o outputFileName.txt]

April 20, 2009, at 02:03 PM by 137.48.19.50 -
Changed line 362 from:

ChemChains can be run with randomly generated conditions for every simulation. To run ChemChains with random initial conditions enabled, use the '-rand_init' flag.

to:

ChemChains can be run with randomly generated conditions for every simulation. To run ChemChains with random initial conditions enabled, use the '-randInit' flag.

February 28, 2009, at 11:11 AM by 68.229.177.191 -
Changed line 144 from:
Bool:B:True:A,C:FF,FT,TT
to:
Bool:B:True:C,A:FF,FT,TT
February 28, 2009, at 12:29 AM by 68.229.177.191 -
Changed line 355 from:

-ispecs inFiles/exts/CChain/logic/sampleNet.txt

to:

-ispecs inFiles/exts/CChain/specs/sampleSpecs.txt

February 28, 2009, at 12:28 AM by 68.229.177.191 -
Changed line 294 from:

-ispecs inFiles/exts/CChain/logic/sampleNet.txt

to:

-ispecs inFiles/exts/CChain/specs/sampleSpecs.txt

February 28, 2009, at 12:26 AM by 68.229.177.191 -
Changed line 275 from:

-ispecs inFiles/exts/CChain/logic/sampleNet.txt

to:

-ispecs inFiles/exts/CChain/specs/sampleSpecs.txt

November 17, 2008, at 11:36 AM by 68.229.177.191 -
Changed lines 44-46 from:
  1. Unpack ChemChains onto your Desktop and copy/move the ChemChains directory into the Cygwin\home\username\ directory (the cygwin directory should be on your Desktop as the instructions above suggested)
  2. Start Cygwin by clicking on the Cygwin shortcut on your Desktop.

When Cygwin is launched you will begin in the default directory, C:\cygwin\~.

to:
  1. Unpack ChemChains onto your Desktop and copy/move the ChemChains directory into the Cygwin\home\username\ directory (the cygwin directory should be on your Desktop as the instructions above suggested). This is also where your simulation results will be stored.
  2. Start Cygwin by clicking on the Cygwin shortcut on your Desktop. When Cygwin is launched you will begin in the default directory, /home/yourUsername/.
November 17, 2008, at 11:33 AM by 68.229.177.191 -
Changed line 34 from:
  1. Select the root directory. For this tutorial, select your Desktop as the root directory. (A message will pop up, saying that you should not choose a path that contains spaces. Proceed anyway. Once you're familiar with Cygwin, you can reinstall Cygwin in a different directory)
to:
  1. Select the root directory. For this tutorial, select a directory on your Desktop as the root directory. E.g., "C:\Documents and Settings\yourUsername\Desktop\cygwin" (A message will pop up, saying that you should not choose a path that contains spaces. Proceed anyway. Once you're familiar with Cygwin, you can reinstall Cygwin in a different directory)
Changed line 37 from:
  1. Select the location to download packages from (try to select one closer to your location to reach faster download speed).
to:
  1. Select the location to download packages from (you can use ftp://ftp/gtlib/gatech.edu which has been faster than others in our case).
Changed line 44 from:
  1. Unpack ChemChains onto your Desktop
to:
  1. Unpack ChemChains onto your Desktop and copy/move the ChemChains directory into the Cygwin\home\username\ directory (the cygwin directory should be on your Desktop as the instructions above suggested)
Changed lines 47-51 from:
  1. Type in 'cd ..' and press ENTER to get to the root directory 'C:\cygwin'
  2. You will need to copy the ChemChains sourcefiles into a subdirectory within cygwin
  3. To enter the ChemChains directory, type cd followed by the directory you put ChemChains in and press ENTER
  4. Compile ChemChains by typing 'make' and pressing ENTER
to:
  1. Type in 'cd ChemChains1.0_clean' and press ENTER to get to the ChemChains directory
  2. Compile ChemChains by typing 'make' and pressing ENTER.

Comgratulations!!ChemChains is now installed and ready for your first simulation!

November 17, 2008, at 11:16 AM by 68.229.177.191 -
Changed line 34 from:
  1. Select the root directory. For this tutorial, select your Desktop as the root directory.
to:
  1. Select the root directory. For this tutorial, select your Desktop as the root directory. (A message will pop up, saying that you should not choose a path that contains spaces. Proceed anyway. Once you're familiar with Cygwin, you can reinstall Cygwin in a different directory)
November 17, 2008, at 11:13 AM by 68.229.177.191 -
Changed line 34 from:
  1. Select the root directory (default = C:\cygwin)
to:
  1. Select the root directory. For this tutorial, select your Desktop as the root directory.
Changed lines 40-41 from:
to:
  1. Click Finish once the installation is completed. This will create a shortcut on your Desktop.
Added lines 44-45:
  1. Unpack ChemChains onto your Desktop
  2. Start Cygwin by clicking on the Cygwin shortcut on your Desktop.
November 17, 2008, at 10:54 AM by 68.229.177.191 -
Changed lines 39-40 from:
  1. Hit next. The installer will download and install the selected packages. (If anytime in the future a new package needs to be added the Cygwin installer can be re-run and additional package(s) selected.)
to:
  1. Hit next. The installer will download and install the selected packages. This may take a while, depending on your Internet connection speed. (If anytime in the future a new package needs to be added the Cygwin installer can be re-run and additional package(s) selected.)
November 17, 2008, at 10:45 AM by 68.229.177.191 -
Changed line 38 from:
  1. The package list interface will come up to select packages to install. To compile and run ChemChains the following packages are necessary from the Developer package IN ADDITION TO the ones preselected by Cygwin: binutils, gcc-c++, and make packages
to:
  1. The package list interface will come up to select packages to install. To compile and run ChemChains the following packages are necessary from the Developer package IN ADDITION TO the ones preselected by Cygwin: binutils, gcc-g++, and make packages
November 17, 2008, at 10:43 AM by 68.229.177.191 -
Changed line 38 from:
  1. The package list interface will come up to select packages to install. To compile and run ChemChains the following packages are necessary from the Developer packages IN ADDITION TO the ones preselected by Cygwin: binutils, gcc-c++, and make packages
to:
  1. The package list interface will come up to select packages to install. To compile and run ChemChains the following packages are necessary from the Developer package IN ADDITION TO the ones preselected by Cygwin: binutils, gcc-c++, and make packages
November 17, 2008, at 10:40 AM by 68.229.177.191 -
Changed lines 36-37 from:
  1. Select your connection type. Hit next.
  2. Select the location to download packages from.
to:
  1. Select your connection type (Direct connection should suffice). Hit next.
  2. Select the location to download packages from (try to select one closer to your location to reach faster download speed).
November 17, 2008, at 10:38 AM by 68.229.177.191 -
Changed line 35 from:
  1. Select the package directory (this is where it the installation files are kept); for this tutorial, select your Desktop location. Click next.
to:
  1. Select the package directory (this is where it the installation files are kept); for this tutorial, use your Desktop location (which should be selected by default). Click next.
November 17, 2008, at 10:37 AM by 68.229.177.191 -
Changed line 35 from:
  1. Select the package directory (this is where it the installation files are kept); the same directory as used for root is acceptable. Click next.
to:
  1. Select the package directory (this is where it the installation files are kept); for this tutorial, select your Desktop location. Click next.
November 14, 2008, at 11:16 AM by 137.48.20.71 -
Added line 32:
  1. File download manager will pop up. Select Run.
November 14, 2008, at 11:14 AM by 137.48.20.71 -
Changed line 31 from:
  1. Go to here and download and run the file Install.exe (The Cygwin installation wizard will come up)
to:
  1. Go to here and click on "Install or update now!" link. (The Cygwin installation wizard will come up)
November 14, 2008, at 11:13 AM by 137.48.20.71 -
Changed lines 40-41 from:

Running Cygwin

to:

Running Cygwin & Setting up ChemChains

November 14, 2008, at 11:11 AM by 137.48.20.71 -
Changed line 21 from:
  1. Download ChemChains package from here and save it to your desktop.
to:
  1. Download ChemChains package from here and save it to your desktop.
November 14, 2008, at 11:10 AM by 137.48.20.71 -
Changed line 21 from:
  1. Download ChemChains package from here and save it to your desktop.
to:
  1. Download ChemChains package from here and save it to your desktop.
November 14, 2008, at 11:08 AM by 137.48.20.71 -
Changed lines 15-16 from:

For example, you can download and install the freely available cygwin from here.

to:

You can use a freely available Cygwin (see below).

October 31, 2008, at 12:01 PM by 137.48.19.37 -
Changed lines 44-45 from:
  1. To enter the ChemChains directory, type 'cd xxx' and press ENTER
to:
  1. You will need to copy the ChemChains sourcefiles into a subdirectory within cygwin
  2. To enter the ChemChains directory, type cd followed by the directory you put ChemChains in and press ENTER
October 21, 2008, at 05:27 PM by 137.48.16.86 -
Changed line 229 from:

Flag to Specify the Network Descriptor File

to:

Flag to Specify the Simulation Specification File

October 21, 2008, at 05:26 PM by 137.48.16.86 -
Changed lines 230-231 from:
./ChemChains -ilogic [network descriptor filename]
to:
./ChemChains -ispecs [simulation specification filename]
October 21, 2008, at 05:26 PM by 137.48.16.86 -
Added lines 229-231:

Flag to Specify the Network Descriptor File

./ChemChains -ilogic [network descriptor filename]
October 21, 2008, at 05:23 PM by 137.48.16.86 -
Changed lines 144-145 from:

Once finished, save the file as inFiles/CChain/logic/myNetwork.txt.

to:

Once finished, save the file as inFiles/CChain/logic/myNetwork.txt or just use the sample network descriptor provided in the current release as mentioned above.

Added line 148:

\\

October 21, 2008, at 05:22 PM by 137.48.16.86 -
Added line 111:
Added lines 146-147:

Flag to Specify the Network Descriptor File

./ChemChains -ilogic [network descriptor filename]
October 21, 2008, at 05:19 PM by 137.48.16.86 -
Changed line 68 from:

cellSpecification file name

to:

(:cell:)Simulation specification file name

Changed line 70 from:

cellNetwork logic file name

to:

(:cell:)Network descriptor file name

October 21, 2008, at 05:17 PM by 137.48.16.86 -
Changed lines 127-128 from:
Node Truth Tables
Figure 2: Truth tables for nodes A, B, and C, representing the sample network in Fig. 1
to:
Node Truth Tables
Figure 2: Truth tables for nodes A, B, and C, representing the sample network in Fig. 1
October 21, 2008, at 05:16 PM by 137.48.16.86 -
Changed lines 127-128 from:
Node Truth Tables
Figure 2: Truth tables for nodes A, B, and C, representing the sample network in Fig. 1
to:
Node Truth Tables
Figure 2: Truth tables for nodes A, B, and C, representing the sample network in Fig. 1
October 21, 2008, at 05:15 PM by 137.48.16.86 -
Added line 113:

\\

Added lines 125-126:

These activation mechanisms can be expressed as individual truth tables (Figure 2).

Deleted lines 128-130:

These activation mechanisms can be expressed as individual truth tables (Figure 2).

October 21, 2008, at 05:15 PM by 137.48.16.86 -
Deleted line 112:

\\

October 21, 2008, at 05:14 PM by 137.48.16.86 -
Added line 127:
Changed lines 151-152 from:

\\(The following example of a simple simulation specification file is included with the current ChemChains release and can be found in "inFiles/CChain/specs/sampleSpecs.txt" file in the ChemChains directory)

to:

(The following example of a simple simulation specification file is included with the current ChemChains release and can be found in "inFiles/CChain/specs/sampleSpecs.txt" file in the ChemChains directory)

October 21, 2008, at 05:13 PM by 137.48.16.86 -
Added lines 150-151:

\\(The following example of a simple simulation specification file is included with the current ChemChains release and can be found in "inFiles/CChain/specs/sampleSpecs.txt" file in the ChemChains directory)

October 21, 2008, at 05:12 PM by 137.48.16.86 -
Changed lines 113-114 from:

(The following example of a simple toy network is available with the current ChemChains release and can be found in "inFiles/CChain/logic/sampleNet.txt" file in the ChemChains directory)

to:


(The following example of a simple toy network is included with the current ChemChains release and can be found in "inFiles/CChain/logic/sampleNet.txt" file in the ChemChains directory)

October 21, 2008, at 05:11 PM by 137.48.16.86 -
Deleted lines 52-54:

Changed lines 112-113 from:

(The following example of a simple toy network is available with the current ChemChains release and can be found in "inFiles/CChain/logic/sampleNet.txt" file in the ChemChains directory)

to:


(The following example of a simple toy network is available with the current ChemChains release and can be found in "inFiles/CChain/logic/sampleNet.txt" file in the ChemChains directory)

October 21, 2008, at 05:10 PM by 137.48.16.86 -
Changed lines 115-116 from:
to:

(The following example of a simple toy network is available with the current ChemChains release and can be found in "inFiles/CChain/logic/sampleNet.txt" file in the ChemChains directory)

October 21, 2008, at 04:58 PM by 137.48.16.86 -
Changed lines 27-28 from:
  1. make (This should create an executable file called ChemChains)
to:
  1. Type "make" to compile ChemChains (This should create an executable file called ChemChains)
October 21, 2008, at 04:57 PM by 137.48.16.86 -
Changed lines 26-27 from:
  1. Type: make (This should create an executable file called ChemChains)
to:
  1. Change to the unziped ChemChains directory on your desktop
  2. make (This should create an executable file called ChemChains)
October 21, 2008, at 04:55 PM by 137.48.16.86 -
Changed line 21 from:
  1. Download ChemChains package from here and save it to your desktop.
to:
  1. Download ChemChains package from here and save it to your desktop.
October 21, 2008, at 04:54 PM by 137.48.16.86 -
Added lines 19-23:

Download

  1. Download ChemChains package from here and save it to your desktop.
  2. Unzip the package to your desktop (you can unzip the package anywhere on your computer, but this tutorial assumes the location of the ChemChains directory on your desktop)
October 20, 2008, at 02:29 PM by 137.48.16.86 -
Changed line 36 from:

When Cygwin is started the default directory is C:\cygwin\~.

to:

When Cygwin is launched you will begin in the default directory, C:\cygwin\~.

October 20, 2008, at 02:28 PM by 137.48.16.86 -
Changed lines 31-32 from:
  1. The package list interface will come up to select packages to install. To compile and

run ChemChains the following packages are necessary from the Developer packages IN ADDITION TO the ones preselected by Cygwin: binutils, gcc-c++, and make packages

to:
  1. The package list interface will come up to select packages to install. To compile and run ChemChains the following packages are necessary from the Developer packages IN ADDITION TO the ones preselected by Cygwin: binutils, gcc-c++, and make packages
Changed lines 35-42 from:

There are a couple useful commands for working in a Unix environment,

to:

When Cygwin is started the default directory is C:\cygwin\~.

  1. Type in 'cd ..' and press ENTER to get to the root directory 'C:\cygwin'
  2. To enter the ChemChains directory, type 'cd xxx' and press ENTER
  3. Compile ChemChains by typing 'make' and pressing ENTER

Some basic Unix commands
There are a couple useful commands for working in a Unix environment:

Changed lines 47-54 from:

When you start Cygwin it will start you into C:\cygwin\~, you need to cd .. to get to C:\cygwin, when you get to the directory that you put the ChemChains binary into you can use the command make to compile it. When it finishes it creates the executable ChemChains, to run it it use the command ./ChemChains along with the flags you want to use. You can use ./ChemChains -h to view flag usage documentation.

to:

October 20, 2008, at 02:18 PM by 137.48.16.86 -
Changed lines 25-43 from:

First go here and download the file Install.exe, when you run it it will open the Cygwin installation wizard. If you don't have any cygwin packages downloaded allready select Install From Internet and hit next. It will prompt you for a root directory with the default C:\cygwin. You can use another directory if you want but I would advise against using C:\. It will then prompt you for a package directory, this is where it will keep the installation files for  the packages you install, I usually use the same directory as I selected for root. Click next and it will prompt you for your connection type, select it and hit next, then select a mirror to download packages from. Then it will bring up a package list interface. To compile and run ChemChains you will need the binutils, gcc-c++, and make packages from the Developer packages in addition to all of the packages that Cygwin will automatically select. After you select the packages that you want hit next and the installer will download and install the packages you've selected. If anytime in the future you find that you need a new package installed you can re-run the Cygwin installer and select the package(s) you need and it will install them for you.

to:
  1. Go to here and download and run the file Install.exe (The Cygwin installation wizard will come up)
  2. Select Install From Internet and hit next
  3. Select the root directory (default = C:\cygwin)
  4. Select the package directory (this is where it the installation files are kept); the same directory as used for root is acceptable. Click next.
  5. Select your connection type. Hit next.
  6. Select the location to download packages from.
  7. The package list interface will come up to select packages to install. To compile and

run ChemChains the following packages are necessary from the Developer packages IN ADDITION TO the ones preselected by Cygwin: binutils, gcc-c++, and make packages

  1. Hit next. The installer will download and install the selected packages. (If anytime in the future a new package needs to be added the Cygwin installer can be re-run and additional package(s) selected.)
September 30, 2008, at 03:36 PM by 137.48.19.37 -
Changed lines 48-50 from:
  1. cd [name] - changes directory to [name], if you use .., it will take
  2. you up a directory
to:
  1. cd [name] - changes directory to [name], if you use .., it will take you up a directory
September 30, 2008, at 03:22 PM by 137.48.19.37 -
Changed lines 24-26 from:
  1. Start Cygwin
  2. In the Cygwin terminal window, type: make (This should create an executable file called ChemChains)
to:

Installing Cygwin

First go here and download the file Install.exe, when you run it it will open the Cygwin installation wizard. If you don't have any cygwin packages downloaded allready select Install From Internet and hit next. It will prompt you for a root directory with the default C:\cygwin. You can use another directory if you want but I would advise against using C:\. It will then prompt you for a package directory, this is where it will keep the installation files for  the packages you install, I usually use the same directory as I selected for root. Click next and it will prompt you for your connection type, select it and hit next, then select a mirror to download packages from. Then it will bring up a package list interface. To compile and run ChemChains you will need the binutils, gcc-c++, and make packages from the Developer packages in addition to all of the packages that Cygwin will automatically select. After you select the packages that you want hit next and the installer will download and install the packages you've selected. If anytime in the future you find that you need a new package installed you can re-run the Cygwin installer and select the package(s) you need and it will install them for you.

Running Cygwin

There are a couple useful commands for working in a Unix environment,

  1. ls - shows the contents of the current directory
  2. mkdir [name] - makes a new directory named [name]
  3. cd [name] - changes directory to [name], if you use .., it will take
  4. you up a directory

When you start Cygwin it will start you into C:\cygwin\~, you need to cd .. to get to C:\cygwin, when you get to the directory that you put the ChemChains binary into you can use the command make to compile it. When it finishes it creates the executable ChemChains, to run it it use the command ./ChemChains along with the flags you want to use. You can use ./ChemChains -h to view flag usage documentation.

August 23, 2008, at 09:56 AM by 68.229.177.191 -
Changed lines 183-184 from:

To create a delay node, use the following syntax:

to:

To create a sustain node, use the following syntax:

July 27, 2008, at 01:41 AM by 68.229.177.191 -
Added lines 61-62:

(:cellnr:)-A (:cell:)Output all nodes

July 27, 2008, at 01:39 AM by 68.229.177.191 -
Changed lines 183-184 from:
Sustain:name:initial value:parent node:duration (in iteration units)
to:
Sustain:name:initial value:parent node:duration
July 27, 2008, at 01:38 AM by 68.229.177.191 -
Changed lines 294-295 from:
default:lower_limit1 higher_limit1 code1,lower_limit2 higher_limit2 code2
to:
default:lower_limit1 higher_limit1 code1,
lower_limit2 higher_limit2 code2
Changed lines 302-303 from:
NodeName:lower_limit1 higher_limit1 code1,lower_limit2 higher_limit2 code2
to:
NodeName:lower_limit1 higher_limit1 code1,
lower_limit2 higher_limit2 code2 
July 26, 2008, at 11:10 PM by 68.229.177.191 -
Changed line 37 from:

Table 1: List of flags available in the calculation mode.

to:

Table 1: List of currently available flags.

Changed line 52 from:

cellnritables xxx

to:

(:cellnr:)-itables xxx

Changed lines 257-267 from:

table border=1 width=40% align=center bgcolor=grey cellspacing=0 cellnr Table 3: Contents of output generated during calculation mode. cellnr

to:

(:table border=1 bgcolor=#b5dbff cellspacing=0 :) (:cellnr colspan=2:) Table 2: Contents of output generated during calculation mode. (:cellnr align=center:)File/Directory Name (:cell align=center:) Description (:cellnr:)all_avg.mtb (:cell:)Tab-delimited text file with activation levels of all nodes across all simulations (:cellnr:)all_dosage.mtb (:cell:)Activity levels of all inputs across all simulations (:cellnr:)outputNode_avg.csv (:cell:)Activity levels of nodes specified for pattern analysis. (:cellnr:)inputNames.csv (:cell:)List of input nodes. (:cellnr:)nodeNames.csv (:cell:)Names of all nodes in the network. (:cellnr:)specs.txt (:cell:)Specification file used for this experiment. (:cellnr:)logic/ (:cell:)Directory containing all logic files associated with this experiment (:cellnr:)nodesAvg/ (:cell:)Directory containing activity level information for each node. (:cellnr:)patterns/ (:cell:)Output directory for the patterns extension. (:cellnr:)bits/ (:cell:)Output directory holding ON/OFF sequences for all nodes in the network

July 26, 2008, at 11:02 PM by 68.229.177.191 -
Added lines 58-60:

(:cellnr colspan=2:)Flags used with Visual mode (:cellnr:)-vis xxx (:cell:)Instantiates the visual mode and sets the output file name

Changed lines 70-73 from:

cellnr colspan=2Flags used with Visual mode cellnr-vis xxx cellInstantiates the visual mode and sets the output file name cellnr colspan=2Flags used with Calculation mode

to:

(:cellnr colspan=2:)Flags used for Pattern analysis extension

July 26, 2008, at 11:00 PM by 68.229.177.191 -
Changed lines 31-32 from:

To run ChemChains, users must provide several input files. Once simulations and/or analysis are initiated, ChemChains will create several types of output file formats. Both the input files, as well as the desired output format and the output files must be specified by users in the form of command-line parameters provided to ChemChains at the time of program initiation. To see all available options and command-line parameters run ChemChains with the -h flag.

to:

To run ChemChains, users must provide several input files. Once simulations and/or analysis are initiated, ChemChains will create several types of output file formats. Both the input files, as well as the desired output format and the output files must be specified by users in the form of command-line parameters provided to ChemChains at the time of program initiation. To see all available options and command-line parameters run ChemChains with the -h flag. All flags available in the most recent version of ChemChains are described in Table 1.

Deleted line 34:

All flags available in the most recent version of ChemChains are described in Table 1.

July 26, 2008, at 11:00 PM by 68.229.177.191 -
Added lines 35-79:

All flags available in the most recent version of ChemChains are described in Table 1. (:table border=1 bgcolor=#b5dbff cellspacing=0 :) (:cellnr colspan=2:) Table 1: List of flags available in the calculation mode. (:cellnr align=center:)Flag (:cell align=center:) Description (:cellnr colspan=2:)General flags used with all running modes (:cellnr:)-ispecs xxx (:cell:)Specification file name (:cellnr:)-ilogic xxx (:cell:)Network logic file name (:cellnr:)-v (:cell:)Verbose mode (:cellnr colspan=2:)Flags used with FileConversion mode (:cellnr:)-ND2TT (:cell:)Convert -ilogic file into a truth table (:cellnr:)-TT2ND (:cell:)Convert truth tables into a specs file (:cellnr:)itables xxx (:cell:)File path for list of truthtables, and the nodelist (:cellnr:)-inodelist xxx (:cell:)File for List of Nodes, Used with TT2ND (:cellnr:)-o xxx (:cell:)File Converter output path/file (:cellnr colspan=2:)Flags used with Calculation mode (:cellnr:)-calc xxx (:cell:)Calculation mode and experiment name (:cellnr:)-n xxx (:cell:)Number of consecutive simulations (:cellnr:)-noBits (:cell:)Suppress bitfile printing (:cellnr:)-randInit (:cell:)Generate random network initial conditions for each simulation (:cellnr colspan=2:)Flags used with Visual mode (:cellnr:)-vis xxx (:cell:)Instantiates the visual mode and sets the output file name (:cellnr colspan=2:)Flags used with Calculation mode (:cellnr:)-patterns (:cell:)Instatiate patterns analysis (:cellnr:)-isettings xxx (:cell:)Patterns file with node activity range settings (:cellnr:)-inodes xxx (:cell:)File with nodes to be analyzed (:tableend:)

Changed lines 246-247 from:

To run ChemChains in the calculation mode, use the '-calc' flag. Other flags available within the calculation mode are listed in Table 2.

to:

To run ChemChains in the calculation mode, use the '-calc' flag.

You can run ChemChains (using our previously created network descriptor and simulation specification files) in the calculation mode in the most basic way (without the use of any extensions) as follows:

./ChemChains -ilogic inFiles/exts/CChain/logic/sampleNet.txt 
-ispecs inFiles/exts/CChain/logic/sampleNet.txt 
-n 5 -calc myFirstCalcSimulation 

This command will simulate our toy network five times and will save all output in CCOutput/stats/myFirstCalcSimulation folder.

The following table describes the structure and contents of the output folder.

Changed line 260 from:

Table 2: List of flags available in the calculation mode.

to:

Table 3: Contents of output generated during calculation mode.

Deleted lines 270-292:

You can run ChemChains (using our previously created network descriptor and simulation specification files) in the calculation mode in the most basic way (without the use of any extensions) as follows:

./ChemChains -ilogic inFiles/exts/CChain/logic/sampleNet.txt 
-ispecs inFiles/exts/CChain/logic/sampleNet.txt 
-n 5 -calc myFirstCalcSimulation 

This command will simulate our toy network five times and will save all output in CCOutput/stats/myFirstCalcSimulation folder.

The following table describes the structure and contents of the output folder.

table border=1 width=40% align=center bgcolor=grey cellspacing=0 cellnr Table 3: Contents of output generated during calculation mode. cellnr

tableend

July 26, 2008, at 10:19 PM by 68.229.177.191 -
Changed lines 175-176 from:

Save the file as sampleNodelist.txtc.

to:

Save the file as sampleNodelist.txt.

Changed lines 179-181 from:
./ChemChains -TT2ND -iNodeList inFiles/exts/FileConverter/sampleNodeList.txt 
-iTables inFiles/exts/FileConverter/sampleNet 
to:
./ChemChains -TT2ND 
-iNodeList inFiles/exts/FileConverter/sampleNodeList.txt 
-iTables inFiles/exts/FileConverter/sampleNet
Changed lines 249-250 from:
default:lower_limit1 higher_limit1 code1, lower_limit2 higher_limit2 code2
to:
default:lower_limit1 higher_limit1 code1,lower_limit2 higher_limit2 code2
Changed lines 256-257 from:
NodeName:lower_limit1 higher_limit1 code1, lower_limit2 higher_limit2 code2
to:
NodeName:lower_limit1 higher_limit1 code1,lower_limit2 higher_limit2 code2
July 26, 2008, at 10:17 PM by 68.229.177.191 -
Changed lines 94-95 from:
to:

Note: All parameters are case sensitive.

July 26, 2008, at 10:17 PM by 68.229.177.191 -
Changed lines 94-95 from:

Note: All parameters are case sensitive.

to:
July 26, 2008, at 10:17 PM by 68.229.177.191 -
Changed lines 89-92 from:
Input:name:initial/default value:random(R)/fixed(F):noise(N)/fixed/(F):time to be
 introduced:dose (in percentage):duration of the dosage

(explanation of each option below)

to:
Input:name:initial/default value:random(R)/fixed(F):
noise(N)/fixed/(F):time to be introduced:dose (in percentage):
duration of the dosage
July 26, 2008, at 10:16 PM by 68.229.177.191 -
Changed lines 56-58 from:
Bool:name:initial state[True|False]:input1,input2..inputN:list of states of input nodes 
for non-initial state(separated by comma)
to:
Bool:name:initial state[True|False]:input1,input2..inputN:list of 
states of input nodes for non-initial state(separated by comma)
July 26, 2008, at 10:15 PM by 68.229.177.191 -
Changed lines 146-147 from:
[@Output:output name:initial value:node name]
to:
Output:output name:initial value:node name
July 26, 2008, at 10:13 PM by 68.229.177.191 -
Changed line 93 from:

Note: Each input needs to be declared on a new line.

to:

Note: Each input needs to be declared on a new line.

Changed lines 134-135 from:
[Delay:name:initial value:parent node:iterations to wait]
to:
Delay:name:initial value:parent node:iterations to wait
Changed lines 139-140 from:
[Sustain:name:initial value:parent node:duration (in iteration units)]
to:
Sustain:name:initial value:parent node:duration (in iteration units)
Changed lines 146-147 from:
to:
[@Output:output name:initial value:node name]
July 26, 2008, at 10:12 PM by 68.229.177.191 -
Changed lines 41-44 from:
Sample toy network
Figure 1: Sample network.

As an example, let's assume a toy network (Figure 1) consisting of nodes A, B, C, and external input IN1, where green line (with an arrow) denotes positive regulation (i.e., activation) and red line (with a stop line) denotes negative regulation. Because this is a boolean network, each node has a an activation mechanism associated with it. Let's assume the activation mechanisms for the nodes of this network as follows:

to:
Sample toy network
Figure 1: Sample network.

As an example, let's assume a toy network (Figure 1) consisting of nodes A, B, C, and external input IN1, where green line (with an arrow) denotes positive regulation (e.g., activation) and red line (with a stop line) denotes negative regulation (e.g., inhibition). Because we're dealing with a boolean network, each node has an activation mechanism (represented by truth tables) associated with it. As an example, the activation mechanisms for the nodes of this network are as follows:

Changed lines 50-55 from:
Node Truth Tables
Figure 2: Truth tables for nodes A, B, and C, representing the sample network in Fig. 1

These activation mechanisms can be expressed as individual truth tables (Figure 2).

Once we have the network and truth tables established, we can create our network descriptor file using these tables. To create the file, the following syntax needs to be used:

to:
Node Truth Tables
Figure 2: Truth tables for nodes A, B, and C, representing the sample network in Fig. 1

These activation mechanisms can be expressed as individual truth tables (Figure 2).

Once the network and truth tables are established, they can be used to create the network descriptor file. Use the following syntax to create the file:

Changed lines 81-84 from:

For our example, we'll set the total time to 20 iterations and transient time to 10 as follows:

RunTime:10:20
to:

For our example, we'll set the total time to 100 iterations and transient time to 70 as follows:

RunTime:70:100
Changed lines 93-94 from:

Note: Each input needs to be declared on a new line

to:

Note: Each input needs to be declared on a new line. Note: All parameters are case sensitive.

Changed line 97 from:
  • Initial/Default value - self-explanatory
to:
  • Initial/Default value - True or False
Added lines 128-130:

Note: The name of the delay, sustain, and output nodes has to differ from the names of their inputs.

Changed lines 132-135 from:
[Needs content]
to:

To create a delay node, use the following syntax:

[Delay:name:initial value:parent node:iterations to wait]
Changed lines 137-140 from:
[Needs content]
to:

To create a delay node, use the following syntax:

[Sustain:name:initial value:parent node:duration (in iteration units)]
Changed lines 142-143 from:
[Needs content]
to:

Output nodes are nodes that will be printed out via ChemChains' visual mode.

To create a new output node, use the following syntax:

Changed lines 149-150 from:

Depending on which mode ChemChains is run in, different output will be generated. In general, both the visual and calculation modes will create and save their output in a directory called 'CCOutput' that will be created (if it already doesn't exist) in a directory directly above the directory with ChemChains software. Refer to the Running Modes section on detailed description of output generated by ChemChains.

to:

Depending on which mode ChemChains is run in, different output will be generated. In general, both the visual and calculation modes will create and save their output in a directory called 'CCOutput' that will be created (if it already doesn't exist) in a directory directly above the directory with ChemChains software. Refer to the Running Modes section on detailed description of output generated by ChemChains.

Deleted line 151:
Changed lines 159-160 from:

Thus, for the toy network (Figure 1) with truth tables as shown in Figure 2, create a new directory called "sampleNet" in "inFiles/exts/FileConverter", and three text files (A.csv, B.csv, and C.csv) with the truth tables in tab-delimited format and save them in the "inFiles/exts/FileConverter/sampleNet" directory.

to:

Thus, for the toy network (Figure 1) with truth tables as shown in Figure 2, create a new directory called "sampleNet" in "inFiles/exts/FileConverter", and three text files (A.csv, B.csv, and C.csv) with the truth tables in tab-delimited format and save them in the "inFiles/exts/FileConverter/sampleNet" directory.

Changed lines 170-174 from:
A 1 0
B 2 0
C 3 0
IN1 IN101 1
to:
A 1
B 2 1
C 3 1
IN1 IN4
July 26, 2008, at 08:22 PM by 68.229.177.191 -
Changed lines 36-37 from:

To simulate logical networks with ChemChains, two input files are required: the network descriptor file and simulation specification file.

to:

To simulate logical networks with ChemChains, two input files are required: the network descriptor file and simulation specification file (additional input files may be required for individual running modes.

Changed line 134 from:

ChemChains Output

to:

ChemChains Output

Changed lines 137-138 from:

Running Modes

to:

Running Modes

July 26, 2008, at 08:20 PM by 68.229.177.191 -
Changed lines 31-32 from:

To run ChemChains, users must provide several input files. Once simulations and/or analysis are initiated, ChemChains will create several types of output file formats. Both the input files, as well as the desired output format and the output files must be specified by users in the form of command-line parameters provided to ChemChains at the time of program initiation. To see all available options and command-line parameters run ChemChains with the -h flag.

to:

To run ChemChains, users must provide several input files. Once simulations and/or analysis are initiated, ChemChains will create several types of output file formats. Both the input files, as well as the desired output format and the output files must be specified by users in the form of command-line parameters provided to ChemChains at the time of program initiation. To see all available options and command-line parameters run ChemChains with the -h flag.

Changed line 35 from:

Input Files

to:

Input Files

July 26, 2008, at 08:19 PM by 68.229.177.191 -
Changed lines 36-38 from:

To simulate logical networks with ChemChains, two input files are required: the network descriptor file and simulation specification file.

Network Descriptor

to:

To simulate logical networks with ChemChains, two input files are required: the network descriptor file and simulation specification file.

Network Descriptor

Changed line 72 from:

Simulation Specification file

to:

Simulation Specification file

July 25, 2008, at 04:13 PM by 137.48.16.86 -
Changed line 3 from:

to:

July 25, 2008, at 04:11 PM by 137.48.16.86 -
Changed lines 3-5 from:

to:

July 25, 2008, at 03:59 PM by 137.48.16.86 -
Changed lines 3-6 from:

tocnum 1.1.1.1. indent

to:

Table of Contents (:toc:)(:num 1.1.1.1. :)(:indent:)


July 25, 2008, at 03:56 PM by 137.48.16.86 -
Changed lines 4-5 from:

tocnum 1.1.1.1. indent

to:

(:toc:)(:num 1.1.1.1. :)(:indent:)

July 25, 2008, at 03:50 PM by 137.48.16.86 -
Changed lines 102-103 from:
Advanced Example: For each simulation, to set IN1 between 0-10% for the first 30 iterations, 11-50% for iterations 31-70, and 51-100% for the remaining simulation time, add the following:
to:
Advanced Example: For each simulation, to set IN1 between 0-10% for the first 30 iterations, 11-50% for iterations 31-70, and 51-100% for the remaining simulation time, add the following:
Changed lines 105-106 from:
to:

July 25, 2008, at 03:49 PM by 137.48.16.86 -
Added line 106:
July 25, 2008, at 03:49 PM by 137.48.16.86 -
Changed lines 2-3 from:

font-size=smaller bgcolor=#e0e0ff%

to:

July 25, 2008, at 03:46 PM by 137.48.16.86 -
Changed lines 2-3 from:

to:

font-size=smaller bgcolor=#e0e0ff%

July 25, 2008, at 03:46 PM by 137.48.16.86 -
Changed lines 102-103 from:
%div >advanced apply=div%< Advanced Example: For each simulation, to set IN1 between 0-10% for the first 30 iterations, 11-50% for iterations 31-70, and 51-100% for the remaining simulation time, add the following:
to:
Advanced Example: For each simulation, to set IN1 between 0-10% for the first 30 iterations, 11-50% for iterations 31-70, and 51-100% for the remaining simulation time, add the following:
Changed line 105 from:
%div > apply=div%<
to:
July 25, 2008, at 03:45 PM by 137.48.16.86 -
Changed lines 2-3 from:

to:

Changed lines 102-103 from:

Advanced Example: For each simulation, to set IN1 between 0-10% for the first 30 iterations, 11-50% for iterations 31-70, and 51-100% for the remaining simulation time, add the following:

to:
%div >advanced apply=div%< Advanced Example: For each simulation, to set IN1 between 0-10% for the first 30 iterations, 11-50% for iterations 31-70, and 51-100% for the remaining simulation time, add the following:
Changed line 105 from:
to:
%div > apply=div%<
July 25, 2008, at 03:44 PM by 137.48.16.86 -
Changed lines 2-3 from:

%

to:

July 25, 2008, at 03:43 PM by 137.48.16.86 -
Changed lines 2-3 from:
to:

%

Changed lines 100-101 from:
Input:IN1:True:F:F:1:10:20
to:
Input:IN1:True:F:F:1:10:99

Advanced Example: For each simulation, to set IN1 between 0-10% for the first 30 iterations, 11-50% for iterations 31-70, and 51-100% for the remaining simulation time, add the following:

Input:IN1:True:R:F:1:0-10:29,30:11-50:39,71:51-100:29
July 25, 2008, at 03:32 PM by 137.48.16.86 -
Changed lines 242-246 from:

-n 5 -calc myFirstCalcSimulation @]

to:

-n 5 -calc myFirstCalcSimulation @]

Random Initial Conditions

ChemChains can be run with randomly generated conditions for every simulation. To run ChemChains with random initial conditions enabled, use the '-rand_init' flag.

July 25, 2008, at 03:28 PM by 137.48.16.86 -
Changed lines 71-72 from:
  • Runtime - specifies the overall length of each simulation, as well as the number of iterations (transient time) before any analysis is conducted.
to:
  • Runtime - specifies the overall length of each simulation, as well as the number of iterations (transient time) before any analysis is conducted.
Changed lines 79-80 from:
  • Inputs - external inputs (IN1 in the above toy network)
to:
  • Inputs - external inputs (IN1 in the above toy network)
Changed lines 101-103 from:
  • Noise
The noise variable allows the input activity level to randomly bounce around the defined value within a specified range. For example, if the activity level for IN1 is set to 10% with a noise range of 5, the actual activity level at time t will be 10%+/-5.
to:
  • Noise
The noise variable allows the input activity level to randomly bounce around the defined value within a specified range. For example, if the activity level for IN1 is set to 10% with a noise range of 5, the actual activity level at time t will be 10+/-5%.
Changed line 110 from:
  • Mutation
to:
  • Mutation
Changed line 116 from:
  • Delay Nodes
to:
  • Delay Nodes
Changed line 118 from:
  • Sustain Nodes
to:
  • Sustain Nodes
Changed line 120 from:
  • Output Nodes
to:
  • Output Nodes
July 25, 2008, at 03:25 PM by 137.48.16.86 -
Changed lines 102-103 from:
The noise variable allows the input activity level to randomly bounce around the defined value within a specified range. For example, if the activity level for IN1 is set to 10% with a noise range of 5, the actual activity level, at time t, will be 10%+/-5.
to:
The noise variable allows the input activity level to randomly bounce around the defined value within a specified range. For example, if the activity level for IN1 is set to 10% with a noise range of 5, the actual activity level at time t will be 10%+/-5.
July 25, 2008, at 03:23 PM by 137.48.16.86 -
Changed lines 30-31 from:

To simulate logical networks with ChemChains, two input files are required: the network descriptor and a simulation specification file.

to:

To simulate logical networks with ChemChains, two input files are required: the network descriptor file and simulation specification file.

July 25, 2008, at 03:12 PM by 137.48.16.86 -
Changed lines 1-2 from:

to:

Added lines 55-56:

Note: The declaration of each node is on a new line.

Changed line 61 from:

Note: that the declaration of each node is on a new line.

to:
Changed lines 81-82 from:

Syntax to declare an input (note that each input needs to be declared on a new line:

to:

Syntax to declare an input:

Added lines 87-88:

Note: Each input needs to be declared on a new line

Added lines 143-144:

Note: If the initial value is False (i.e., 0 ) we can leave the third column empty.

Changed line 150 from:
Note that if the initial value is False (i.e., 0 ) we can leave the third column empty.
to:
Changed lines 165-166 from:

Note: Make sure that you have created at least one output node in the simulation specification file!

to:

Note: Make sure that you have created at least one output node in the simulation specification file!

Changed lines 171-172 from:

Note: When running in the visual mode, ChemChains can run only one simulation at a time. To run multiple simulations in an automated fashion, run ChemChains in calculation mode.

to:

Note: When running in the visual mode, ChemChains can run only one simulation at a time. To run multiple simulations in an automated fashion, run ChemChains in calculation mode.

July 25, 2008, at 03:06 PM by 137.48.16.86 -
Added lines 1-2:

Changed line 59 from:

Note that the declaration of each node is on a new line.

to:

Note: that the declaration of each node is on a new line.

July 25, 2008, at 03:00 PM by 137.48.16.86 -
Changed lines 1-2 from:

tocnum 1.1.1.1indent

to:

(:toc:)(:num 1.1.1.1. :)(:indent:)

July 25, 2008, at 02:59 PM by 137.48.16.86 -
Changed lines 1-2 from:

tocnum 1.1.1.1.1indent

to:

(:toc:)(:num 1.1.1.1:)(:indent:)

Changed line 225 from:

List of nodes to be analyzed'''

to:
  • List of nodes to be analyzed
July 25, 2008, at 02:59 PM by 137.48.16.86 -
Changed line 225 from:
  • List of nodes to be analyzed
to:

List of nodes to be analyzed'''

July 25, 2008, at 02:58 PM by 137.48.16.86 -
Changed lines 1-2 from:

tocnum 1.1.1.1indent

to:

(:toc:)(:num 1.1.1.1.1:)(:indent:)

July 25, 2008, at 02:57 PM by 137.48.16.86 -
Changed lines 1-2 from:

tocnum 1.1.1indent

to:

(:toc:)(:num 1.1.1.1:)(:indent:)

July 25, 2008, at 02:53 PM by 137.48.16.86 -
Changed line 210 from:
  • Settings File
to:
  • Settings File
Changed line 225 from:
  • List of nodes to be analyzed
to:
  • List of nodes to be analyzed
July 25, 2008, at 02:52 PM by 137.48.16.86 -
Changed line 210 from:

Settings File

to:
  • Settings File
Changed line 225 from:

List of nodes to be analyzed

to:
  • List of nodes to be analyzed
July 25, 2008, at 02:51 PM by 137.48.16.86 -
Changed line 225 from:
  • List of nodes to be analyzed
to:

List of nodes to be analyzed

July 25, 2008, at 02:50 PM by 137.48.16.86 -
Changed lines 1-2 from:

toc

to:

(:toc:)(:num 1.1.1:)(:indent:)

Added line 9:

(:num:)

July 25, 2008, at 02:40 PM by 137.48.16.86 -
Deleted lines 0-12:

table border=1 width=40% align=left bgcolor=#cccc99 cellspacing=0 cellnr Navigation Links cellnr num

  1. Requirements
  2. Installation
  3. How-to

tableend

Changed line 209 from:
  • Settings File
to:

Settings File

July 25, 2008, at 02:40 PM by 137.48.16.86 -
Deleted line 15:

num

Changed line 221 from:

nonum

to:
July 25, 2008, at 02:38 PM by 137.48.16.86 -
Added lines 14-15:

(:toc:)

July 25, 2008, at 02:31 PM by 137.48.16.86 -
Added line 5:

(:num:)

Changed lines 220-221 from:

Settings File

to:

(:nonum:)

  • Settings File
Changed line 236 from:

List of nodes to be analyzed

to:
  • List of nodes to be analyzed
July 25, 2008, at 02:26 PM by 137.48.16.86 -
Changed line 127 from:

ChemChains Output

to:

ChemChains Output

July 25, 2008, at 02:25 PM by 137.48.16.86 -
Changed lines 20-21 from:

Installation

Linux

to:

Installation

Linux

Changed line 25 from:

Windows

to:

Windows

Changed lines 29-30 from:

Basic How-to

Introduction

to:

Basic How-to

Introduction

Changed line 37 from:

Input Files

to:

Input Files

Changed line 40 from:

Network Descriptor

to:

Network Descriptor

Changed line 72 from:

Simulation Specification file

to:

Simulation Specification file

Changed line 127 from:

ChemChains Output

to:

ChemChains Output

Changed lines 130-131 from:

Running Modes

to:

Running Modes

Changed line 134 from:

File Conversion Mode

to:

File Conversion Mode

Changed line 160 from:

Visual Mode

to:

Visual Mode

Changed line 175 from:

Calculation Mode

to:

Calculation Mode

Changed line 216 from:

Patterns Analysis

to:

Patterns Analysis

Changed line 219 from:

Settings File

to:

Settings File

Changed line 234 from:

List of nodes to be analyzed

to:

List of nodes to be analyzed

July 25, 2008, at 02:24 PM by 137.48.16.86 -
Changed line 13 from:

(:num;)

to:

(:num:)

July 25, 2008, at 02:23 PM by 137.48.16.86 -
Changed lines 13-14 from:

Requirements

to:

(:num;)

Requirements

July 24, 2008, at 12:25 PM by 137.48.16.86 -
Changed line 5 from:
to:
Changed lines 7-11 from:
to:
July 24, 2008, at 12:25 PM by 137.48.16.86 -
Changed line 5 from:
to:
July 24, 2008, at 12:24 PM by 137.48.16.86 -
Changed line 5 from:
to:
July 24, 2008, at 10:44 AM by 137.48.16.86 -
Changed lines 43-44 from:
Sample toy network
Figure 1: Sample network.
to:
Sample toy network
Figure 1: Sample network.
Changed lines 52-53 from:
Node Truth Tables
Figure 2: Truth tables for nodes A, B, and C, representing the sample network in Fig. 1
to:
Node Truth Tables
Figure 2: Truth tables for nodes A, B, and C, representing the sample network in Fig. 1
July 24, 2008, at 10:41 AM by 137.48.16.86 -
Changed lines 45-47 from:

As an example, let's assume a toy network (Figure 1) consisting of nodes A, B, and C, where green line (with an arrow) denotes positive regulation (i.e., activation) and red line (with a stop line) denotes negative regulation. Because this is a boolean network, each node has a an activation mechanism associated with it. Let's assume the activation mechanisms for the nodes of this network as follows:

  • Node A: Node A is activated by node C
to:

As an example, let's assume a toy network (Figure 1) consisting of nodes A, B, C, and external input IN1, where green line (with an arrow) denotes positive regulation (i.e., activation) and red line (with a stop line) denotes negative regulation. Because this is a boolean network, each node has a an activation mechanism associated with it. Let's assume the activation mechanisms for the nodes of this network as follows:

  • Node A: Node A is activated by node C.
Changed lines 49-50 from:
  • Node C: Node C is activated by node B
to:
  • Node C: Node C is activated by input node IN1 and node B.
  • Input node IN1: this node is an input node and hence has no input.
July 24, 2008, at 10:36 AM by 137.48.16.86 -
Changed lines 67-68 from:

Once finished, save the file as myNetwork.txtin inFiles/CChain/logic/ and move on to the simulation specification file.

to:

Once finished, save the file as inFiles/CChain/logic/myNetwork.txt.

The next section describes how to create the simulation specification file.

July 24, 2008, at 10:35 AM by 137.48.16.86 -
Changed lines 67-68 from:

Once finished we can save the file as myNetwork.txtand move on to the simulation specification file.

to:

Once finished, save the file as myNetwork.txtin inFiles/CChain/logic/ and move on to the simulation specification file.

July 24, 2008, at 10:33 AM by 137.48.16.86 -
Changed lines 63-65 from:
Bool:B:False:A,C:FF,FT,TT
Bool:C:False:B:T
to:
Bool:B:True:A,C:FF,FT,TT
Bool:C:True:IN1,B:FF
July 24, 2008, at 10:30 AM by 137.48.16.86 -
Changed lines 51-52 from:
Node Truth Tables
Figure 2: Truth tables for nodes A, B, and C, representing the sample network in Figure 1
to:
Node Truth Tables
Figure 2: Truth tables for nodes A, B, and C, representing the sample network in Fig. 1
July 24, 2008, at 10:29 AM by 137.48.16.86 -
Changed lines 51-52 from:
Node Truth Tables
Figure 2: Truth tables for nodes A, B, and C.
to:
Node Truth Tables
Figure 2: Truth tables for nodes A, B, and C, representing the sample network in Figure 1
July 23, 2008, at 05:22 PM by 137.48.16.86 -
Added line 79:
Added line 108:
Added line 110:
Added line 115:
Changed line 160 from:

[@./ChemChains -ilogic inFiles/exts/CChain/logic/sampleNet.txt

to:
[@./ChemChains -ilogic inFiles/exts/CChain/logic/sampleNet.txt
Changed line 192 from:

[@./ChemChains -ilogic inFiles/exts/CChain/logic/sampleNet.txt

to:
[@./ChemChains -ilogic inFiles/exts/CChain/logic/sampleNet.txt
Changed line 236 from:

[@./ChemChains -ilogic inFiles/exts/CChain/logic/sampleNet.txt

to:
[@./ChemChains -ilogic inFiles/exts/CChain/logic/sampleNet.txt
July 23, 2008, at 05:17 PM by 137.48.16.86 -
Changed lines 85-87 from:
Input:name:initial/default value:random(R)/fixed(F):noise(N)/fixed/(F):time to be introduced:dose 
(in percentage):duration of the dosage
(explanation of each option below)
to:
Input:name:initial/default value:random(R)/fixed(F):noise(N)/fixed/(F):time to be
 introduced:dose (in percentage):duration of the dosage

(explanation of each option below)

July 23, 2008, at 05:16 PM by 137.48.16.86 -
Changed lines 57-59 from:
Bool:name:initial state[True|False]:input1,input2..inputN:list of states of input nodes for non-initial
state(separated by comma)
to:
Bool:name:initial state[True|False]:input1,input2..inputN:list of states of input nodes 
for non-initial state(separated by comma)
Changed lines 155-156 from:

[@./ChemChains -ilogic inFiles/exts/CChain/logic/sampleNet.txt -ispecs inFiles/exts/CChain/logic/sampleNet.txt

to:

[@./ChemChains -ilogic inFiles/exts/CChain/logic/sampleNet.txt -ispecs inFiles/exts/CChain/logic/sampleNet.txt

Changed lines 187-188 from:

[@./ChemChains -ilogic inFiles/exts/CChain/logic/sampleNet.txt -ispecs inFiles/exts/CChain/logic/sampleNet.txt

to:

[@./ChemChains -ilogic inFiles/exts/CChain/logic/sampleNet.txt -ispecs inFiles/exts/CChain/logic/sampleNet.txt

July 23, 2008, at 05:14 PM by 137.48.16.86 -
Changed lines 229-230 from:

[@./ChemChains -ilogic inFiles/exts/CChain/logic/sampleNet.txt -ispecs inFiles/exts/CChain/logic/sampleNet.txt -patterns -isettings inFiles/exts/exts/Patterns/settings.txt -inodes nFiles/exts/exts/Patterns/sampleOutNodes.txt

to:

[@./ChemChains -ilogic inFiles/exts/CChain/logic/sampleNet.txt -ispecs inFiles/exts/CChain/logic/sampleNet.txt -patterns -isettings inFiles/exts/exts/Patterns/settings.txt -inodes nFiles/exts/exts/Patterns/sampleOutNodes.txt

July 23, 2008, at 05:13 PM by 137.48.16.86 -
Changed lines 149-150 from:
./ChemChains -TT2ND -iNodeList inFiles/exts/FileConverter/sampleNodeList.txt -iTables inFiles/exts/FileConverter/sampleNet
to:
./ChemChains -TT2ND -iNodeList inFiles/exts/FileConverter/sampleNodeList.txt 
-iTables inFiles/exts/FileConverter/sampleNet 
July 23, 2008, at 05:13 PM by 137.48.16.86 -
Changed lines 57-58 from:
Bool:name:initial state[True|False]:input1,input2..inputN:list of states of input nodes for non-initial state(separated by comma)
to:
Bool:name:initial state[True|False]:input1,input2..inputN:list of states of input nodes for non-initial
state(separated by comma)
July 23, 2008, at 05:11 PM by 137.48.16.86 -
Changed lines 153-154 from:

./ChemChains -ilogic inFiles/exts/CChain/logic/sampleNet.txt -ispecs inFiles/exts/CChain/logic/sampleNet.txt -vis myFirstSimulation.txt

to:
./ChemChains -ilogic inFiles/exts/CChain/logic/sampleNet.txt -ispecs inFiles/exts/CChain/logic/sampleNet.txt 
-vis myFirstSimulation.txt 
July 23, 2008, at 05:10 PM by 137.48.16.86 -
Changed lines 183-184 from:

./ChemChains -ilogic inFiles/exts/CChain/logic/sampleNet.txt -ispecs inFiles/exts/CChain/logic/sampleNet.txt -n 5 -calc myFirstCalcSimulation

to:
./ChemChains -ilogic inFiles/exts/CChain/logic/sampleNet.txt -ispecs inFiles/exts/CChain/logic/sampleNet.txt 
-n 5 -calc myFirstCalcSimulation 
July 23, 2008, at 05:10 PM by 137.48.16.86 -
Changed lines 84-85 from:
Input:name:initial/default value:random(R)/fixed(F):noise(N)/fixed/(F):time to be introduced:dose (in percentage):duration of the dosage (explanation of each option below)
to:
Input:name:initial/default value:random(R)/fixed(F):noise(N)/fixed/(F):time to be introduced:dose 
(in percentage):duration of the dosage
(explanation of each option below)
July 23, 2008, at 05:07 PM by 137.48.16.86 -
Changed lines 224-225 from:
./ChemChains -ilogic inFiles/exts/CChain/logic/sampleNet.txt -ispecs inFiles/exts/CChain/logic/sampleNet.txt [[<<]]
-patterns -isettings inFiles/exts/exts/Patterns/settings.txt -n 5 -inodes nFiles/exts/exts/Patterns/sampleOutNodes.txt -calc myFirstCalcSimulation 
to:
./ChemChains -ilogic inFiles/exts/CChain/logic/sampleNet.txt -ispecs inFiles/exts/CChain/logic/sampleNet.txt
-patterns -isettings inFiles/exts/exts/Patterns/settings.txt -inodes nFiles/exts/exts/Patterns/sampleOutNodes.txt
-n 5 -calc myFirstCalcSimulation 
July 23, 2008, at 05:07 PM by 137.48.16.86 -
Changed lines 224-225 from:

./ChemChains -ilogic inFiles/exts/CChain/logic/sampleNet.txt -ispecs inFiles/exts/CChain/logic/sampleNet.txt [[<<]]-patterns -isettings inFiles/exts/exts/Patterns/settings.txt -n 5 -inodes nFiles/exts/exts/Patterns/sampleOutNodes.txt -calc myFirstCalcSimulation

to:
./ChemChains -ilogic inFiles/exts/CChain/logic/sampleNet.txt -ispecs inFiles/exts/CChain/logic/sampleNet.txt [[<<]]
-patterns -isettings inFiles/exts/exts/Patterns/settings.txt -n 5 -inodes nFiles/exts/exts/Patterns/sampleOutNodes.txt -calc myFirstCalcSimulation 
July 23, 2008, at 05:06 PM by 137.48.16.86 -
Changed line 224 from:

./ChemChains -ilogic inFiles/exts/CChain/logic/sampleNet.txt -ispecs inFiles/exts/CChain/logic/sampleNet.txt [<<]-patterns -isettings inFiles/exts/exts/Patterns/settings.txt -n 5 -inodes nFiles/exts/exts/Patterns/sampleOutNodes.txt -calc myFirstCalcSimulation

to:

./ChemChains -ilogic inFiles/exts/CChain/logic/sampleNet.txt -ispecs inFiles/exts/CChain/logic/sampleNet.txt [[<<]]-patterns -isettings inFiles/exts/exts/Patterns/settings.txt -n 5 -inodes nFiles/exts/exts/Patterns/sampleOutNodes.txt -calc myFirstCalcSimulation

July 23, 2008, at 05:05 PM by 137.48.16.86 -
Changed line 224 from:

./ChemChains -ilogic inFiles/exts/CChain/logic/sampleNet.txt -ispecs inFiles/exts/CChain/logic/sampleNet.txt -patterns -isettings inFiles/exts/exts/Patterns/settings.txt -n 5 -inodes nFiles/exts/exts/Patterns/sampleOutNodes.txt -calc myFirstCalcSimulation

to:

./ChemChains -ilogic inFiles/exts/CChain/logic/sampleNet.txt -ispecs inFiles/exts/CChain/logic/sampleNet.txt [<<]-patterns -isettings inFiles/exts/exts/Patterns/settings.txt -n 5 -inodes nFiles/exts/exts/Patterns/sampleOutNodes.txt -calc myFirstCalcSimulation

July 23, 2008, at 04:59 PM by 137.48.16.86 -
Added lines 117-119:

ChemChains Output

Depending on which mode ChemChains is run in, different output will be generated. In general, both the visual and calculation modes will create and save their output in a directory called 'CCOutput' that will be created (if it already doesn't exist) in a directory directly above the directory with ChemChains software. Refer to the Running Modes section on detailed description of output generated by ChemChains.

Changed lines 150-151 from:

Although, ChemChains is a command-line program, it can output visual simulation results via its visual mode. To run ChemChains in visual mode, use the “-vis” flag.

to:

Although, ChemChains is a command-line program, it can output visual simulation results via its visual mode. To run ChemChains in visual mode, use the “-vis” flag. To simulate the toy network using the simulation specification file both created in the previous sections run ChemChains as follows:

./ChemChains -ilogic inFiles/exts/CChain/logic/sampleNet.txt -ispecs inFiles/exts/CChain/logic/sampleNet.txt -vis myFirstSimulation.txt

Note: Make sure that you have created at least one output node in the simulation specification file!

Once the simulation finishes, a new file will be created in the ChemChains output folder, in a text file called “myFirstSimulation.txt”.

Open the text file and we should see output similar to the Figure 3. ('*' denotes the active state of the node, while '.' represents the OFF state)

Note: When running in the visual mode, ChemChains can run only one simulation at a time. To run multiple simulations in an automated fashion, run ChemChains in calculation mode.

Changed lines 163-166 from:

[Needs content] [Needs more content...]

Advanced How-to

[Needs content]

to:

Calculation mode provide ChemChains users the ability to run thousands of automated simulations and subsequently use the generated data to analyze the dynamics of the simulated model.

To run ChemChains in the calculation mode, use the '-calc' flag. Other flags available within the calculation mode are listed in Table 2.

(:table border=1 width=40% align=center bgcolor=grey cellspacing=0 :) (:cellnr:) Table 2: List of flags available in the calculation mode. (:cellnr:)

(:tableend:)

You can run ChemChains (using our previously created network descriptor and simulation specification files) in the calculation mode in the most basic way (without the use of any extensions) as follows:

./ChemChains -ilogic inFiles/exts/CChain/logic/sampleNet.txt -ispecs inFiles/exts/CChain/logic/sampleNet.txt -n 5 -calc myFirstCalcSimulation

This command will simulate our toy network five times and will save all output in CCOutput/stats/myFirstCalcSimulation folder.

The following table describes the structure and contents of the output folder.

(:table border=1 width=40% align=center bgcolor=grey cellspacing=0 :) (:cellnr:) Table 3: Contents of output generated during calculation mode. (:cellnr:)

(:tableend:)

Patterns Analysis

To perform patterns analysis, ChemChains must be initiated in the calculation mode (as described above), and using '-patterns' flag. When using patterns to perform analysis, two additional input files are required: i) the settings file and ii) a text file with a list of nodes that will undergo the pattern analysis.

Settings File

The patterns settings file defines activity ranges that will form patterns.

For your convenience, a sample settings files has already been created. You can find it and edit it in inFiles/exts/Patterns/settings.txt. The file contains two groups of settings: i) default settings that are applied on all nodes subjected to patterns analysis and ii) node specific settings that apply to only one node at a time. The syntax is as follows:

Default settings:

default:lower_limit1 higher_limit1 code1, lower_limit2 higher_limit2 code2

The sample settings provided should have the following:

default:0 9 0;10 29 1;30 100 2,

which means the activity of all nodes being analyzed will be categorized into three ranges: 0-9% (all nodes in this range will be coded “0”), 10-29% (all nodes in this range will be coded “1”), and 30-100% (all nodes in this range will be coded “2”)

Node specific settings:

NodeName:lower_limit1 higher_limit1 code1, lower_limit2 higher_limit2 code2

List of nodes to be analyzed

An example of this file is also supplied with the latest ChemChains release, and is located in inFiles/exts/Patterns/sampleOutNodes.txt. In this file, each node to be analyzed with the patterns extension is entered on a new line.

To run ChemChains using these input files, type in the following command:

./ChemChains -ilogic inFiles/exts/CChain/logic/sampleNet.txt -ispecs inFiles/exts/CChain/logic/sampleNet.txt -patterns -isettings inFiles/exts/exts/Patterns/settings.txt -n 5 -inodes nFiles/exts/exts/Patterns/sampleOutNodes.txt -calc myFirstCalcSimulation

July 22, 2008, at 10:19 PM by 68.229.177.191 -
Added lines 1-153:

(:table border=1 width=40% align=left bgcolor=#cccc99 cellspacing=0 :) (:cellnr:) Navigation Links (:cellnr:)

(:tableend:)

Requirements

ChemChains is a platform independent command-line software written in C++, that has been tested on Linux and Windows platforms.

To run ChemChains in Windows, a Linux-like environment is necessary. For example, you can download and install the freely available cygwin from here.

Installation

Linux

  1. Open a new terminal window
  2. Type: make (This should create an executable file called ChemChains)

Windows

  1. Start Cygwin
  2. In the Cygwin terminal window, type: make (This should create an executable file called ChemChains)

Basic How-to

Introduction

This section will provide you with the most basic ways of simulating your first network model using ChemChains.

To run ChemChains, users must provide several input files. Once simulations and/or analysis are initiated, ChemChains will create several types of output file formats. Both the input files, as well as the desired output format and the output files must be specified by users in the form of command-line parameters provided to ChemChains at the time of program initiation. To see all available options and command-line parameters run ChemChains with the -h flag.

./ChemChains -h

Input Files

To simulate logical networks with ChemChains, two input files are required: the network descriptor and a simulation specification file.

Network Descriptor

Network descriptor is a syntax-specific text file that stores the network, and logic for each node.

Sample toy network
Figure 1: Sample network.

As an example, let's assume a toy network (Figure 1) consisting of nodes A, B, and C, where green line (with an arrow) denotes positive regulation (i.e., activation) and red line (with a stop line) denotes negative regulation. Because this is a boolean network, each node has a an activation mechanism associated with it. Let's assume the activation mechanisms for the nodes of this network as follows:

  • Node A: Node A is activated by node C
  • Node B: Node B is inhibited by node A and activated by node C. In addition, node C is a required positive regulator. The negative regulation is dominant over the positive one.
  • Node C: Node C is activated by node B

Node Truth Tables
Figure 2: Truth tables for nodes A, B, and C.

These activation mechanisms can be expressed as individual truth tables (Figure 2).

Once we have the network and truth tables established, we can create our network descriptor file using these tables. To create the file, the following syntax needs to be used:

Bool:name:initial state[True|False]:input1,input2..inputN:list of states of input nodes for non-initial state(separated by comma)

Thus, the network descriptor for our toy network can look like:

Bool:A:False:C:T
Bool:B:False:A,C:FF,FT,TT
Bool:C:False:B:T

Note that the declaration of each node is on a new line. Once finished we can save the file as myNetwork.txtand move on to the simulation specification file.

Simulation Specification file

ChemChains is a feature-rich logic network simulation software, which offers users many advanced simulation options. These options are specified by users in the specification file, the second of the required input files, that is loaded into the program before each simulation experiment.

The following describes the various options contained within this file:

  • Runtime - specifies the overall length of each simulation, as well as the number of iterations (transient time) before any analysis is conducted.

Syntax: RunTime:TransientTime:TotalTime

For our example, we'll set the total time to 20 iterations and transient time to 10 as follows:

RunTime:10:20

  • Inputs - external inputs (IN1 in the above toy network)

Syntax to declare an input (note that each input needs to be declared on a new line:

Input:name:initial/default value:random(R)/fixed(F):noise(N)/fixed/(F):time to be introduced:dose (in percentage):duration of the dosage (explanation of each option below)

  • Name -self-explanatory
  • Initial/Default value - self-explanatory
  • Random(R)/Fixed(F) - this parameter specifies whether the percentage ON should be as specified by the user or generated randomly
  • Noise(N)/Fixed(F) - specifies whether the input will be set on a periodic cycle or randomly bounce around within a given range (see Noise below)
  • Time to be introduced - time when a given percentage ON will come into an effect
  • Dosage - specified percent ON for a given input (integer from 0 to 100)
  • Duration of the dosage - the number of iterations the dosage amount will be exerted on the input (note that if the duration is shorter than the total runtime, the input will be set to 0% ON once the duration period is achieved)

To declare input IN1, with True as the initial condition, fixed percentage activity on a periodic cycle set to 10%, and effective for the entire simulation length add the following line in the specification file:

Input:IN1:True:F:F:1:10:20

  • Noise
The noise variable allows the input activity level to randomly bounce around the defined value within a specified range. For example, if the activity level for IN1 is set to 10% with a noise range of 5, the actual activity level, at time t, will be 10%+/-5.

To measure the current level of activity for each input during a simulation, ChemChains uses a sliding window (user pre-defined length) approach which allows the program to know whether the activity is within the desired percentage ON. In this example we'll set the sliding window to 5. Syntax: Noise:Window size:noise level To set the noise level as specified above, add the following line to the specification file:

Noise:5:5
  • Mutation

The mutation parameter enables users to turn ON/OFF any node in the network to perform mutagenesis studies. When the node(s) is mutated, the corresponding truth table is ignored by the simulation engine and the activity of the node becomes fixed for the entire course of the simulation. For example, to turn off node A, you would add the following line to the specification file:

Mutation:OFF:A

To mutate node A to be constitutively active, replace 'OFF' with 'ON'.

  • Delay Nodes
[Needs content]
  • Sustain Nodes
[Needs content]
  • Output Nodes
[Needs content]

Running Modes

The most recent version of ChemChains can be ran in three modes, one of which is a network construction mode (or File Conversion) and the remaining two are simulation modes.

File Conversion Mode

As mentioned above, to run ChemChains, a file with the network description is required. This file can be created manually as described in the previous section, or automatically from a provided set of truth tables for individual nodes.

These truth tables need to be in the form of a tab-delimited text file. Each table must be in a separate file which should be named the same as the name of the node of interest.

Thus, for the toy network (Figure 1) with truth tables as shown in Figure 2, create a new directory called "sampleNet" in "inFiles/exts/FileConverter", and three text files (A.csv, B.csv, and C.csv) with the truth tables in tab-delimited format and save them in the "inFiles/exts/FileConverter/sampleNet" directory.

In addition, we need to create another file with the list of nodes comprising our network. In this file, each node has two properties, nodeID and initial value, associated with it. Each node and its properties need to be on a new line. The mentioned node properties need to be tab-separated.

The syntax is as follows:

NodeName NodeID InitialValue

Sample node list for our network will look like:

A 1 0
B 2 0
C 3 0
IN1 IN101 1
Note that if the initial value is False (i.e., 0 ) we can leave the third column empty.

Save the file as sampleNodelist.txtc.

To create the Network Descriptor file from existing truth tables, run ChemChains with the following parameters:

./ChemChains -TT2ND -iNodeList inFiles/exts/FileConverter/sampleNodeList.txt -iTables inFiles/exts/FileConverter/sampleNet

Visual Mode

Although, ChemChains is a command-line program, it can output visual simulation results via its visual mode. To run ChemChains in visual mode, use the “-vis” flag.

Calculation Mode

[Needs content] [Needs more content...]

Advanced How-to

[Needs content]

July 18, 2008, at 09:19 PM by 68.229.177.191 -
Deleted lines 0-144:

table border=1 width=40% align=left bgcolor=#cccc99 cellspacing=0 cellnr Navigation Links cellnr

tableend

Requirements

ChemChains is a platform independent command-line software written in C++, that has been tested on Linux and Windows platforms.

To run ChemChains in Windows, a Linux-like environment is necessary. For example, you can download and install the freely available cygwin from here.

Installation

Linux

  1. Open a new terminal window
  2. Type: make (This should create an executable file called ChemChains)

Windows

  1. Start Cygwin
  2. In the Cygwin terminal window, type: make (This should create an executable file called ChemChains)

Basic How-to

Introduction

This section will provide you with the most basic ways of simulating your first network model using ChemChains.

To run ChemChains, users must provide several input files. Once simulations and/or analysis are initiated, ChemChains will create several types of output file formats. Both the input files, as well as the desired output format and the output files must be specified by users in the form of command-line parameters provided to ChemChains at the time of program initiation. To see all available options and command-line parameters run ChemChains with the -h flag.

./ChemChains -h

Input Files

To simulate logical networks with ChemChains, two input files are required: the network descriptor and a simulation specification file.

Network Descriptor

Network descriptor is a syntax-specific text file that stores the network, and logic for each node.

Sample toy network
Figure 1: Sample network.

As an example, let's assume a toy network (Figure 1) consisting of nodes A, B, and C, where green line (with an arrow) denotes positive regulation (i.e., activation) and red line (with a stop line) denotes negative regulation. Because this is a boolean network, each node has a an activation mechanism associated with it. Let's assume the activation mechanisms for the nodes of this network as follows:

  • Node A: Node A is activated by node C
  • Node B: Node B is inhibited by node A and activated by node C. In addition, node C is a required positive regulator. The negative regulation is dominant over the positive one.
  • Node C: Node C is activated by node B

Node Truth Tables
Figure 2: Truth tables for nodes A, B, and C.

These activation mechanisms can be expressed as individual truth tables (Figure 2).

Once we have the network and truth tables established, we can create our network descriptor file using these tables. To create the file, the following syntax needs to be used:

Bool:name:initial state[True|False]:input1,input2..inputN:list of states of input nodes for non-initial state(separated by comma)

Thus, the network descriptor for our toy network can look like:

Bool:A:False:C:T
Bool:B:False:A,C:FF,FT,TT
Bool:C:False:B:T

Note that the declaration of each node is on a new line. Once finished we can save the file as myNetwork.txtand move on to the simulation specification file.

Simulation Specification file

ChemChains is a feature-rich logic network simulation software, which offers users many advanced simulation options. These options are specified by users in the specification file, the second of the required input files, that is loaded into the program before each simulation experiment.

The following describes the various options contained within this file:

  • Runtime - specifies the overall length of each simulation, as well as the number of iterations (transient time) before any analysis is conducted.

Syntax: RunTime:TransientTime:TotalTime

For our example, we'll set the total time to 20 iterations and transient time to 10 as follows:

RunTime:10:20

  • Inputs - external inputs (IN1 in the above toy network)

Syntax to declare an input (note that each input needs to be declared on a new line:

Input:name:initial/default value:random(R)/fixed(F):noise(N)/fixed/(F):time to be introduced:dose (in percentage):duration of the dosage (explanation of each option below)

  • Name -self-explanatory
  • Initial/Default value - self-explanatory
  • Random(R)/Fixed(F) - this parameter specifies whether the percentage ON should be as specified by the user or generated randomly
  • Noise(N)/Fixed(F) - specifies whether the input will be set on a periodic cycle or randomly bounce around within a given range (see Noise below)
  • Time to be introduced - time when a given percentage ON will come into an effect
  • Dosage - specified percent ON for a given input (integer from 0 to 100)
  • Duration of the dosage - the number of iterations the dosage amount will be exerted on the input (note that if the duration is shorter than the total runtime, the input will be set to 0% ON once the duration period is achieved)

To declare input IN1, with True as the initial condition, fixed percentage activity on a periodic cycle set to 10%, and effective for the entire simulation length add the following line in the specification file:

Input:IN1:True:F:F:1:10:20

  • Noise
[Needs content]
  • Mutation
[Needs content]
  • Delay Nodes
[Needs content]
  • Sustain Nodes
[Needs content]
  • Output Nodes
[Needs content]

Simulation Modes

The most recent version of ChemChains can be ran in three modes, one of which is a network construction mode (or File Conversion) and the remaining two are simulation modes.

File Conversion Mode

As mentioned above, to run ChemChains, a file with the network description is required. This file can be created manually as described in the previous section, or automatically from a provided set of truth tables for individual nodes.

These truth tables need to be in the form of a tab-delimited text file. Each table must be in a separate file which should be named the same as the name of the node of interest.

Thus, for the toy network (Figure 1) with truth tables as shown in Figure 2, create a new directory called "sampleNet" in "inFiles/exts/FileConverter", and three text files (A.csv, B.csv, and C.csv) with the truth tables in tab-delimited format and save them in the "inFiles/exts/FileConverter/sampleNet" directory.

In addition, we need to create another file with the list of nodes comprising our network. In this file, each node has two properties, nodeID and initial value, associated with it. Each node and its properties need to be on a new line. The mentioned node properties need to be tab-separated.

The syntax is as follows:

NodeName NodeID InitialValue

Sample node list for our network will look like:

A 1 0
B 2 0
C 3 0
IN1 IN101 1
Note that if the initial value is False (i.e., 0 ) we can leave the third column empty.

Save the file as sampleNodelist.txtc.

To create the Network Descriptor file from existing truth tables, run ChemChains with the following parameters:

./ChemChains -TT2ND -iNodeList inFiles/exts/FileConverter/sampleNodeList.txt -iTables inFiles/exts/FileConverter/sampleNet

Visual Mode

[Needs content]

Calculation Mode

[Needs content] [Needs more content...]

Advanced How-to

[Needs content]

July 18, 2008, at 09:18 PM by 68.229.177.191 -
Added line 98:
  • Noise
Deleted lines 99-100:
  • Noise
[Needs content]
July 18, 2008, at 09:16 PM by 68.229.177.191 -
Changed lines 84-85 from:
Input:name:initial/default value:random(R)/fixed(F):noise(N)/fixed/(F):time to be introduced:dose (in percentage):duration of the dosage
to:
Input:name:initial/default value:random(R)/fixed(F):noise(N)/fixed/(F):time to be introduced:dose (in percentage):duration of the dosage (explanation of each option below)

  • Name -self-explanatory
  • Initial/Default value - self-explanatory
  • Random(R)/Fixed(F) - this parameter specifies whether the percentage ON should be as specified by the user or generated randomly
  • Noise(N)/Fixed(F) - specifies whether the input will be set on a periodic cycle or randomly bounce around within a given range (see Noise below)
  • Time to be introduced - time when a given percentage ON will come into an effect
  • Dosage - specified percent ON for a given input (integer from 0 to 100)
  • Duration of the dosage - the number of iterations the dosage amount will be exerted on the input (note that if the duration is shorter than the total runtime, the input will be set to 0% ON once the duration period is achieved)
Changed lines 96-97 from:
Input:name:True:F:F:1:10:20
to:
Input:IN1:True:F:F:1:10:20
July 18, 2008, at 08:12 PM by 68.229.177.191 -
Changed lines 82-83 from:

Syntax to declare an input (note that each input needs to be declared on a new line)

to:

Syntax to declare an input (note that each input needs to be declared on a new line:

Added lines 85-89:

To declare input IN1, with True as the initial condition, fixed percentage activity on a periodic cycle set to 10%, and effective for the entire simulation length add the following line in the specification file:

Input:name:True:F:F:1:10:20
July 18, 2008, at 08:06 PM by 68.229.177.191 -
Changed lines 73-83 from:
  • Runtime
to:
  • Runtime - specifies the overall length of each simulation, as well as the number of iterations (transient time) before any analysis is conducted.

Syntax: RunTime:TransientTime:TotalTime

For our example, we'll set the total time to 20 iterations and transient time to 10 as follows:

RunTime:10:20

  • Inputs - external inputs (IN1 in the above toy network)

Syntax to declare an input (note that each input needs to be declared on a new line)

Input:name:initial/default value:random(R)/fixed(F):noise(N)/fixed/(F):time to be introduced:dose (in percentage):duration of the dosage
Deleted lines 84-85:
  • Inputs
[Needs content]
July 17, 2008, at 05:07 PM by 70.167.145.201 -
Added lines 90-91:

The most recent version of ChemChains can be ran in three modes, one of which is a network construction mode (or File Conversion) and the remaining two are simulation modes.

Added lines 117-121:

Visual Mode

[Needs content]

Calculation Mode

[Needs content]

July 17, 2008, at 04:47 PM by 70.167.145.201 -
Changed line 90 from:

File Conversion

to:

File Conversion Mode

Changed lines 95-96 from:

Thus, for the toy network (Figure 1) with truth tables as shown in Figure 2, create three text files (A.csv, B.csv, and C.csv) with the truth tables in tab-delimited format.

to:

Thus, for the toy network (Figure 1) with truth tables as shown in Figure 2, create a new directory called "sampleNet" in "inFiles/exts/FileConverter", and three text files (A.csv, B.csv, and C.csv) with the truth tables in tab-delimited format and save them in the "inFiles/exts/FileConverter/sampleNet" directory.

Changed lines 109-110 from:
to:

Save the file as sampleNodelist.txtc.

To create the Network Descriptor file from existing truth tables, run ChemChains with the following parameters:

./ChemChains -TT2ND -iNodeList inFiles/exts/FileConverter/sampleNodeList.txt -iTables inFiles/exts/FileConverter/sampleNet
July 17, 2008, at 04:37 PM by 70.167.145.201 -
Added lines 100-102:

The syntax is as follows:

NodeName NodeID InitialValue
Changed lines 108-110 from:
to:
Note that if the initial value is False (i.e., 0 ) we can leave the third column empty.

July 17, 2008, at 04:34 PM by 70.167.145.201 -
Added lines 97-105:

In addition, we need to create another file with the list of nodes comprising our network. In this file, each node has two properties, nodeID and initial value, associated with it. Each node and its properties need to be on a new line. The mentioned node properties need to be tab-separated.

Sample node list for our network will look like:

A 1 0
B 2 0
C 3 0
IN1 IN101 1
July 17, 2008, at 04:28 PM by 70.167.145.201 -
Changed lines 90-92 from:
  • File Conversion
As mentioned above, to run ChemChains, a file with the network description is required. This file can be created manually as described in the previous section, or automatically from a provided set of truth tables for individual nodes.
to:

File Conversion

As mentioned above, to run ChemChains, a file with the network description is required. This file can be created manually as described in the previous section, or automatically from a provided set of truth tables for individual nodes.

July 17, 2008, at 04:27 PM by 70.167.145.201 -
Added lines 90-96:
  • File Conversion
As mentioned above, to run ChemChains, a file with the network description is required. This file can be created manually as described in the previous section, or automatically from a provided set of truth tables for individual nodes.

These truth tables need to be in the form of a tab-delimited text file. Each table must be in a separate file which should be named the same as the name of the node of interest.

Thus, for the toy network (Figure 1) with truth tables as shown in Figure 2, create three text files (A.csv, B.csv, and C.csv) with the truth tables in tab-delimited format.

July 17, 2008, at 04:16 PM by 70.167.145.201 -
Changed lines 17-18 from:

To run ChemChains in Windows, a Linux-like environment is necessary. For example, you can download and install the freely available cygwin from here.

to:

To run ChemChains in Windows, a Linux-like environment is necessary. For example, you can download and install the freely available cygwin from here.

July 16, 2008, at 10:27 PM by 68.229.177.191 -
Changed line 75 from:
to:
[Needs content]
Added line 77:
[Needs content]
Added line 79:
[Needs content]
Added line 81:
[Needs content]
Added line 83:
[Needs content]
Changed lines 85-86 from:
to:
[Needs content]
July 16, 2008, at 10:27 PM by 68.229.177.191 -
Changed line 73 from:

[Needs content]

to:
[Needs content]
July 16, 2008, at 10:27 PM by 68.229.177.191 -
Added line 73:

[Needs content]

Added line 75:
July 16, 2008, at 10:26 PM by 68.229.177.191 -
Changed lines 65-69 from:

Once finished we can save the file as myNetwork.txt.


to:

Once finished we can save the file as myNetwork.txtand move on to the simulation specification file.

Changed lines 68-79 from:
to:

ChemChains is a feature-rich logic network simulation software, which offers users many advanced simulation options. These options are specified by users in the specification file, the second of the required input files, that is loaded into the program before each simulation experiment.

The following describes the various options contained within this file:

  • Runtime
  • Inputs
  • Noise
  • Mutation
  • Delay Nodes
  • Sustain Nodes
  • Output Nodes
July 16, 2008, at 10:03 PM by 68.229.177.191 -
Changed lines 58-59 from:

Thus, our toy network would look like:

to:

Thus, the network descriptor for our toy network can look like:

Changed lines 64-66 from:

to:

Note that the declaration of each node is on a new line. Once finished we can save the file as myNetwork.txt.

July 16, 2008, at 10:01 PM by 68.229.177.191 -
Changed lines 58-66 from:
to:

Thus, our toy network would look like:

Bool:A:False:C:T
Bool:B:False:A,C:FF,FT,TT
Bool:C:False:B:T

July 16, 2008, at 09:57 PM by 68.229.177.191 -
Changed lines 54-58 from:
to:

Once we have the network and truth tables established, we can create our network descriptor file using these tables. To create the file, the following syntax needs to be used:

Bool:name:initial state[True|False]:input1,input2..inputN:list of states of input nodes for non-initial state(separated by comma)

July 16, 2008, at 05:07 PM by 137.48.16.86 -
Changed lines 42-43 from:
Sample toy network
Figure 1.
to:
Sample toy network
Figure 1: Sample network.
Changed lines 50-51 from:
Node Truth Tables
Figure 2.
to:
Node Truth Tables
Figure 2: Truth tables for nodes A, B, and C.
July 16, 2008, at 05:04 PM by 137.48.16.86 -
Changed line 47 from:
  • Node B: Node B is inhibited by node A and activated by node C. In addition, node C is a required positive regulator.
to:
  • Node B: Node B is inhibited by node A and activated by node C. In addition, node C is a required positive regulator. The negative regulation is dominant over the positive one.
July 16, 2008, at 04:55 PM by 137.48.16.86 -
Changed line 47 from:
  • Node B: Node B is inhibited by node A
to:
  • Node B: Node B is inhibited by node A and activated by node C. In addition, node C is a required positive regulator.
July 16, 2008, at 04:54 PM by 137.48.16.86 -
Changed lines 52-54 from:

These activation mechanisms can be expressed as a truth tables (Figure 2).

to:

These activation mechanisms can be expressed as individual truth tables (Figure 2).

July 16, 2008, at 04:53 PM by 137.48.16.86 -
Changed lines 50-51 from:
to:
Node Truth Tables
Figure 2.
July 16, 2008, at 04:53 PM by 137.48.16.86 -
Changed lines 50-51 from:
to:
July 16, 2008, at 04:53 PM by 137.48.16.86 -
Changed lines 50-52 from:

This mechanism can be expressed as a truth table.

to:

Attach:toynetwork_TT.jpeg Δ | Figure 2.

These activation mechanisms can be expressed as a truth tables (Figure 2).

July 16, 2008, at 03:43 PM by 137.48.16.86 -
Added line 45:
July 16, 2008, at 03:43 PM by 137.48.16.86 -
Changed line 44 from:

As an example, let's assume a toy network (Figure 1) consisting of nodes A, B, and C, where green line (with an arrow) denotes positive regulation (i.e., activation) and red line (with a stop line) denotes negative regulation. Because this is a boolean network, each node has a an activation mechanism associated with it. The activation mechanisms for the nodes of this network are as follows:

to:

As an example, let's assume a toy network (Figure 1) consisting of nodes A, B, and C, where green line (with an arrow) denotes positive regulation (i.e., activation) and red line (with a stop line) denotes negative regulation. Because this is a boolean network, each node has a an activation mechanism associated with it. Let's assume the activation mechanisms for the nodes of this network as follows:

July 16, 2008, at 03:42 PM by 137.48.16.86 -
Added lines 42-43:
Sample toy network
Figure 1.
Changed line 51 from:
Sample toy network
Figure 1.
to:
July 16, 2008, at 03:41 PM by 137.48.16.86 -
Changed lines 42-43 from:

As an example, let's assume the following toy network consisting of nodes A, B, and C.

to:

As an example, let's assume a toy network (Figure 1) consisting of nodes A, B, and C, where green line (with an arrow) denotes positive regulation (i.e., activation) and red line (with a stop line) denotes negative regulation. Because this is a boolean network, each node has a an activation mechanism associated with it. The activation mechanisms for the nodes of this network are as follows:

  • Node A: Node A is activated by node C
  • Node B: Node B is inhibited by node A
  • Node C: Node C is activated by node B

This mechanism can be expressed as a truth table.

July 16, 2008, at 03:35 PM by 137.48.16.86 -
Changed lines 44-45 from:
Sample toy network
Figure 1.
to:
Sample toy network
Figure 1.


July 16, 2008, at 03:34 PM by 137.48.16.86 -
Changed lines 44-45 from:
Sample toy network
Figure 1.
to:
Sample toy network
Figure 1.
July 16, 2008, at 03:33 PM by 137.48.16.86 -
Changed lines 44-45 from:
Sample toy network
Figure 1.
to:
Sample toy network
Figure 1.
July 16, 2008, at 03:33 PM by 137.48.16.86 -
Changed lines 44-46 from:

%lfloat text-align=center margin-top=5px margin-right=25px margin-bottom=5px margin-left=25px% Sample toy network|Figure 1.

to:
Sample toy network
Figure 1.
July 16, 2008, at 03:32 PM by 137.48.16.86 -
Changed lines 44-45 from:
Sample toy network
to:

%lfloat text-align=center margin-top=5px margin-right=25px margin-bottom=5px margin-left=25px% Sample toy network|Figure 1.

July 16, 2008, at 03:26 PM by 137.48.16.86 -
Changed lines 44-46 from:

toynet.jpeg"Sample toy network"

to:
Sample toy network
July 16, 2008, at 03:23 PM by 137.48.16.86 -
Changed line 44 from:
to:
July 16, 2008, at 02:58 PM by 137.48.16.86 -
Changed line 44 from:
Sample toy network
to:
July 16, 2008, at 02:58 PM by 137.48.16.86 -
Changed lines 44-46 from:
to:
Sample toy network

toynet.jpeg"Sample toy network"

July 16, 2008, at 02:26 PM by 137.48.16.86 -
Changed lines 44-46 from:
Sample toy network

to:
July 16, 2008, at 02:26 PM by 137.48.16.86 -
Changed lines 44-46 from:
Sample toy network

to:
Sample toy network

July 16, 2008, at 02:25 PM by 137.48.16.86 -
Changed lines 44-46 from:
Sample toy network

to:
Sample toy network

July 16, 2008, at 02:08 PM by 137.48.16.86 -
Changed lines 45-48 from:

http://example.com| http://pmichaud.com/img/misc/pc.jpg | [- [[ (Wikipedia:Paper_clips | Paper clips ]] are fun to work with. -]

to:
July 16, 2008, at 02:07 PM by 137.48.16.86 -
Changed line 45 from:
to:

http://example.com|

Added line 48:
July 16, 2008, at 02:04 PM by 137.48.16.86 -
Changed lines 46-47 from:
to:

http://pmichaud.com/img/misc/pc.jpg | [- [[ (Wikipedia:Paper_clips | Paper clips ]] are fun to work with. -]

July 16, 2008, at 02:03 PM by 137.48.16.86 -
Changed lines 45-46 from:

[[http://example.com|Attach:toynet1.jpg]]

to:
July 16, 2008, at 02:03 PM by 137.48.16.86 -
Changed lines 45-46 from:
to:

[[http://example.com|Attach:toynet1.jpg]]

July 16, 2008, at 02:00 PM by 137.48.16.86 -
Changed lines 44-45 from:

Attach:Main.Tutorial/toynet1.jpg

to:
Sample toy network
July 16, 2008, at 01:57 PM by 137.48.16.86 -
Changed lines 44-45 from:

Attach:Main/toynet1.jpg

to:

Attach:Main.Tutorial/toynet1.jpg

July 16, 2008, at 01:56 PM by 137.48.16.86 -
Changed lines 44-45 from:
to:

Attach:Main/toynet1.jpg

July 16, 2008, at 01:56 PM by 137.48.16.86 -
Changed lines 44-45 from:

Attach:toynet1.jpg

to:
July 16, 2008, at 01:55 PM by 137.48.16.86 -
Changed lines 44-45 from:
to:

Attach:toynet1.jpg

July 16, 2008, at 01:45 PM by 137.48.16.86 -
Changed lines 44-45 from:
to:
July 16, 2008, at 01:44 PM by 137.48.16.86 -
Changed lines 44-45 from:
to:
July 16, 2008, at 01:43 PM by 137.48.16.86 -
Added line 45:
July 16, 2008, at 01:35 PM by 137.48.16.86 -
Changed line 44 from:
to:
July 16, 2008, at 01:05 PM by 137.48.16.86 -
Changed lines 40-42 from:

Network descriptor is a syntax-specific text file that stores the network and logic for each node.

to:

Network descriptor is a syntax-specific text file that stores the network, and logic for each node.

As an example, let's assume the following toy network consisting of nodes A, B, and C.

July 16, 2008, at 01:03 PM by 137.48.16.86 -
Changed lines 40-42 from:
to:

Network descriptor is a syntax-specific text file that stores the network and logic for each node.

July 16, 2008, at 12:59 PM by 137.48.16.86 -
Changed lines 39-42 from:

Network Descriptor

Simulation Specification file

to:

Network Descriptor

Simulation Specification file

July 16, 2008, at 12:58 PM by 137.48.16.86 -
Changed line 14 from:
  1. !!Requirements
to:

Requirements

July 16, 2008, at 12:58 PM by 137.48.16.86 -
Changed line 14 from:

Requirements

to:
  1. !!Requirements
July 16, 2008, at 12:58 PM by 137.48.16.86 -
Changed line 29 from:

Introduction

to:

Introduction

Changed line 36 from:

Input Files

to:

Input Files

Changed lines 43-44 from:

Simulation Modes

to:

Simulation Modes

July 16, 2008, at 12:57 PM by 137.48.16.86 -
Changed lines 37-42 from:
to:

To simulate logical networks with ChemChains, two input files are required: the network descriptor and a simulation specification file.

Network Descriptor

Simulation Specification file

July 16, 2008, at 12:34 AM by 68.229.177.191 -
Added lines 38-39:

Simulation Modes

July 16, 2008, at 12:28 AM by 68.229.177.191 -
Changed line 1 from:

table border=1 width=30% align=left bgcolor=#cccc99 cellspacing=0

to:

(:table border=1 width=40% align=left bgcolor=#cccc99 cellspacing=0 :)

July 16, 2008, at 12:28 AM by 68.229.177.191 -
Added line 10:
July 16, 2008, at 12:27 AM by 68.229.177.191 -
Added lines 8-9:
Changed lines 35-36 from:

Input Files

to:

Input Files

July 16, 2008, at 12:26 AM by 68.229.177.191 -
Added line 26:

Introduction

July 16, 2008, at 12:25 AM by 68.229.177.191 -
Changed lines 32-33 from:
to:

Input Files

July 16, 2008, at 12:24 AM by 68.229.177.191 -
Changed lines 28-29 from:

To run ChemChains, users must provide several input files. Once simulations and/or analysis are initiated, ChemChains will create several types of output file formats. Both the input files, as well as the desired output format and the output files must be specified by users in the form of command-line parameters provided to ChemChains at the time of program initiation. To see all available options and command-line parameters run ChemChains with the -h flag.\\

to:

To run ChemChains, users must provide several input files. Once simulations and/or analysis are initiated, ChemChains will create several types of output file formats. Both the input files, as well as the desired output format and the output files must be specified by users in the form of command-line parameters provided to ChemChains at the time of program initiation. To see all available options and command-line parameters run ChemChains with the -h flag.

July 16, 2008, at 12:24 AM by 68.229.177.191 -
Changed line 28 from:

To run ChemChains, users must provide several input files. Once simulations and/or analysis are initiated, ChemChains will create several types of output file formats. Both the input files, as well as the desired output format and the output files must be specified by users in the form of command-line parameters provided to ChemChains at the time of program initiation. To see all available options and command-line parameters run ChemChains with the -h flag.

to:

To run ChemChains, users must provide several input files. Once simulations and/or analysis are initiated, ChemChains will create several types of output file formats. Both the input files, as well as the desired output format and the output files must be specified by users in the form of command-line parameters provided to ChemChains at the time of program initiation. To see all available options and command-line parameters run ChemChains with the -h flag.\\

July 16, 2008, at 12:24 AM by 68.229.177.191 -
Changed lines 28-32 from:

To run ChemChains, users must provide several input files. Once simulations and/or analysis are initiated, ChemChains will create several types of output file formats. Both the input files, as well as the desired output format and the output files must be specified by users in the form of command-line parameters provided to ChemChains at the time of program initiation. To see all available options and command-line parameters run ChemChains with the -h flag. ./ChemChains -h

to:

To run ChemChains, users must provide several input files. Once simulations and/or analysis are initiated, ChemChains will create several types of output file formats. Both the input files, as well as the desired output format and the output files must be specified by users in the form of command-line parameters provided to ChemChains at the time of program initiation. To see all available options and command-line parameters run ChemChains with the -h flag.

./ChemChains -h

July 16, 2008, at 12:23 AM by 68.229.177.191 -
Changed lines 29-34 from:

markup ./ChemChains -h markupend

to:

./ChemChains -h

July 16, 2008, at 12:22 AM by 68.229.177.191 -
Changed line 30 from:
./ChemChains -h
to:

./ChemChains -h

July 16, 2008, at 12:22 AM by 68.229.177.191 -
Changed lines 28-31 from:

To run ChemChains, users must provide several input files. Once simulations and/or analysis are initiated, ChemChains will create several types of output file formats. Both the input files, as well as the desired output format and the output files must be specified by users in the form of command-line parameters provided to ChemChains at the time of program initiation.

to:

To run ChemChains, users must provide several input files. Once simulations and/or analysis are initiated, ChemChains will create several types of output file formats. Both the input files, as well as the desired output format and the output files must be specified by users in the form of command-line parameters provided to ChemChains at the time of program initiation. To see all available options and command-line parameters run ChemChains with the -h flag. (:markup:)

./ChemChains -h

(:markupend:)

July 16, 2008, at 12:16 AM by 68.229.177.191 -
Changed lines 28-31 from:

To run ChemChains, users must provide several input files. Once simulations and/or analysis are initiated, ChemChains will create several types of output file formats. Both the input files, as well as the desired output format and the output files must be specified by users in the form of command-line parameters provided to ChemChains at the time of program initiation.

to:

To run ChemChains, users must provide several input files. Once simulations and/or analysis are initiated, ChemChains will create several types of output file formats. Both the input files, as well as the desired output format and the output files must be specified by users in the form of command-line parameters provided to ChemChains at the time of program initiation.

July 16, 2008, at 12:16 AM by 68.229.177.191 -
Changed lines 28-31 from:

To run ChemChains, users must provide several input files (described below). Once simulations and/or analysis are initiated, ChemChains will create several types of output file formats. Both the input files, as well as the desired output format and the output files must be specified by users in the form of command-line parameters provided to ChemChains at the time of program initiation.

to:

To run ChemChains, users must provide several input files. Once simulations and/or analysis are initiated, ChemChains will create several types of output file formats. Both the input files, as well as the desired output format and the output files must be specified by users in the form of command-line parameters provided to ChemChains at the time of program initiation.

July 16, 2008, at 12:15 AM by 68.229.177.191 -
Changed line 26 from:

This section will provide you with the most basic ways of simulating your first network model using ChemChains.\\

to:

This section will provide you with the most basic ways of simulating your first network model using ChemChains.\\

July 16, 2008, at 12:14 AM by 68.229.177.191 -
Changed line 12 from:

ChemChains is a platform independent command-line software written in C++, that has been tested on Linux and Windows platforms. \\

to:

ChemChains is a platform independent command-line software written in C++, that has been tested on Linux and Windows platforms.\\

July 16, 2008, at 12:14 AM by 68.229.177.191 -
Changed lines 26-27 from:

This section will provide you with the most basic ways of simulating your first network model using ChemChains.\\

to:

This section will provide you with the most basic ways of simulating your first network model using ChemChains.\\ \\

July 16, 2008, at 12:14 AM by 68.229.177.191 -
Changed line 12 from:

ChemChains is a platform independent software written in C++, that has been tested on Linux and Windows platforms. \\

to:

ChemChains is a platform independent command-line software written in C++, that has been tested on Linux and Windows platforms. \\

Changed lines 26-32 from:

[Needs content]

to:

This section will provide you with the most basic ways of simulating your first network model using ChemChains.\\
To run ChemChains, users must provide several input files (described below). Once simulations and/or analysis are initiated, ChemChains will create several types of output file formats. Both the input files, as well as the desired output format and the output files must be specified by users in the form of command-line parameters provided to ChemChains at the time of program initiation.

[Needs more content...]

July 16, 2008, at 12:08 AM by 68.229.177.191 -
Changed line 12 from:

ChemChains is a platform independent software that has been tested on Linux and Windows platforms. \\

to:

ChemChains is a platform independent software written in C++, that has been tested on Linux and Windows platforms. \\

July 16, 2008, at 12:04 AM by 68.229.177.191 -
Deleted line 24:
Changed lines 27-28 from:

Advanced How-to

to:

Advanced How-to

[Needs content]

July 16, 2008, at 12:04 AM by 68.229.177.191 -
Changed line 27 from:
to:

[Needs content]

July 16, 2008, at 12:03 AM by 68.229.177.191 -
Changed lines 17-25 from:
to:

Linux

  1. Open a new terminal window
  2. Type: make (This should create an executable file called ChemChains)

Windows

  1. Start Cygwin
  2. In the Cygwin terminal window, type: make (This should create an executable file called ChemChains)

July 15, 2008, at 11:58 PM by 68.229.177.191 -
Changed line 13 from:
to:

\\

July 15, 2008, at 11:58 PM by 68.229.177.191 -
Changed lines 14-15 from:

To run ChemChains in Windows, download cygwin

to:

To run ChemChains in Windows, a Linux-like environment is necessary. For example, you can download and install the freely available cygwin from here.

July 15, 2008, at 11:56 PM by 68.229.177.191 -
Changed lines 12-21 from:

alkhdflakshdf
asdfasdf
asdfasdf
asdfasdf
asdfasdf
asdfasdf
asdfasdf
asdfasdfa
asdfadgafrger

to:

ChemChains is a platform independent software that has been tested on Linux and Windows platforms.
To run ChemChains in Windows, download cygwin

July 15, 2008, at 11:23 PM by 68.229.177.191 -
Added line 21:
July 15, 2008, at 11:23 PM by 68.229.177.191 -
Changed lines 12-20 from:
to:

alkhdflakshdf
asdfasdf
asdfasdf
asdfasdf
asdfasdf
asdfasdf
asdfasdf
asdfasdfa
asdfadgafrger\\

July 15, 2008, at 11:22 PM by 68.229.177.191 -
Changed lines 6-8 from:
to:
Added lines 12-17:

Installation

Basic How-to

Advanced How-to

July 15, 2008, at 11:21 PM by 68.229.177.191 -
Changed lines 9-10 from:

tableend

to:

(:tableend:)

July 15, 2008, at 11:21 PM by 68.229.177.191 -
Changed lines 9-10 from:

tableend//

to:

(:tableend:)

July 15, 2008, at 11:21 PM by 68.229.177.191 -
Changed lines 9-10 from:

tableend

to:

(:tableend:)//

July 15, 2008, at 11:19 PM by 68.229.177.191 -
Changed line 11 from:

Requirements

to:

Requirements

July 15, 2008, at 11:18 PM by 68.229.177.191 -
Changed line 11 from:

to:

Requirements

July 15, 2008, at 11:15 PM by 68.229.177.191 -
Changed line 5 from:
to:
Added line 11:

July 15, 2008, at 11:13 PM by 68.229.177.191 -
Changed lines 6-8 from:
to:
July 15, 2008, at 11:12 PM by 68.229.177.191 -
Changed line 1 from:

table border=1 width=30% align=right bgcolor=#cccc99 cellspacing=0

to:

(:table border=1 width=30% align=left bgcolor=#cccc99 cellspacing=0 :)

Changed line 5 from:
to:
July 15, 2008, at 11:09 PM by 68.229.177.191 -
Changed line 5 from:
to:
July 15, 2008, at 11:09 PM by 68.229.177.191 -
Changed line 5 from:
to:
July 15, 2008, at 11:08 PM by 68.229.177.191 -
Changed lines 5-6 from:
to:
Deleted lines 10-14:
  • Requirements
  • Installation
  • Basic How-to
  • Advanced How-to
July 15, 2008, at 11:07 PM by 68.229.177.191 -
Added lines 1-8:

(:table border=1 width=30% align=right bgcolor=#cccc99 cellspacing=0 :) (:cellnr:) Navigation Links (:cellnr:)

(:tableend:)

July 15, 2008, at 11:04 PM by 68.229.177.191 -
Changed lines 4-5 from:
  • Advanced How-to
to:
  • Advanced How-to
July 15, 2008, at 11:02 PM by 68.229.177.191 -
Changed lines 1-4 from:

to be written...

to:
  • Requirements
  • Installation
  • Basic How-to
  • Advanced How-to
July 15, 2008, at 11:00 PM by 68.229.177.191 -
Added line 1:

to be written...