Randisi at 11:37, 1 February 2018

2018-02-01T11:37:58Z

← Older revision		Revision as of 11:37, 1 February 2018
Line 12:		Line 12:

	# <tt>src/Interactions/InteractionFactory.cpp</tt> Now your file will be compiled, but it's still disjoint from the rest of the program. In order to make sure that the oxDNA program can use your interaction, you must modify the <tt>InteractionFactory.cpp</tt> file to use your interaction.		# <tt>src/Interactions/InteractionFactory.cpp</tt> Now your file will be compiled, but it's still disjoint from the rest of the program. In order to make sure that the oxDNA program can use your interaction, you must modify the <tt>InteractionFactory.cpp</tt> file to use your interaction.
	## Add the header file <tt>#include "~~JordanInteraction~~.h"</tt> together with the other interaction header files, at the beginning of the file.		## Add the header file <tt>#include "MyInteraction.h"</tt> together with the other interaction header files, at the beginning of the file.
	## In the function <tt>make_interaction</tt> there's a long list of statements that create a different type of interaction depending on the value of the <tt>interaction_type</tt> string in the oxDNA input file. Add your own interaction there, making sure not to mask any previously defined interactions. The syntax of the code of block might change, but currently it's just a bunch of lines like <br> <br> <tt>else if(inter_type.compare("DNA_nomesh") == 0) return new DNAInteraction_nomesh<number>();<br> else if(inter_type.compare("DNA2_nomesh") == 0) return new DNA2Interaction_nomesh<number>();<br> else if(inter_type.compare("LJ") == 0) return new LJInteraction<number>();<br> else if(inter_type.compare("DNA_relax") == 0) return new DNAInteraction_relax<number>();<br> else if(inter_type.compare("RNA") == 0) return new RNAInteraction<number>();</tt><br><br> so you would just add the line <br><br> <tt>else if(inter_type.compare("my_interaction") == 0) return new MyInteraction<number>();</tt><br><br> somewhere over there.		## In the function <tt>make_interaction</tt> there's a long list of statements that create a different type of interaction depending on the value of the <tt>interaction_type</tt> string in the oxDNA input file. Add your own interaction there, making sure not to mask any previously defined interactions. The syntax of the code of block might change, but currently it's just a bunch of lines like <br> <br> <tt>else if(inter_type.compare("DNA_nomesh") == 0) return new DNAInteraction_nomesh<number>();<br> else if(inter_type.compare("DNA2_nomesh") == 0) return new DNA2Interaction_nomesh<number>();<br> else if(inter_type.compare("LJ") == 0) return new LJInteraction<number>();<br> else if(inter_type.compare("DNA_relax") == 0) return new DNAInteraction_relax<number>();<br> else if(inter_type.compare("RNA") == 0) return new RNAInteraction<number>();</tt><br><br> so you would just add the line <br><br> <tt>else if(inter_type.compare("my_interaction") == 0) return new MyInteraction<number>();</tt><br><br> somewhere over there.

Randisi: Creating the guideline

2018-01-17T14:40:01Z

Creating the guideline

New page

The oxDNA program is written in such a way to be easily modifiable to perform research in previously unplanned research directions. One of the most common ways of doing so is to write a new interaction, to simulate a different DNA/RNA model or to simulate something else entirely, including patchy particles.

This section (currently a stub) is going to explain briefly what is needed to write such an interaction.

== Files to create ==
# '''Interaction Header''' - this is the header file of your interaction. Contains the C++ header of the interaction, and should be saved in the directory <tt>src/Interactions</tt> with extension <tt>.h</tt>. The faster way to write it is probably to copy the one of an existing interaction that is somewhat similar to the interaction you want to write and modify it until you're happy with it. The name of the file should be as close as the one of the class defining the interaction, with the extension <tt>.h</tt> common to all header files. Therefore, if your interaction defines the class <tt>MyInteraction</tt>, the file could be called <tt>MyInteraction.h</tt>.
# '''Interaction Source''' - this is the source file of your interaction. Like the header, it should be saved in the <tt>src/Interactions</tt> directory, but it should have extension <tt>.cpp</tt>. Again, the best way to write one is to look at the <tt>.cpp</tt> file of an interaction similar to the one you are going to write and modify it as needed. The name should be the same as the header file, with the only difference that the extension should be <tt>.cpp</tt> instead of <tt>.h</tt>.

== Files to modify ==
Here and in the following we are assuming that your interaction defines a class <tt>MyInteraction</tt>, and is saved in the files <tt>MyInteraction.h</tt> and <tt>MyInteraction.cpp</tt>. Your interaction will of course have a more informative name, so make sure to modify the following files accordingly.
# <tt>src/CMakeLists.txt</tt> - this files contains information on how to compile oxDNA, i.e. which files to use to produce the oxDNA executable and how to do it. The files containing the interactions are listed in the block that starts with <tt> SET(interactions_SOURCES </tt>. Add a line containing <tt>MyInteraction.cpp</tt> to the list, so that the source file will be included in the build. The header file will be included by the source file (provided it contains the appropriate <tt>#include</tt> directive).

# <tt>src/Interactions/InteractionFactory.cpp</tt> Now your file will be compiled, but it's still disjoint from the rest of the program. In order to make sure that the oxDNA program can use your interaction, you must modify the <tt>InteractionFactory.cpp</tt> file to use your interaction.
## Add the header file <tt>#include "JordanInteraction.h"</tt> together with the other interaction header files, at the beginning of the file.
## In the function <tt>make_interaction</tt> there's a long list of statements that create a different type of interaction depending on the value of the <tt>interaction_type</tt> string in the oxDNA input file. Add your own interaction there, making sure not to mask any previously defined interactions. The syntax of the code of block might change, but currently it's just a bunch of lines like <tt>else if(inter_type.compare("DNA_nomesh") == 0) return new DNAInteraction_nomesh<number>(); else if(inter_type.compare("DNA2_nomesh") == 0) return new DNA2Interaction_nomesh<number>(); else if(inter_type.compare("LJ") == 0) return new LJInteraction<number>(); else if(inter_type.compare("DNA_relax") == 0) return new DNAInteraction_relax<number>(); else if(inter_type.compare("RNA") == 0) return new RNAInteraction<number>();</tt> so you would just add the line <tt>else if(inter_type.compare("my_interaction") == 0) return new MyInteraction<number>();</tt> somewhere over there.

How To Write An Interaction - Revision history

Randisi at 11:37, 1 February 2018

Randisi: Creating the guideline