working version

.gitignore

@@ -14,4 +14,5 @@ index*
 # *.npz
 /.quarto/
 my.txt
-LLM.txt
+LLM.txt
+Output/

Data/12_Each_Page/right_Nav copy.qmd

@@ -0,0 +1,131 @@
+
+
+<script>
+console.log("Right Nav script is found and activated");
+</script>
+
+
+<div id="popper_Tooltip_Gen">
+    Feel free to share your thoughts 
+<div id="pop_Arrow_Gen" data-popper-arrow></div>
+</div>
+
+<!-- Production version -->
+<script src="https://unpkg.com/@popperjs/core@2"></script>
+
+<!-- load external javascript-code -->
+<!--these loads is required since the path from where the access to the scripts happens varies-->
+<!-- <script src="../../../Web_Code/Js/lotti_Sidebar_Anim.js"></script> -->
+<!-- <script src="../../Web_Code/Js/lotti_Sidebar_Anim.js"></script>
+<script src="../Web_Code/Js/lotti_Sidebar_Anim.js"></script>
+<script src="./Web_Code/Js/lotti_Sidebar_Anim.js"></script> -->
+
+<script src="/Web_Code/Js/popper_Tooltip_General.js"></script>
+<script src="/Web_Code/Js/lotti_Sidebar_Anim.js"></script>
+
+<!-- <script src="../../../Web_Code/Js/popper_Tooltip_General.js"></script> -->
+<!-- <script src="../../Web_Code/Js/popper_Tooltip_General.js"></script>
+<script src="../Web_Code/Js/popper_Tooltip_General.js"></script>
+<script src="./Web_Code/Js/popper_Tooltip_General.js"></script> -->
+
+<!-- documentation: https://docs.lottiefiles.com/dotlottie-player/ -->j
+<script src="https://unpkg.com/@dotlottie/player-component@latest/dist/dotlottie-player.js"></script>
+
+<dotlottie-player 
+id="lotti_Anim_Each_Page"
+mode="normal" 
+style="max-height:15rem"
+background="transparent"
+speed="1"
+> 
+</dotlottie-player>
+
+<script>
+// get acceess to the right sidebar
+const quartoMarginSidebar = document.getElementById("quarto-margin-sidebar");
+
+// generate a place where the lotti animation shall be placed
+const player = document.getElementById('lotti_Anim_Each_Page');
+
+// take it from the previous position an move it to the new posistion --> removed prom previous DOM pos
+quartoMarginSidebar.insertBefore(player, quartoMarginSidebar.firstChild);
+
+
+/* --------------------------- get Feedback <p><a> -------------------------- */
+// Create a new <p> element
+const button_Elem = document.createElement('button');
+
+// Create a new <a> element
+const aElement = document.createElement('a');
+
+// Set the href attribute of the <a> element
+aElement.href = 'https://discord.gg/EEsXp39DaA';
+aElement.id = 'feedback_A';
+button_Elem.id = 'feedback_Button';
+
+// button_Elem.setAttribute("aria-describedby","popper_Tooltip_Gen");
+// aElement.setAttribute("aria-describedby","popper_Tooltip_Gen");
+
+// Set the text content of the <a> element
+const linkText = document.createElement('span');
+linkText.textContent = 'Share your thoughts';
+
+// Create a new SVG element
+const svgElement = document.createElementNS('http://www.w3.org/2000/svg', 'svg');
+svgElement.setAttribute('viewBox', '0 0 512 512'); // set the viewBox attribute to define the SVG size
+svgElement.setAttribute('class', 'ionicon'); // set the class attribute to apply any CSS styles
+svgElement.setAttribute('width', '2rem'); // set the width attribute to scale the SVG
+svgElement.setAttribute('height', '2rem'); // set the height attribute to scale the SVG
+
+// Set the content of the SVG element to the contents of the SVG file
+svgElement.innerHTML = `<!-- see https://ionic.io/ionicons/
+see <ion-icon name="chatbox-ellipses-outline"></ion-icon> -->
+<path d="M408 64H104a56.16 56.16 0 00-56 56v192a56.16 56.16 0 0056 56h40v80l93.72-78.14a8 8 0 015.13-1.86H408a56.16 56.16 0 0056-56V120a56.16 56.16 0 00-56-56z" fill="none" stroke="#ecff7f" stroke-linejoin="round" stroke-width="32" />
+<circle cx="160" cy="216" r="32" fill="#ecff7f" />
+<circle cx="256" cy="216" r="32" fill="#ecff7f" />
+<circle cx="352" cy="216" r="32" fill="#ecff7f" />`;
+
+
+// Append the SVG element to the <a> element
+aElement.appendChild(linkText);
+aElement.appendChild(svgElement);
+
+// Append the <a> element to the <p> element
+button_Elem.appendChild(aElement);
+quartoMarginSidebar.insertBefore(button_Elem, player.nextSibling);
+
+// see: https://lottiefiles.com/129292-aeroplane-flying?lang=de 
+player.load('https://assets3.lottiefiles.com/packages/lf20_FsI2nYFYMo.json');
+player.loop = false;
+
+var second_Anim = false;
+
+// Add event listener for click event
+player.addEventListener('click', () => {
+    player.play();
+    complete_Check(second_Anim);
+
+});
+
+
+const popcorn = document.querySelector('#feedback_Button');
+const tooltip = document.querySelector('#popper_Tooltip_Gen');
+
+const popperInstance = Popper.createPopper(popcorn, tooltip, {
+placement: 'top',
+modifiers: [
+    {
+        name: 'offset',
+    options: {
+        offset: [0, 8],
+    },
+    },
+],
+});
+
+run_Pop(popcorn);
+
+</script>
+
+
+

Data/12_Each_Page/right_Nav.qmd

@@ -14,9 +14,10 @@ console.log("Right Nav script is found and activated");
 <script src="https://unpkg.com/@popperjs/core@2"></script>
 
 <!-- load external javascript-code -->
-<script src="../../../Web_Code/Js/lotti_Sidebar_Anim.js"></script>
+<!--these loads is required since the path from where the access to the scripts happens varies-->
+<script src="/Web_Code/Js/lotti_Sidebar_Anim.js"></script>
 
-<script src="../../../Web_Code/Js/popper_Tooltip_General.js"></script>
+<script src="/Web_Code/Js/popper_Tooltip_General.js"></script>
 
 <!-- documentation: https://docs.lottiefiles.com/dotlottie-player/ -->
 <script src="https://unpkg.com/@dotlottie/player-component@latest/dist/dotlottie-player.js"></script>

Data/1_Writing/2_Task/2_Clustering.qmd

@@ -13,9 +13,6 @@ The $F(\vec{\beta})$ and cluster-algorithm specific parameters are filtered and
 <!-- % ============================================== -->
 ![Data and workflow of the second step: Clustering](../../3_Figs_Pyth/2_Task/9_Clust.svg){#fig-fig_12_Clust}
 
-<!--%-->
-<!--%-->
-
 Data clustering is an unsupervised machine learning technique. 
 There are a variety of approaches that may be used for this, e.g., 
 k-means, affinity propagation, mean shift, 

Data/1_Writing/2_Task/3_Tracking.qmd

@@ -90,4 +90,4 @@ The third method was based on the sequence of the labels.
 The idea was that the order of the movement from one centroid to another centroid is known. In other terms, if the current position is at centroid $c_i$ and the next position for centroid $c_{i+1}$ is known. Assuming that the sequences across the $\vec{\beta}$ should be very similar to each other, a majority vote should return the correct tracking results. It can be recorded that this was not the case and the approach was dismissed.\newline
 
 {{< include 4_Track_Workflow.qmd >}}
-{{< include 5_Track_Validity.qmd >}}
+{{< include 5_Track_Validity.qmd >}}

Data/1_Writing/2_Task/4_Track_Workflow.qmd

@@ -1,15 +1,12 @@
+
 After having explained 3 methods, which did not lead to a satisfactory outcome, the data and workflow of the final successful approach shall be presented.
 First very concisely, followed by an in-depth account.
 For that, figure @fig-fig_24_Tracking_Workflow shall be analyzed.
 The initial input is obtained through *settings.py*, where execution, storage and plotting attributes are defined. 
 For the further sub-steps, it shall be noted that the index big O stands for output of the respective sub-step.
-The clustered results from step two, described in section [@sec_2_3_Clustering] are used as input for the so-called ordering step.
+The clustered results from step two, described in section [-@sec-sec_2_3_Clustering] are used as input for the so-called ordering step.
 The ordered state can be stored and plotted if desired and exploited to calculate a cost matrix $\boldsymbol A (\vec{\beta})$. \newline
 
-<!-- % =============================================================================-->
-<!-- % ================ Tracking Workflow ==========================================-->
-<!-- % =============================================================================-->
-<!-- NOTE - sideway -->
 ![General data and workflow overview of the third step, tracking](../../3_Figs_Pyth/2_Task/1_Tracking/3_Track.svg){#fig-fig_24_Tracking_Workflow}
 
 The tracking demand is applied on $\boldsymbol A (\vec{\beta})$, e.g., each row element must be matched to exactly one column element with the constraint that their additive sum is minimized. 

_quarto.yml

@@ -2,6 +2,7 @@
 # https://quarto.org/docs/reference/projects/books.html
 project:
   type: book
+  output-dir: Output/docs
 
   # HTML library (JS/CSS/etc.) directory
   # lib-dir: ["Web_Code/CSS/", "Web_Code/Js"]