MotiveValidator:Terminology - Revision history

Lukas: /* Validation terminology */

2014-07-30T21:41:01Z

Validation terminology

← Older revision		Revision as of 21:41, 30 July 2014
Line 21:		Line 21:

	=Validation terminology=		=Validation terminology=
	* '''Model residue:''' Or simply ''model''is a particular structure that is known to be correct. This structure is then used as reference template in the validation process, whereby a query residue with the same name (3-letter code) as the model will be compared to the model. Within the ''MotiveValidator'' environment, a model contains one residue. The origin of the ''model'' can be the wwPDB chemical component dictionary accessible via LigandExpo<ref name ="ligandexpo"/>, or a custom model provided by the user.		* '''Model residue:''' Or simply ''model'' is a particular structure that is known to be correct. This structure is then used as reference template in the validation process, whereby a query residue with the same name (3-letter code) as the model will be compared to the model. Within the ''MotiveValidator'' environment, a model contains one residue. The origin of the ''model'' can be the wwPDB chemical component dictionary accessible via LigandExpo<ref name ="ligandexpo"/>, or a custom model provided by the user.
	* '''Residue to be validated (validated residue):''' Residue of interest for validation.		* '''Residue to be validated (validated residue):''' Residue of interest for validation.
	* '''Input motif:''' Residues to be validated together with their immediate surroundings (i.e. atoms within one or two bonds of any atom of the residue to be validated).		* '''Input motif:''' Residues to be validated together with their immediate surroundings (i.e. atoms within one or two bonds of any atom of the residue to be validated).

Lukas: /* Validation terminology */

2014-07-28T21:03:45Z

Validation terminology

← Older revision		Revision as of 21:03, 28 July 2014
Line 22:		Line 22:
	=Validation terminology=		=Validation terminology=
	* '''Model residue:''' Or simply ''model''is a particular structure that is known to be correct. This structure is then used as reference template in the validation process, whereby a query residue with the same name (3-letter code) as the model will be compared to the model. Within the ''MotiveValidator'' environment, a model contains one residue. The origin of the ''model'' can be the wwPDB chemical component dictionary accessible via LigandExpo<ref name ="ligandexpo"/>, or a custom model provided by the user.		* '''Model residue:''' Or simply ''model''is a particular structure that is known to be correct. This structure is then used as reference template in the validation process, whereby a query residue with the same name (3-letter code) as the model will be compared to the model. Within the ''MotiveValidator'' environment, a model contains one residue. The origin of the ''model'' can be the wwPDB chemical component dictionary accessible via LigandExpo<ref name ="ligandexpo"/>, or a custom model provided by the user.
	* '''Residue to be validated:''' Residue of interest for validation.		* '''Residue to be validated (validated residue):''' Residue of interest for validation.
	* '''Input motif:''' Residues to be validated together with their immediate surroundings (i.e. atoms within one or two bonds of any atom of the residue to be validated).		* '''Input motif:''' Residues to be validated together with their immediate surroundings (i.e. atoms within one or two bonds of any atom of the residue to be validated).
	* '''Validated motif:''' The subset of atoms from the input motif paired with atoms in the model residue.		* '''Validated motif:''' The subset of atoms from the input motif paired with atoms in the model residue.


	=References=		=References=

Lukas: /* Motif / Fragment */

2014-07-10T13:13:09Z

Motif / Fragment

← Older revision		Revision as of 13:13, 10 July 2014
Line 16:		Line 16:
	refers to a fragment made up from the residue under study, together with its surroundings (i.e., atoms from neighboring residues). Note that the terms ''fragment'' and ''motif'' are used as synonyms in this manual.		refers to a fragment made up from the residue under study, together with its surroundings (i.e., atoms from neighboring residues). Note that the terms ''fragment'' and ''motif'' are used as synonyms in this manual.

	We can generally say that, within the ''MotiveValidator'' environment, all ''residues'' can be thought of as ''motifs''. Therefore, different ''instances of the same residue'' (such as multiple arginine residues throughout the sequence of a protein, or copies of the same ligand in different monomers) can be considered and processed as different ''motifs'', making their identification straightforward and unambiguous.		We can generally say that, within the '''MotiveValidator''' environment, all ''residues'' can be thought of as ''motifs''. Therefore, different ''instances of the same residue'' (such as multiple arginine residues throughout the sequence of a protein, or copies of the same ligand in different monomers) can be considered and processed as different ''motifs'', making their identification straightforward and unambiguous.

	We use the term model residue (or simply model) to refer to a particular structure that is known to be correct. This structure will then be used as reference template in the validation process, whereby a query residue with the same name (3-letter code) as the model will be compared to the model. Within the ''MotiveValidator'' environment, a model contains one residue. The origin of the model can be the wwPDB chemical component dictionary accessible via LigandExpo, or a custom model provided by the user.

			We use the term model residue (or simply model) to refer to a particular structure that is known to be correct. This structure will then be used as reference template in the validation process, whereby a query residue with the same name (3-letter code) as the model will be compared to the model. Within the '''MotiveValidator''' environment, a model contains one residue. The origin of the model can be the wwPDB chemical component dictionary accessible via LigandExpo, or a custom model provided by the user.

	=Validation terminology=		=Validation terminology=

Lukas at 13:13, 7 July 2014

2014-07-07T13:13:37Z

← Older revision		Revision as of 13:13, 7 July 2014
Line 1:		Line 1:
	Below you can find an established meaning of a key terms within the ~~'''~~MotiveValidator~~'''~~ and ~~'''~~ValidatorDB~~'''~~ environment.		Below you can find an established meaning of a key terms within the [[MotiveValidator]] and [[ValidatorDB]] environment.

	=Residue=		=Residue=
Line 16:		Line 16:
	refers to a fragment made up from the residue under study, together with its surroundings (i.e., atoms from neighboring residues). Note that the terms ''fragment'' and ''motif'' are used as synonyms in this manual.		refers to a fragment made up from the residue under study, together with its surroundings (i.e., atoms from neighboring residues). Note that the terms ''fragment'' and ''motif'' are used as synonyms in this manual.

			We can generally say that, within the ''MotiveValidator'' environment, all ''residues'' can be thought of as ''motifs''. Therefore, different ''instances of the same residue'' (such as multiple arginine residues throughout the sequence of a protein, or copies of the same ligand in different monomers) can be considered and processed as different ''motifs'', making their identification straightforward and unambiguous.

	We ~~can generally say~~ that, ~~within~~ the '''MotiveValidator''' environment, ~~all ''residues'' can be thought of as ''motifs''~~. ~~Therefore, different ''instances~~ of the ~~same residue'' (such as multiple arginine residues throughout~~ the ~~sequence of a protein~~, or ~~copies of~~ the ~~same ligand in different monomers) can be considered and processed as different ''motifs'', making their identification straightforward and unambiguous~~.		We use the term model residue (or simply model) to refer to a particular structure that is known to be correct. This structure will then be used as reference template in the validation process, whereby a query residue with the same name (3-letter code) as the model will be compared to the model. Within the ''MotiveValidator'' environment, a model contains one residue. The origin of the model can be the wwPDB chemical component dictionary accessible via LigandExpo, or a custom model provided by the user.

	We use the term model residue (or simply model) to refer to a particular structure that is known to be correct. This structure will then be used as reference template in the validation process, whereby a query residue with the same name (3-letter code) as the model will be compared to the model. Within the '''MotiveValidator''' environment, a model contains one residue. The origin of the model can be the wwPDB chemical component dictionary accessible via LigandExpo<ref name="ligandexpo">Feng,Z., Chen,L., Maddula,H., Akcan,O., Oughtred,R., Berman,H.M. and Westbrook,J. (2004) [http://dx.doi.org/10.1093/bioinformatics/bth214 Ligand Depot: a data warehouse for ligands bound to macromolecules]. Bioinformatics, 20, 2153–5.</ref>, or a custom model provided by the user.

	=~~Model residue~~=		=Validation terminology=
	~~We use the term~~ ''~~model~~ residue'' ~~(or~~ simply ''model''~~) to refer to~~ a particular structure that is known to be correct. This structure ~~will~~ then be used as reference template in the validation process, whereby a query residue with the same name (3-letter code) as the model will be compared to the model. Within the '''MotiveValidator''' environment, a model contains one residue. The origin of the ''model'' can be the wwPDB chemical component dictionary accessible via LigandExpo, or a custom model provided by the user.		* '''Model residue:''' Or simply ''model''is a particular structure that is known to be correct. This structure is then used as reference template in the validation process, whereby a query residue with the same name (3-letter code) as the model will be compared to the model. Within the ''MotiveValidator'' environment, a model contains one residue. The origin of the ''model'' can be the wwPDB chemical component dictionary accessible via LigandExpo<ref name ="ligandexpo"/>, or a custom model provided by the user.
			* '''Residue to be validated:''' Residue of interest for validation.
			* '''Input motif:''' Residues to be validated together with their immediate surroundings (i.e. atoms within one or two bonds of any atom of the residue to be validated).
			* '''Validated motif:''' The subset of atoms from the input motif paired with atoms in the model residue.


	=References=		=References=
	<references/>		<references>
			<ref name="ligandexpo">Feng,Z., Chen,L., Maddula,H., Akcan,O., Oughtred,R., Berman,H.M. and Westbrook,J. (2004) [http://dx.doi.org/10.1093/bioinformatics/bth214 Ligand Depot: a data warehouse for ligands bound to macromolecules]. Bioinformatics, 20, 2153–5.</ref>
			</references>

Lukas at 15:26, 2 July 2014

2014-07-02T15:26:45Z

← Older revision		Revision as of 15:26, 2 July 2014
Line 19:		Line 19:
	We can generally say that, within the '''MotiveValidator''' environment, all ''residues'' can be thought of as ''motifs''. Therefore, different ''instances of the same residue'' (such as multiple arginine residues throughout the sequence of a protein, or copies of the same ligand in different monomers) can be considered and processed as different ''motifs'', making their identification straightforward and unambiguous.		We can generally say that, within the '''MotiveValidator''' environment, all ''residues'' can be thought of as ''motifs''. Therefore, different ''instances of the same residue'' (such as multiple arginine residues throughout the sequence of a protein, or copies of the same ligand in different monomers) can be considered and processed as different ''motifs'', making their identification straightforward and unambiguous.

	We use the term model residue (or simply model) to refer to a particular structure that is known to be correct. This structure will then be used as reference template in the validation process, whereby a query residue with the same name (3-letter code) as the model will be compared to the model. Within the '''MotiveValidator''' environment, a model contains one residue. The origin of the model can be the wwPDB chemical component dictionary accessible via LigandExpo<ref>~~{{cite~~ doi \| 10.1093/bioinformatics/bth214}}</ref>, or a custom model provided by the user.		We use the term model residue (or simply model) to refer to a particular structure that is known to be correct. This structure will then be used as reference template in the validation process, whereby a query residue with the same name (3-letter code) as the model will be compared to the model. Within the '''MotiveValidator''' environment, a model contains one residue. The origin of the model can be the wwPDB chemical component dictionary accessible via LigandExpo<ref name="ligandexpo">Feng,Z., Chen,L., Maddula,H., Akcan,O., Oughtred,R., Berman,H.M. and Westbrook,J. (2004) [http://dx.doi.org/10.1093/bioinformatics/bth214 Ligand Depot: a data warehouse for ligands bound to macromolecules]. Bioinformatics, 20, 2153–5.</ref>, or a custom model provided by the user.

	=Model residue=		=Model residue=

Lukas: /* Motif / Fragment */

2014-07-02T14:58:08Z

Motif / Fragment

← Older revision		Revision as of 14:58, 2 July 2014
Line 19:		Line 19:
	We can generally say that, within the '''MotiveValidator''' environment, all ''residues'' can be thought of as ''motifs''. Therefore, different ''instances of the same residue'' (such as multiple arginine residues throughout the sequence of a protein, or copies of the same ligand in different monomers) can be considered and processed as different ''motifs'', making their identification straightforward and unambiguous.		We can generally say that, within the '''MotiveValidator''' environment, all ''residues'' can be thought of as ''motifs''. Therefore, different ''instances of the same residue'' (such as multiple arginine residues throughout the sequence of a protein, or copies of the same ligand in different monomers) can be considered and processed as different ''motifs'', making their identification straightforward and unambiguous.

	We use the term model residue (or simply model) to refer to a particular structure that is known to be correct. This structure will then be used as reference template in the validation process, whereby a query residue with the same name (3-letter code) as the model will be compared to the model. Within the '''MotiveValidator''' environment, a model contains one residue. The origin of the model can be the wwPDB chemical component dictionary accessible via LigandExpo<ref>{{cite doi 10.1093/bioinformatics/bth214}}</ref>, or a custom model provided by the user.		We use the term model residue (or simply model) to refer to a particular structure that is known to be correct. This structure will then be used as reference template in the validation process, whereby a query residue with the same name (3-letter code) as the model will be compared to the model. Within the '''MotiveValidator''' environment, a model contains one residue. The origin of the model can be the wwPDB chemical component dictionary accessible via LigandExpo<ref>{{cite doi \| 10.1093/bioinformatics/bth214}}</ref>, or a custom model provided by the user.


	=Model residue=		=Model residue=

Lukas at 22:12, 19 June 2014

2014-06-19T22:12:15Z

← Older revision		Revision as of 22:12, 19 June 2014
Line 19:		Line 19:
	We can generally say that, within the '''MotiveValidator''' environment, all ''residues'' can be thought of as ''motifs''. Therefore, different ''instances of the same residue'' (such as multiple arginine residues throughout the sequence of a protein, or copies of the same ligand in different monomers) can be considered and processed as different ''motifs'', making their identification straightforward and unambiguous.		We can generally say that, within the '''MotiveValidator''' environment, all ''residues'' can be thought of as ''motifs''. Therefore, different ''instances of the same residue'' (such as multiple arginine residues throughout the sequence of a protein, or copies of the same ligand in different monomers) can be considered and processed as different ''motifs'', making their identification straightforward and unambiguous.

	We use the term model residue (or simply model) to refer to a particular structure that is known to be correct. This structure will then be used as reference template in the validation process, whereby a query residue with the same name (3-letter code) as the model will be compared to the model. Within the '''MotiveValidator''' environment, a model contains one residue. The origin of the model can be the wwPDB chemical component dictionary accessible via LigandExpo, or a custom model provided by the user.		We use the term model residue (or simply model) to refer to a particular structure that is known to be correct. This structure will then be used as reference template in the validation process, whereby a query residue with the same name (3-letter code) as the model will be compared to the model. Within the '''MotiveValidator''' environment, a model contains one residue. The origin of the model can be the wwPDB chemical component dictionary accessible via LigandExpo<ref>{{cite doi 10.1093/bioinformatics/bth214}}</ref>, or a custom model provided by the user.


Line 27:		Line 27:

	=References=		=References=
			<references/>

Lukas at 07:28, 19 June 2014

2014-06-19T07:28:39Z

← Older revision		Revision as of 07:28, 19 June 2014
Line 1:		Line 1:
	~~TODO~~		Below you can find an established meaning of a key terms within the '''MotiveValidator''' and '''ValidatorDB''' environment.

			=Residue=
			We use the term ''residue'' to refer to any component of a biomacromolecule or a biomacromolecular complex. This includes amino acid residues and nucleotides, which are commonly referred to as residues as they form proteins and nucleic acids. Within the '''MotiveValidator''' environment, any collection of atoms bound by chemical bonds (covalent, coordinative or ionic) can be considered a residue as long as this fact is appropriately indicated in the input PDB file. Specifically, all the atoms that make up a residue should have the same ''residue name'' (3-letter code) and ''residue identifier'' (index internal to the input PDB file).

			=Ligand=
			We use the term ''ligand'' to refer to a chemical compound which forms a complex with a biomacromolecule (e.g., sugar, drug, heme). Ions can also function as self standing ligands, or they can be part of a residue (such as Fe in heme). In the PDB format, a ligand has its own residue identifier and 3-letter code, and is composed from HETATM records. The '''MotiveValidator''' term [[#Residue \| residue]] thus fully covers ligands, in addition to typical components like amino acids and nucleotides.

			=Sugar=
			We use the term ''sugar'' to refer to the special case when a residue belongs to a carbohydrate (saccharide).

			=Motif / Fragment=
			With respect to the chemistry of biomolecules, the term ''motif'' is used to refer to a well defined distribution of structural elements in a biomolecule or biomolecular complex, with characteristics
			generally associated with a specific function. Within the '''MotiveValidator''' environment, a ''motif'' is generally a fragment of a biomacromolecule, biomacromolecular complex or ligand, made up of
			one or more residues or parts of residues. A ''motif'' can in principle be any fragment of a biomolecule. Nonetheless, '''MotiveValidator''' is focused on the validation of residues, thus here ''motif'' generally
			refers to a fragment made up from the residue under study, together with its surroundings (i.e., atoms from neighboring residues). Note that the terms ''fragment'' and ''motif'' are used as synonyms in this manual.


			We can generally say that, within the '''MotiveValidator''' environment, all ''residues'' can be thought of as ''motifs''. Therefore, different ''instances of the same residue'' (such as multiple arginine residues throughout the sequence of a protein, or copies of the same ligand in different monomers) can be considered and processed as different ''motifs'', making their identification straightforward and unambiguous.

			We use the term model residue (or simply model) to refer to a particular structure that is known to be correct. This structure will then be used as reference template in the validation process, whereby a query residue with the same name (3-letter code) as the model will be compared to the model. Within the '''MotiveValidator''' environment, a model contains one residue. The origin of the model can be the wwPDB chemical component dictionary accessible via LigandExpo, or a custom model provided by the user.


			=Model residue=
			We use the term ''model residue'' (or simply ''model'') to refer to a particular structure that is known to be correct. This structure will then be used as reference template in the validation process, whereby a query residue with the same name (3-letter code) as the model will be compared to the model. Within the '''MotiveValidator''' environment, a model contains one residue. The origin of the ''model'' can be the wwPDB chemical component dictionary accessible via LigandExpo, or a custom model provided by the user.


			=References=

Lukas: Created page with "TODO"

2014-06-18T13:18:18Z

Created page with "TODO"

New page

TODO