> For the complete documentation index, see [llms.txt](https://elishai.gitbook.io/retinal-stimulation-modeling-environment/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://elishai.gitbook.io/retinal-stimulation-modeling-environment/model-specification/biophysical-description.md).

# Biophysical Description

In the biophysical description layer, we specify synapses and cells' biophysical properties. 

Synapses are identified by a name, type, and phase.  Synapse's type is a function-defined dynamics, receiving a list of illuminated or not values and returning a transformed list containing synaptic activation times - the times of each synaptic activation.

In the following XML, we defined a synapse, which follows the dynamic of the light stimulus affecting SACs via Bipolar Cells (BCs). We named this synapse "light synapse". Synapse type was defined as "spatially dependent dynamic", which is defined in the SimSimulation.py file. 

Each synapse is also defined with a weight and an SBML-defined density function, defining the probability of synapse existence as a function of its distance from the soma.

![](/files/-MlQEdBgpY5zIeD_CelT)

Each cell identified by its ID is set with biophysical characteristics. Here we defined the SAC's cytoplasmic resistivity and capacitance. We also set two passive properties: conductance (g\_pas) \[mV] *and equilibrium potential and conductance* (e*\_*pas) \[siemens/cm2].

```
<biophysics xmlns = "RSME.simulation_parameters">

  <biophysics_description> TEST </biophysics_description>

  <biophysics_models>

    <synapses>

        <synapse name='light_synapse' type='spatially_dependent_dynamic' phase = 'on'>

            <density_function>
                <math>
                    <apply>
                        <plus/>
                        <cn> 0 </cn>
                        <apply>
                            <times/>
                            <apply>
                                <lt/>
                                <ci> x </ci>
                                <cn> 125 </cn>
                            </apply> 
			                <cn> 0.2 </cn>
                         </apply>
                    </apply>
                </math>
            </density_function>
            
            <weight>
                <math>
                    <cn> 0.8 </cn>
                </math>
            </weight>
            
        </synapse>

    </synapses>

    <cells>

        <cell_id id = "0" >

            <cytoplasmic_resistivity> 75 </cytoplasmic_resistivity>
            <capicitance> 1 </capicitance>

            <channels_spatial_distribution>
                <pas>
                    <g_pas>
                        <math>
                            <cn> 0.00006 </cn>
                        </math>
                    </g_pas>

                    <e_pas>
                        <math>
                            <cn> -60 </cn>
                        </math>
                    </e_pas>

                </pas>
            </channels_spatial_distribution>

        </cell_id>

     </cells>
     
  </biophysics_models>

</biophysics>

```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://elishai.gitbook.io/retinal-stimulation-modeling-environment/model-specification/biophysical-description.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.