CurrentVoltageRelation

How the current through the channel depends on the conductance of the channel. 
Only ohmic and integrate_and_fire supported at the moment

Complex Type Information

Model

Attributes

QName Type Fixed Default Use Inheritable Annotation
charge xs:positiveInteger optional
Electrical charge of the ion in question
cond_law ConductanceLaw optional
Introduced in v1.7.3 for new format ChannelML. Specifies which type of conductance law to use: ohmic, etc.
default_erev VoltageValue optional
Most implementations of these channel mechanisms (e.g. a mod file) will need a value for the
reversal potential for the ion which flows through the channel. However, this is a property of the cell, as opposed to the channel.
For convenience though, a typical value can be used here, so a pretty self contained script can be produced, but when used in a real cell the
actual value for erev must be calculated
default_gmax ConductanceDensityValue optional
Introduced in v1.7.3 for new format ChannelML. Maximum conductance density of channel. Note this will normally be reset when the channel mechanism is placed on a cell, but it it 
useful to have a default value here.
fixed_erev YesNo no optional
Flags whether the reversal potential can be influenced from outside the channel (value = no; default)
as is normally the case (e.g. a Ca channel whose reversal potential is influenced by a decaying calcium pool), or 
whether the rev pot remains fixed (just for this channel) at default_erev (value = yes)
ion xs:string optional
Introduced in v1.7.3 for new format ChannelML. The ion which will flow due to the conductance. Note this should be already declared in an Ion element at the beginning of the file.

Used By

Source

<xs:complexType name="CurrentVoltageRelation">
  <xs:annotation>
    <xs:documentation>How the current through the channel depends on the conductance of the channel. Only ohmic and integrate_and_fire supported at the moment</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="ohmic" type="Deprecated_Ohmic" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Deprecated since v1.7.3. Use attribute cond_law and gate elements below this element instead.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="integrate_and_fire" type="IntegrateAndFire" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Note: use attribute cond_law="integrate_and_fire" and no other attributes here when using this. Signifies a current which will cause the cell to behave like an integrate and fire neuron</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="conc_dependence" type="ConcDependence" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Preferred location of conc_dependence since v1.7.3.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="conc_factor" type="ConcFactor" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Preferred location of conc_factor since v1.7.3.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="q10_settings" type="Q10Settings" minOccurs="0" maxOccurs="unbounded">
      <xs:annotation>
        <xs:documentation>Preferred location of Q10 information since v1.7.3.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="offset" type="Offset" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Preferred location of offset information since v1.7.3.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="gate" type="GatingComplex" minOccurs="0" maxOccurs="unbounded">
      <xs:annotation>
        <xs:documentation>Preferred way of expressing gating complexes since v1.7.3.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
  <!-- <xs:attribute name="name" type="xs:string"/> removed in v1.7.3 -->
  <xs:attribute name="cond_law" type="ConductanceLaw" use="optional">
    <xs:annotation>
      <xs:documentation>Introduced in v1.7.3 for new format ChannelML. Specifies which type of conductance law to use: ohmic, etc.</xs:documentation>
    </xs:annotation>
  </xs:attribute>
  <xs:attribute name="ion" type="xs:string" use="optional">
    <xs:annotation>
      <xs:documentation>Introduced in v1.7.3 for new format ChannelML. The ion which will flow due to the conductance. Note this should be already declared in an Ion element at the beginning of the file.</xs:documentation>
    </xs:annotation>
  </xs:attribute>
  <xs:attribute name="default_gmax" type="bio:ConductanceDensityValue" use="optional">
    <xs:annotation>
      <xs:documentation>Introduced in v1.7.3 for new format ChannelML. Maximum conductance density of channel. Note this will normally be reset when the channel mechanism is placed on a cell, but it it useful to have a default value here.</xs:documentation>
    </xs:annotation>
  </xs:attribute>
  <xs:attribute name="default_erev" type="bio:VoltageValue" use="optional">
    <xs:annotation>
      <xs:documentation>Most implementations of these channel mechanisms (e.g. a mod file) will need a value for the reversal potential for the ion which flows through the channel. However, this is a property of the cell, as opposed to the channel. For convenience though, a typical value can be used here, so a pretty self contained script can be produced, but when used in a real cell the actual value for erev must be calculated</xs:documentation>
    </xs:annotation>
  </xs:attribute>
  <xs:attribute name="charge" type="xs:positiveInteger" use="optional">
    <xs:annotation>
      <xs:documentation>Electrical charge of the ion in question</xs:documentation>
    </xs:annotation>
  </xs:attribute>
  <xs:attribute name="fixed_erev" type="meta:YesNo" default="no" use="optional">
    <xs:annotation>
      <xs:documentation>Flags whether the reversal potential can be influenced from outside the channel (value = no; default) as is normally the case (e.g. a Ca channel whose reversal potential is influenced by a decaying calcium pool), or whether the rev pot remains fixed (just for this channel) at default_erev (value = yes)</xs:documentation>
    </xs:annotation>
  </xs:attribute>
</xs:complexType>