Fix various issues

.github/workflows/build.yaml

@@ -76,7 +76,7 @@ jobs:
       - name: Build Documentation
         run: pixi run sphinx-build -M html . _build -W --keep-going -a -t draft
 
-      - uses: actions/upload-artifact@v3
+      - uses: actions/upload-artifact@v4
         with:
           name: beta-version
           path: _build/html
@@ -102,7 +102,7 @@ jobs:
         run: pixi run sphinx-build -M html . _build -W --keep-going -a
 
 
-      - uses: actions/upload-artifact@v3
+      - uses: actions/upload-artifact@v4
         with:
           name: tagged-version
           path: _build/html
@@ -111,15 +111,15 @@ jobs:
     needs: [build-latest, build-tagged]
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/download-artifact@v3
+      - uses: actions/download-artifact@v4
         with:
           name: tagged-version
           path: public
-      - uses: actions/download-artifact@v3
+      - uses: actions/download-artifact@v4
         with:
           name: beta-version
           path: public/beta
-      - uses: actions/upload-pages-artifact@v2
+      - uses: actions/upload-pages-artifact@v3
         with: 
           path: public
 

Muscle_modeling/lesson1.md

@@ -144,7 +144,7 @@ involved joints, and where contraction velocities are small.
 
 There are two optional parameters for this model. Vol0 can be used in muscle
 recruitment to form a muscle volume weighted sum of muscle activations; see e.g.
-[^cite_happee-van-der-hel-1995]. `Lf0` can be tuned in a calibration study; then
+[^cite_happee_van_der_hel_1995]. `Lf0` can be tuned in a calibration study; then
 using `Vol0`, modified physiological cross sectional area (`PCSA`) of the
 muscle can be computed by the user (e.g. as `PCSA=Vol0/Lf0`), which can be
 used afterwards to modify the value for `F0`.

Muscle_modeling/lesson5.md

@@ -7,7 +7,7 @@ Muscle model is a description of how a muscle behaves under different
 operating conditions. There are two schools of thought within this area.
 
 - The first school pursues phenomenological models based on
-  the classical work by *A.V. Hill* [^cite_hill-1938]. These models are usually based on
+  the classical work by *A.V. Hill* [^cite_hill_1938]. These models are usually based on
   a description of a muscle as a contractile element in combination
   with a number of elastic elements. While these models make no attempt
   to directly model the microscopic mechanisms of muscle contraction,
@@ -16,7 +16,7 @@ operating conditions. There are two schools of thought within this area.
   efficiency.
 - The second school attempts to directly model the microscopic physical
   phenomena of cross bridge activity in muscle contraction. The origin
-  of these models is usually attributed to *A.F. Huxley* [^cite_huxley-1957], and they lead
+  of these models is usually attributed to *A.F. Huxley* [^cite_huxley_1957], and they lead
   to differential equations and consequently to much more
   computationally demanding models.
 
@@ -48,7 +48,7 @@ for their parameters, and they also need fairly costly calibration steps to impr
 The following introduces the muscle models available in AnyBody. The simple (**AnyMuscleModel**) and the three-element (**AnyMuscleModel3E**) muscle models are the most commonly used ones in the AMMR, whereas the two-element (**AnyMuscleModel2ELin**) and the custom user-defined (**AnyMuscleModelUsr1**) models provide users with even more freedom to test, learn and benchmark muscle-tendon units.
 
 - `AnyMuscleModel`: This is the simplest conceivable muscle model, and it is the one we have used in the preceding lessons of this tutorial. The only required input to the model is the muscle's presumed isometric strength, F0, i.e. the force that the muscle can exert in a static condition at its optimal length. F0 is often believed to be proportional to the physiological cross sectional area of the muscle, and it is possible to find that dimension for most significant muscles in the human body from cadaver studies reported in the scientific literature. It is important to stress that the strength of this muscle model is independent of the muscle's current length and contraction velocity. It is known for a fact that muscles do not behave that way, but for models with moderate contraction velocities and small joint angle variations even this simple model will work reasonably well. Such has been shown to be the case for bicycling and gait. This model has a lesser need for calibration steps, which makes it beneficial to save effort while just preparing preliminary results for instance in a model ptorotyping phase.
-- `AnyMuscleModel3E`: This is a full-blown Hill model that takes parallel passive elasticity of the muscle, serial elasticity of the tendon, pennation angle of the fibers, and many other properties into account. The concepts for this model are adopted from [^cite_zajac-1989]. This model requires several physiological parameters that may be difficult to get or estimate for a particular muscle in a particular individual. Moreover, it applies non-linear force-length and force-velocity relationships, which means that the muscle vary strength depending on the length and contraction velocity. It also means and can loose its strength entirely and this calls for calibration of muscle parameters for each indivudualized model to match the muscle's working range to actual working range of the skeleton.
+- `AnyMuscleModel3E`: This is a full-blown Hill model that takes parallel passive elasticity of the muscle, serial elasticity of the tendon, pennation angle of the fibers, and many other properties into account. The concepts for this model are adopted from [^cite_zajac_1989]. This model requires several physiological parameters that may be difficult to get or estimate for a particular muscle in a particular individual. Moreover, it applies non-linear force-length and force-velocity relationships, which means that the muscle vary strength depending on the length and contraction velocity. It also means and can loose its strength entirely and this calls for calibration of muscle parameters for each indivudualized model to match the muscle's working range to actual working range of the skeleton.
 - `AnyMuscleModel2ELin`: This model is simpler multi-element model than the three-element model. It presumes that the muscle strength is proportional to its current length and contraction velocity. This means that the muscle gets weaker when its length decreases or the contraction velocity increases. In other words, the muscle strength is bilinear in the length and velocity space. The model also presumes that the tendon is linearly elastic and as such contains two elements: A contractile element (the muscle), and a serial-elastic element (the tendon). The rationale behind this model is that a muscle has a certain passive elasticity built into it. If the muscle it stretched far enough, the passive elasticity will build up force and reduce the necessity for active muscle force. This is in some cases equivalent to an increase of the muscle's strength. Notice, however, that this model has the significant drawback that the force can be switched off even if the muscle is stretched very far, while the true passive elasticity will always provide a force when it is stretched. While this model is simpler than the three-element model, it does not provide a more efficient workflow because calibration is typically also needed for this model. Therefore, this model is used less frequently for real applications, because it will be natural to consider the two previously described models when choosing will be between simplicity and accuracy.
 - `AnyMuscleModelUsr1`: This is a custom user-defined muscle model. The user is free to define the strength of the muscle as any explicit expression of muscle variables (e.g. isometric strength (F0), volume(Vol0) or PCSA, fiber length (Lf0)), kinematic measures (e.g. actual fiber length and velocity), and even time. This freedom implies that it is also the user's task to make the most reasonable relationship to muscle and kinematic parameters for instance  to include when such paarmeters are affected by model scaling and calibration.
 

conf.py

@@ -286,7 +286,6 @@ def tagged_commit():
     "use_download_button": False,
     "use_edit_page_button": True,
     "use_issues_button": True,
-    "show_navbar_depth": 2,
     "search_bar_text": "",
     "pygment_light_style": "AnyScript",
     "pygment_dark_style": "stata-dark",