From 50f054c6fef4000f8dc3dd7687287279cae9af2e Mon Sep 17 00:00:00 2001
From: Marco Dalla Tiezza <aresvalley.info@gmail.com>
Date: Wed, 5 Jun 2024 21:03:25 +0200
Subject: [PATCH] Deployed c8fcb2c with MkDocs version: 1.6.0

---
 basic_operations/index.html |   2 +-
 build_package/index.html    |   8 ++++----
 contribute/index.html       |  10 +++++-----
 search/search_index.json    |   2 +-
 sitemap.xml.gz              | Bin 127 -> 127 bytes
 5 files changed, 11 insertions(+), 11 deletions(-)

diff --git a/basic_operations/index.html b/basic_operations/index.html
index 5567609..5a5ec40 100755
--- a/basic_operations/index.html
+++ b/basic_operations/index.html
@@ -1347,7 +1347,7 @@
 <li><strong>Edit Tags:</strong> Open the tags editor window. From here, you can add, rename, or delete tags. The tags can be added to a signal from the <a href="#4-tags">tags menu</a></li>
 <li><strong>Open Database Folder:</strong> Shows the folder of the currently loaded database in the explorer.</li>
 <li><strong>Preferences:</strong> Open the program settings window.</li>
-<li><strong>Exit:</strong> This will simply close the application.</li>
+<li><strong>Exit:</strong> This will close the application.</li>
 </ul>
 <h3 id="signal">Signal</h3>
 <ul>
diff --git a/build_package/index.html b/build_package/index.html
index e600a0e..bae209e 100755
--- a/build_package/index.html
+++ b/build_package/index.html
@@ -1224,7 +1224,7 @@
 
 
 <h1 id="build-package">Build Package</h1>
-<p>Building a distributable package with an executable for Artemis creates a practical solution for end-users, as they can run the application without needing to interact with the terminal and they can easily share the application as a stand-alone package.</p>
+<p>Building a distributable package with an executable for Artemis creates a practical solution for end-users, as they can run the application without needing to interact with the terminal and they can easily share the application as a standalone package.</p>
 <h2 id="requirements">Requirements</h2>
 <ul>
 <li>Python (3.11 or higher)</li>
@@ -1235,7 +1235,7 @@
 </div>
 <div class="admonition warning">
 <p class="admonition-title">Cross-Compilation</p>
-<p>To generate standalone packages, an operating system that matches the target OS must be used, as Nuitka does not support cross-compilation. For example: you cannot build binaries on Windows that work on Linux or macOS.</p>
+<p>An operating system that matches the target OS must be used to generate standalone packages, as Nuitka does not support cross-compilation. For example, you cannot build binaries on Windows that work on Linux or macOS.</p>
 </div>
 <h2 id="windows"><span class="twemoji"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M0 0h11.377v11.372H0Zm12.623 0H24v11.372H12.623ZM0 12.623h11.377V24H0Zm12.623 0H24V24H12.623"/></svg></span> Windows</h2>
 <h3 id="procedure">Procedure</h3>
@@ -1246,7 +1246,7 @@
 </code></pre></div>
 </li>
 <li>
-<p>Wait for the build process to complete. This may take a few minutes depending on your system's performance. Once the process finishes, check the <code>artemis.dist/</code> directory: it will contain the stand-alone software with the <code>artemis.exe</code> executable.</p>
+<p>Wait for the build process to complete. This may take a few minutes depending on your system's performance. Once the process finishes, check the <code>artemis.dist/</code> directory: it will contain the standalone software with the <code>artemis.exe</code> executable.</p>
 </li>
 </ol>
 <hr />
@@ -1259,7 +1259,7 @@
 </code></pre></div></p>
 </li>
 <li>
-<p>Wait for the build process to complete. This may take a few minutes depending on your system's performance. Once the process finishes, check the <code>artemis.dist/</code> directory: it will contain the stand-alone software with the <code>app.bin</code> executable.</p>
+<p>Wait for the build process to complete. This may take a few minutes depending on your system's performance. Once the process finishes, check the <code>artemis.dist/</code> directory: it will contain the standalone software with the <code>app.bin</code> executable.</p>
 </li>
 <li>If you wish to create a shortcut, follows the procedure in the <a href="../installation/#create-a-shortcut">installation section</a></li>
 </ol>
diff --git a/contribute/index.html b/contribute/index.html
index 1555297..673d76d 100755
--- a/contribute/index.html
+++ b/contribute/index.html
@@ -1022,31 +1022,31 @@
 
 
 <h1 id="contribute">Contribute</h1>
-<p>Artemis is an open source project an every contribution, no matter how small, is valuable and greatly appreciated. Don't worry about getting everything perfect, we are happy to work with you on your contribution and help you along the way. This guide will help you get started by outlining various ways you can contribute.</p>
+<p>Artemis is an open-source project, and every contribution, no matter how small, is valuable and greatly appreciated. Don't worry about getting everything perfect; we are happy to work with you on your contribution and help you along the way. This guide will help you get started by outlining various ways you can contribute.</p>
 <div class="grid cards">
 <ul>
 <li>
 <p><span class="twemoji"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M14 12h-4v-2h4m0 6h-4v-2h4m6-6h-2.81a5.985 5.985 0 0 0-1.82-1.96L17 4.41 15.59 3l-2.17 2.17a6.002 6.002 0 0 0-2.83 0L8.41 3 7 4.41l1.62 1.63C7.88 6.55 7.26 7.22 6.81 8H4v2h2.09c-.05.33-.09.66-.09 1v1H4v2h2v1c0 .34.04.67.09 1H4v2h2.81c1.04 1.79 2.97 3 5.19 3s4.15-1.21 5.19-3H20v-2h-2.09c.05-.33.09-.66.09-1v-1h2v-2h-2v-1c0-.34-.04-.67-.09-1H20V8Z"/></svg></span> <strong>Spot a bug?</strong></p>
 <hr />
-<p>Open an issue (or pull request) and let us know the problem you faced (or you're working on)</p>
+<p>Please open an issue (or pull request) and let us know the problem you faced (or you're working on)</p>
 <p><a href="https://github.com/AresValley/Artemis/issues"><span class="twemoji"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M13.22 19.03a.75.75 0 0 1 0-1.06L18.19 13H3.75a.75.75 0 0 1 0-1.5h14.44l-4.97-4.97a.749.749 0 0 1 .326-1.275.749.749 0 0 1 .734.215l6.25 6.25a.75.75 0 0 1 0 1.06l-6.25 6.25a.75.75 0 0 1-1.06 0Z"/></svg></span> Open an Issue</a></p>
 </li>
 <li>
 <p><span class="twemoji"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M6 2a3 3 0 0 1 3 3c0 1.28-.81 2.38-1.94 2.81.09.46.33 1.02.94 1.82 1 1.29 3 3.2 4 4.54 1-1.34 3-3.25 4-4.54.61-.8.85-1.36.94-1.82A3.015 3.015 0 0 1 15 5a3 3 0 0 1 3-3 3 3 0 0 1 3 3c0 1.32-.86 2.45-2.05 2.85-.08.52-.31 1.15-.95 1.98-1 1.34-3 3.25-4 4.55-.61.79-.85 1.35-.94 1.81C14.19 16.62 15 17.72 15 19a3 3 0 0 1-3 3 3 3 0 0 1-3-3c0-1.28.81-2.38 1.94-2.81-.09-.46-.33-1.02-.94-1.81-1-1.3-3-3.21-4-4.55-.64-.83-.87-1.46-.95-1.98A3.015 3.015 0 0 1 3 5a3 3 0 0 1 3-3m0 2a1 1 0 0 0-1 1 1 1 0 0 0 1 1 1 1 0 0 0 1-1 1 1 0 0 0-1-1m12 0a1 1 0 0 0-1 1 1 1 0 0 0 1 1 1 1 0 0 0 1-1 1 1 0 0 0-1-1m-6 14a1 1 0 0 0-1 1 1 1 0 0 0 1 1 1 1 0 0 0 1-1 1 1 0 0 0-1-1Z"/></svg></span> <strong>Fork the repository</strong></p>
 <hr />
-<p>Create your own copy of the codebase that you can modify and submit pull requests from.</p>
+<p>Create a copy of the codebase from which you can modify and submit pull requests.</p>
 <p><a href="https://github.com/AresValley/Artemis"><span class="twemoji"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M13.22 19.03a.75.75 0 0 1 0-1.06L18.19 13H3.75a.75.75 0 0 1 0-1.5h14.44l-4.97-4.97a.749.749 0 0 1 .326-1.275.749.749 0 0 1 .734.215l6.25 6.25a.75.75 0 0 1 0 1.06l-6.25 6.25a.75.75 0 0 1-1.06 0Z"/></svg></span> Fork the repo</a></p>
 </li>
 <li>
 <p><span class="twemoji"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M12 6a6 6 0 0 1 6 6c0 2.22-1.21 4.16-3 5.2V19a1 1 0 0 1-1 1h-4a1 1 0 0 1-1-1v-1.8c-1.79-1.04-3-2.98-3-5.2a6 6 0 0 1 6-6m2 15v1a1 1 0 0 1-1 1h-2a1 1 0 0 1-1-1v-1h4m6-10h3v2h-3v-2M1 11h3v2H1v-2M13 1v3h-2V1h2M4.92 3.5l2.13 2.14-1.42 1.41L3.5 4.93 4.92 3.5m12.03 2.13 2.12-2.13 1.43 1.43-2.13 2.12-1.42-1.42Z"/></svg></span> <strong>Ideas?</strong></p>
 <hr />
-<p>Idea for a new feature? Open an issue on the project's GitHub repository to describe your proposal in detail.</p>
+<p>Idea for a new feature? Open an issue on the project's GitHub repository to describe your proposal.</p>
 <p><a href="https://github.com/AresValley/Artemis/issues"><span class="twemoji"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M13.22 19.03a.75.75 0 0 1 0-1.06L18.19 13H3.75a.75.75 0 0 1 0-1.5h14.44l-4.97-4.97a.749.749 0 0 1 .326-1.275.749.749 0 0 1 .734.215l6.25 6.25a.75.75 0 0 1 0 1.06l-6.25 6.25a.75.75 0 0 1-1.06 0Z"/></svg></span> Open an Issue</a></p>
 </li>
 <li>
 <p><span class="twemoji"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="m12 21.35-1.45-1.32C5.4 15.36 2 12.27 2 8.5 2 5.41 4.42 3 7.5 3c1.74 0 3.41.81 4.5 2.08C13.09 3.81 14.76 3 16.5 3 19.58 3 22 5.41 22 8.5c0 3.77-3.4 6.86-8.55 11.53L12 21.35Z"/></svg></span> <strong>Spreading the word!</strong></p>
 <hr />
-<p>Do you like Artemis? Don't forgeto to share it with your network and your friends!</p>
+<p>Do you like Artemis? Remember to share it with your network and your friends!</p>
 </li>
 </ul>
 </div>
diff --git a/search/search_index.json b/search/search_index.json
index 8c840ca..df1174b 100755
--- a/search/search_index.json
+++ b/search/search_index.json
@@ -1 +1 @@
-{"config":{"lang":["en"],"separator":"[\\s\\-]+","pipeline":["stopWordFilter"]},"docs":[{"location":"","title":"Documentation","text":"<p>Artemis is a software designed to assist radio frequency (RF) signal identification and storage. It simplifies real-time spectrum analysis by leveraging one of the most extensive and community-driven databases, containing nearly 500 recognized signals. This comprehensive software solution allows users to collect RF signals with specific parameters such as frequency, bandwidth, modulation, etc. Users can also store spectrum waterfalls, audio samples, and all types of documents for future reference. Artemis provides a robust platform to manage a wide range of RF data with precision and ease.</p>"},{"location":"acf_analysis/","title":"Autocorrelation Function (ACF)","text":""},{"location":"acf_analysis/#theoretical-introduction","title":"Theoretical Introduction","text":"<p>Correlation functions are valuable mathematical tools utilized across various scientific disciplines, including engineering, physics, and chemistry. The cross-correlation function, commonly defined as a sliding inner (dot) product, quantifies the similarity between two signals as a function of a temporal shift applied to one of them:</p> \\[ \\left[ k*l \\right]\\equiv \\int_{-\\infty}^{+\\infty}k^{*}(t)l(t+\\tau)dt \\] <p>where \\(k\\) and \\(l\\) are two general non-discrete functions without discontinuity, \\(k^{*}\\) is the complex conjugate of \\(k\\) and \\(\\tau\\) is the lag (time delay for signal analysis). This representation is closely related to the convolution theorem by the following relationship:</p> \\[ k(t)*l(t)\\equiv k^{*}(-t)*l(t) \\] <p>In our case, the signal must be compared with itself to identify periodic patterns or detect anomalous high degrees of similarity within a given time interval. To achieve this objective, we can employ the Autocorrelation Function (ACF), which is essentially the cross-correlation of a signal with itself, where \\(k(t)=l(t)\\). The following equation defines the ACF, derived from a straightforward modification of the initial equation:</p> \\[ \\left[ k*k \\right](\\tau)\\equiv \\int_{-\\infty}^{+\\infty}k^{*}(t)k(t+\\tau)dt \\] <p>Within a discrete data set composed by \\(Y(t)\\) records we can easily calculate autocorrelation from:</p> \\[ \\rho_{\\tau}=\\frac{\\sum_{i=1}^{N-\\tau}(Y_i-\\bar{Y})(Y_{i+\\tau}-\\bar{Y})}{\\sum_{i=1}^{N}(Y_i-\\bar{Y})^2} \\] <p>where \\(Y_{i+\u03c4}\\) is a lagged data by \\(\u03c4\\) of \\(Y_i\\) and \\(\\bar{Y}\\) is the average value of the original data set. Entire denominator is used to keep the normalization condition, indeed \u03c1\u03c4 can assume a value between -1 (exact anticorrelation) and +1 (exact correlation). A complete correlation can be only achieved with a perfect overlap of the analyzed function with it self; the simple way to verify that is when \\(\u03c4=0\\)</p> <p></p>"},{"location":"acf_analysis/#example-acf-analysis","title":"Example: ACF Analysis","text":""},{"location":"acf_analysis/#stanag-4285","title":"STANAG 4285","text":"<p>The first example will be a NATO standard known as STANAG 4285. You can download a .wav sample from HERE. We start to collect some information about the structure of this signal: a good starting point is the official declassified NATO document dated 1989. The main frame structure can be found at Annex A-3/5 with a graphical view at Annex A-7, also reported below:</p> <ul> <li>STANAG 4285 (i)</li> <li>STANAG 4285 A-3</li> <li>STANAG 4285 A-4</li> <li>STANAG 4285 A-5</li> <li>STANAG 4285 A-7</li> </ul> <p>Summary</p> <ul> <li>1 x 80 bits of synchronization pattern</li> <li>4 x 32 bits of data</li> <li>3 x 16 bits of reference</li> </ul> <p>Therefore, a full sequence will be composed as the sum of all symbols reported above: 256 symbols recursively transmitted at the ratio of 2400 bauds means a redundancy of 106.66 ms. To analyze an unknown signal I strongly recommend Signal Analyzer (SA). SA is actually one of the most valuable and priceless software available by Sergey Makarov (\u041c\u0430\u043a\u0430\u0440\u043e\u0432 \u0421\u0435\u0440\u0433\u0435\u0439 \u041c\u0438\u0445\u0430\u0439\u043b\u043e\u0432\u0438\u0447, sadly passed away on 29 May 2012) and it used to perform several tests on data sample coded as .wav or .mp3 file. The signal waterfall is reported below:</p> <p></p> <p>When an Autocorrelation function is applied on selected data frame (see above), the result shows a clear recursive pattern with a gap of 106.244 ms between every peak as expected. An ACF refinement can be done into WaveForm windows where we can also notice an identical structure as reported by the specifications</p> <p> </p> <p>Summary</p> <ol> <li>Synchronization pattern is composed by \\(2400*33.013E-3=79.2\\simeq 80\\) symbols</li> <li>Data group contain \\(2400*13.348E-3=32.0=32\\) symbols</li> <li>Reference sequence is formed by \\(2400*6.674E-3=16.02\\simeq 16\\) symbols</li> </ol>"},{"location":"basic_operations/","title":"Basic Operations","text":""},{"location":"basic_operations/#1-main-menu","title":"1. Main Menu","text":""},{"location":"basic_operations/#file","title":"File","text":"<ul> <li>New Database: Create a new database.</li> <li>Load Database: Open the Database Manager windows in order to open, rename, or delete a database.</li> <li>Import Database: Import an Artemis database with a standard .tar format.</li> <li>Export Database: Export the loaded database with a standard .tar format.</li> <li>Edit Tags: Open the tags editor window. From here, you can add, rename, or delete tags. The tags can be added to a signal from the tags menu</li> <li>Open Database Folder: Shows the folder of the currently loaded database in the explorer.</li> <li>Preferences: Open the program settings window.</li> <li>Exit: This will simply close the application.</li> </ul>"},{"location":"basic_operations/#signal","title":"Signal","text":"<ul> <li>New: Add a new signal to the database.</li> <li>Edit: Edit the current/selected signal from the loaded database.</li> </ul>"},{"location":"basic_operations/#space-weather","title":"Space Weather","text":"<ul> <li>Check Report: Open the main Space Weather window and retrieve all the live data from Poseidon Crawler.</li> </ul>"},{"location":"basic_operations/#2-signal-list","title":"2. Signal List","text":"<p>This is the signal list where all the database entries are shown. When a signal is selected, it will load on the right panel.</p>"},{"location":"basic_operations/#filter-by-namedescription","title":"Filter by Name/Description","text":"<p>On top of the list, there is a field for filtering signals by name or any keyword inside the description of the signal: this filter has the highest priority among all the filters.</p>"},{"location":"basic_operations/#3-signal-menu","title":"3. Signal Menu","text":"<p>Here you can swithc between the main signal window and the filter page.</p>"},{"location":"basic_operations/#4-tags","title":"4. Tags","text":"<ul> <li>Associate Tag: Custom tags can be associated to the selected signal with the  icon</li> <li>Remove Tag: In order to remove a tag, just click on its badge. </li> <li>Add/Rename Tag: To add a new tag open the Tags Editor in the main menu.</li> </ul>"},{"location":"basic_operations/#5-add-parameter","title":"5. Add Parameter","text":"<p>Click on the labels to add the corresponding parameter to the signal (e.g. click on Frequency to add a new frequency).</p>"},{"location":"basic_operations/#6-edit-parameter","title":"6. Edit Parameter","text":"<p>Click on the parameter badge to open the Signal Editor windows. From here, you can edit or delete the corresponding parameter.</p> <p>Parameter Description</p> <p>All the parameters have a description field: if some text is added, it will appear when the corresponding parameter badge is hovered with the mouse pointer.</p>"},{"location":"basic_operations/#7-description","title":"7. Description","text":"<p>This is the description of the signal and can be edited from the Main Menu (<code>Signal/Edit...</code>)</p> <p>Markdown Supported</p> <p>The Description field can render Markdown, a simple markup language for creating rich text using plain text. Headers, emphasis, lists, links, code blocks, and many more features for advanced text formatting. Markdown Basic Syntax </p>"},{"location":"basic_operations/#8-audio-sample","title":"8. Audio Sample","text":"<p>This is a player where an audio sample of the signal can be played. To associate an audio file to be shown as the main audio sample, check in the extra menu below the signal spectrum.</p>"},{"location":"basic_operations/#9-image-sample","title":"9. Image Sample","text":"<p>This is an image box that commonly contains the signal spectrum/waterfall. To associate an image file to be shown as the main image sample, check in the extra menu below the signal spectrum.</p>"},{"location":"basic_operations/#10-extra","title":"10. Extra","text":"<p> This button is only available for the standard SigID wiki database and connects the local signal to its counterpart on the sigidwiki website.</p> <p> This will open the Documents Manager. From here you can add any file (audio, image, pdf, etc.) to the signal entry. It is also possible to mark only one image and one audio to be shown on the main signal window.</p>"},{"location":"build_package/","title":"Build Package","text":"<p>Building a distributable package with an executable for Artemis creates a practical solution for end-users, as they can run the application without needing to interact with the terminal and they can easily share the application as a stand-alone package.</p>"},{"location":"build_package/#requirements","title":"Requirements","text":"<ul> <li>Python (3.11 or higher)</li> </ul> <p>Info</p> <p>We assume that Python is already installed on the system and the Artemis source code has been downloaded and extracted. If these prerequisites are not met, please follow steps 1 to 3 in the run from source section.</p> <p>Cross-Compilation</p> <p>To generate standalone packages, an operating system that matches the target OS must be used, as Nuitka does not support cross-compilation. For example: you cannot build binaries on Windows that work on Linux or macOS.</p>"},{"location":"build_package/#windows","title":"Windows","text":""},{"location":"build_package/#procedure","title":"Procedure","text":"<ol> <li> <p>Open a PowerShell terminal in the main Artemis folder and execute the following command to start the build process:</p> <pre><code>.\\building\\Windows\\build_windows.ps1\n</code></pre> </li> <li> <p>Wait for the build process to complete. This may take a few minutes depending on your system's performance. Once the process finishes, check the <code>artemis.dist/</code> directory: it will contain the stand-alone software with the <code>artemis.exe</code> executable.</p> </li> </ol>"},{"location":"build_package/#linux","title":"Linux","text":""},{"location":"build_package/#procedure_1","title":"Procedure","text":"<ol> <li> <p>Open a terminal in the main Artemis folder and execute the following command to start the build process:     <pre><code>. ./building/Linux/build_linux.sh\n</code></pre></p> </li> <li> <p>Wait for the build process to complete. This may take a few minutes depending on your system's performance. Once the process finishes, check the <code>artemis.dist/</code> directory: it will contain the stand-alone software with the <code>app.bin</code> executable.</p> </li> <li>If you wish to create a shortcut, follows the procedure in the installation section</li> </ol>"},{"location":"build_package/#mac-os","title":"Mac OS","text":"<p>Warning</p> <p>The support for the macOS compiled version of the program is temporarily limited due to a lack of machines for extensive testing. Feel free to contribute by reporting any issues you encounter by opening an Issue.</p>"},{"location":"build_package/#procedure_2","title":"Procedure","text":"<ol> <li>Open a terminal in the main Artemis folder and execute the following command to start the build process:     <pre><code>. ./building/macOS/build_macos.sh\n</code></pre></li> </ol>"},{"location":"contribute/","title":"Contribute","text":"<p>Artemis is an open source project an every contribution, no matter how small, is valuable and greatly appreciated. Don't worry about getting everything perfect, we are happy to work with you on your contribution and help you along the way. This guide will help you get started by outlining various ways you can contribute.</p> <ul> <li> <p> Spot a bug?</p> <p>Open an issue (or pull request) and let us know the problem you faced (or you're working on)</p> <p> Open an Issue</p> </li> <li> <p> Fork the repository</p> <p>Create your own copy of the codebase that you can modify and submit pull requests from.</p> <p> Fork the repo</p> </li> <li> <p> Ideas?</p> <p>Idea for a new feature? Open an issue on the project's GitHub repository to describe your proposal in detail.</p> <p> Open an Issue</p> </li> <li> <p> Spreading the word!</p> <p>Do you like Artemis? Don't forgeto to share it with your network and your friends!</p> </li> </ul>"},{"location":"credits/","title":"License &amp; Credits","text":""},{"location":"credits/#license","title":"License","text":"<p>Artemis is maintained by Marco Dalla Tiezza and released under the GPLv3 license.</p>"},{"location":"credits/#credits","title":"Credits","text":"<ul> <li>Marco Dalla Tiezza - Artemis I-II-IV developer, DB parsing, Website</li> <li>Alessandro Ceccato - Artemis III lead developer</li> <li>Paolo Romani (IZ1MLL) - Lead \u03b2 Tester, RF specialist</li> <li>Carl Colena - Sigidwiki admin, \u03b2 Tester, Signals expert</li> <li>Marco Bortoli - macOS deployment, \u03b2 Tester</li> <li>Eric Wiessner (KI7POL) - ARM port (Raspberry Pi3B+ and Pi4B)</li> <li>Pierpaolo Pravatto - Wiki page, \u03b2 Tester</li> <li>Francesco Capostagno, Luca, Pietro - \u03b2 Tester</li> </ul>"},{"location":"credits/#donators","title":"Donators","text":"<ul> <li>Eric Hahn</li> <li>Alan Lawrence</li> <li>Diego Gil Fernandez</li> <li>Torsten Teichert</li> <li>Charles Preston</li> <li>Brad Hein</li> <li>Paolo Romani</li> <li>Michelle Corbani</li> <li>Martin van Duinen</li> <li>Valentino Zardi</li> <li>Emmanuel Fabre</li> <li>Oscar Nilsson</li> <li>Pierre Declercq</li> <li>Detlef Jahn</li> <li>Oliver Schellenberg</li> <li>Stephane Imbertone</li> <li>Roel Ketelaars</li> <li>Timothy Ehrhart</li> <li>George Mager</li> <li>Gerhard Amon</li> <li>Gerald Schmidt</li> <li>Carlos Rocha</li> <li>Joshua Frohberg</li> <li>Bill Riches</li> <li>Jeffrey Krehbiel</li> <li>\u0412\u043e\u043b\u043e\u0434\u0438\u043c\u0438\u0440 \u0411\u0430\u0433\u043c\u0435\u0442</li> <li>Philip Hamlin</li> <li>David Davies</li> <li>Nigel P. Lawrence</li> <li>Marco Rissi (PP5ZX)</li> <li>Martin van Duinen</li> <li>Alex Diamantopulo</li> <li>Joseph Winter</li> <li>Mark Bender</li> <li>Rolf Gerhardt</li> <li>Denese Harris</li> <li>Benjamin Steele</li> <li>Alexander Irmscher</li> <li>Jonathan Chang</li> <li>Torsten Lipke</li> <li>Massimo Petrantoni</li> <li>William Arcand</li> <li>Jon Carp</li> <li>Robert Crone</li> <li>William Houston</li> <li>Richard Quasne</li> <li>Tom Krugliakov</li> <li>Francisco Neira Basso</li> <li>Alistair Macrae</li> <li>Kevin Arburn</li> <li>Marek Bar\u0142\u00f3g</li> <li>Gabriel Gl\u00f6smann</li> <li>Corbin Williams</li> <li>Ton Machielsen</li> <li>Ivan Rancic</li> <li>Alipio Fernandez</li> <li>Matt Eisele</li> <li>Martin Dudel</li> <li>Harald Geier</li> </ul>"},{"location":"installation/","title":"Installation","text":"<p>Requirements:</p> <ul> <li>Windows 8 or later</li> <li>Linux Ubuntu 20.04+ / Mint 20+ / Fedora 32+ and many other</li> <li>macOS 11+ (Big Sur or later)</li> </ul>"},{"location":"installation/#windows","title":"Windows","text":"<ol> <li>Download the installer <code>Artemis-Windows-x86_64-4.x.x.exe</code> in the Assets menu from the  LATEST RELEASE and follow the guided procedure to complete the installation process.</li> </ol>"},{"location":"installation/#linux","title":"Linux","text":"<ol> <li>Download <code>Artemis-Linux-x86_64-4.x.x.tar</code> in the Assets menu from the  LATEST RELEASE and extract the tarball archive in a folder of your choice and run the executable <code>app.bin</code>.</li> </ol>"},{"location":"installation/#create-a-shortcut","title":"Create a Shortcut","text":"<ol> <li> <p>To create a direct shortcut (in the main menu) launch the bash script in the terminal with the command:</p> <pre><code>. create_shortcut.sh\n</code></pre> </li> </ol> <p>This script will:</p> <ul> <li>Set the correct read/write privileges of the Artemis folder</li> <li>Create the artemis.desktop file (shortcut) in /home/$USER/.local/share/applications</li> <li>Move the Artemis icon file to /usr/share/icons</li> </ul>"},{"location":"installation/#mac-os","title":"Mac OS","text":"<p>Warning</p> <p>The macOS support is temporarily limited!</p> <p>The support for the macOS compiled version of the program is temporarily limited due to a lack of machines for extensive testing. To use Artemis on a macOS device, you have the following options:</p> <ul> <li>Run the program directly from the source: Follow the instructions provided in this chapter to launch the program from the source code.</li> <li>Compile the Artemis 4 binaries on your machine: In this case, you can contribute by reporting any issues you encounter by opening an Issue.</li> <li>Use the last available compiled version (3.2.1): Although this version is no longer officially supported, it remains available for use:  Artemis-3.2.1.dmg.</li> </ul>"},{"location":"run_from_source/","title":"Run from source code","text":"<p>Running Artemis directly from the source code using the Python interpreter is considered the most reliable and least problematic method. This approach ensures maximum compatibility and reduces the likelihood of encountering runtime issues. However, it is also the less practical option, as it requires the use of the terminal for the execution.</p>"},{"location":"run_from_source/#requirements","title":"Requirements","text":"<ul> <li>Python (3.11 or higher)</li> </ul>"},{"location":"run_from_source/#procedure","title":"Procedure","text":"<ol> <li> <p>Download and install Python (3.11 or higher) from the official website. Be sure to select the flag <code>Add Python 3.x to PATH</code> during the first part of the installation.</p> </li> <li> <p>Download Artemis source code from the latest release in the GitHub repository.</p> </li> <li> <p>Extract the downloaded archive.</p> </li> <li> <p>Open the terminal in Artemis folder and install the required Python libraries with PIP:     <pre><code>pip install -r requirements.txt --user\n</code></pre></p> </li> <li> <p>Launch Artemis:     <pre><code>python app.py\n</code></pre></p> </li> </ol> <p>Note for Developers</p> <p>Whenever modifications are made to any .qml file or any assets (such as images, icons, etc.), it is essential to recompile the resource.py file to ensure that the changes are reflected in the application. To achieve this, execute the following command: <pre><code>pyside6-rcc ./artemis.qrc -o artemis/resources.py\n</code></pre></p>"},{"location":"run_from_source/#folders-structure","title":"Folders Structure","text":"<p>Artemis can be safely executed and/or installed in any folder (even protected ones, such as <code>Program Files (x86)</code> in Windows) because Artemis performs read-only operations in the <code>BASE_DIR</code> folder from where it runs. All the reading-writing operations (such as database ops, logging, etc.) are performed in standard folders as follow:</p>"},{"location":"run_from_source/#windows","title":"Windows","text":"<ul> <li>Data, Cache, Configurations: <code>$USER\\AppData\\Local\\AresValley\\Artemis</code></li> <li>Logs: <code>$USER\\AppData\\Local\\Temp</code></li> </ul>"},{"location":"run_from_source/#linux","title":"Linux","text":"<ul> <li>Data, Cache, Configurations: <code>~/.local/share/AresValley/Artemis</code></li> <li>Logs: <code>/tmp</code></li> </ul>"},{"location":"run_from_source/#mac-os","title":"Mac OS","text":"<ul> <li>Data, Cache, Configurations: <code>~/Library/Application Support/AresValley/Artemis</code></li> <li>Logs: <code>/tmp</code></li> </ul>"},{"location":"database/db_acf/","title":"ACF","text":"<p>The table contains 4 columns explained below.</p> <p>Example</p> <p>A technical explanation on how autocorrelation function works along with a practical example is reported HERE</p>"},{"location":"database/db_acf/#acf_id","title":"ACF_ID","text":"<p><code>INTEGER</code> </p> <p>This is a unique identification number for each entry that is assigned during the creation of a new ACF. It is auto-incrementing and is not replaced in the event of deletion.</p>"},{"location":"database/db_acf/#sig_id","title":"SIG_ID","text":"<p><code>INTEGER</code> </p> <p>This is a direct reference to the specific signal associated with the ACF. It links to the primary key of the Signals table that holds detailed information about the signals.</p>"},{"location":"database/db_acf/#value","title":"VALUE","text":"<p><code>FLOAT</code></p> <p>The autocorrelation time expressed in ms.</p>"},{"location":"database/db_acf/#description","title":"DESCRIPTION","text":"<p><code>TEXT</code></p> <p>The short description is used to explain the details about the autocorrelation value, e.g. <code>Frame</code>, <code>Superframe</code>, etc.</p>"},{"location":"database/db_bandwidth/","title":"Bandwidth","text":"<p>The table contains 4 columns explained below.</p>"},{"location":"database/db_bandwidth/#band_id","title":"BAND_ID","text":"<p><code>INTEGER</code> </p> <p>This is a unique identification number for each entry that is assigned during the creation of a new bandwidth. It is auto-incrementing and is not replaced in the event of deletion.</p>"},{"location":"database/db_bandwidth/#sig_id","title":"SIG_ID","text":"<p><code>INTEGER</code> </p> <p>This is a direct reference to the specific signal associated with the bandwidth. It links to the primary key of the Signals table that holds detailed information about the signals.</p>"},{"location":"database/db_bandwidth/#value","title":"VALUE","text":"<p><code>INTEGER</code></p> <p>The bandwidth in Hz expressed as an integer.</p>"},{"location":"database/db_bandwidth/#description","title":"DESCRIPTION","text":"<p><code>TEXT</code></p> <p>The short description is used to explain the purpose of the bandwidth and any other useful details.</p>"},{"location":"database/db_cat_label/","title":"Category Label","text":"<p>This table contains only the name of the category/tag. The table contains 2 columns explained below.</p>"},{"location":"database/db_cat_label/#clb_id","title":"CLB_ID","text":"<p><code>INTEGER</code> </p> <p>This is a unique identification number for each entry that is assigned during the creation of a new category tag. It is auto-incrementing and is not replaced in the event of deletion.</p>"},{"location":"database/db_cat_label/#value","title":"VALUE","text":"<p><code>TEXT</code></p> <p>The name of the category/tag expressed as a string.</p>"},{"location":"database/db_category/","title":"Category","text":"<p>The primary function of this table is to facilitate the classification of the signal by assigning it to its appropriate family or category. Can be used with any tag. The table contains 3 columns explained below.</p>"},{"location":"database/db_category/#cat_id","title":"CAT_ID","text":"<p><code>INTEGER</code> </p> <p>This is a unique identification number for each entry that is assigned during the creation of a new category/tag. It is auto-incrementing and is not replaced in the event of deletion.</p>"},{"location":"database/db_category/#sig_id","title":"SIG_ID","text":"<p><code>INTEGER</code> </p> <p>This is a direct reference to the specific signal associated with the category. It links to the primary key of the Signals table that holds detailed information about the signals.</p>"},{"location":"database/db_category/#clb_id","title":"CLB_ID","text":"<p><code>INTEGER</code> </p> <p>This is a direct reference to the specific category label associated with the category. It links to the primary key of the Category Label table that holds the name of the category.</p>"},{"location":"database/db_frequency/","title":"Frequency","text":"<p>The table contains 4 columns explained below.</p>"},{"location":"database/db_frequency/#freq_id","title":"FREQ_ID","text":"<p><code>INTEGER</code> </p> <p>This is a unique identification number for each entry that is assigned during the creation of a new frequency. It is auto-incrementing and is not replaced in the event of deletion.</p>"},{"location":"database/db_frequency/#sig_id","title":"SIG_ID","text":"<p><code>INTEGER</code> </p> <p>This is a direct reference to the specific signal associated with the frequency. It links to the primary key of the Signals table that holds detailed information about the signals.</p>"},{"location":"database/db_frequency/#value","title":"VALUE","text":"<p><code>INTEGER</code></p> <p>The freqeuncy in Hz expressed as an integer.</p>"},{"location":"database/db_frequency/#description","title":"DESCRIPTION","text":"<p><code>TEXT</code></p> <p>The short description is used to explain the purpose of the bandwidth and any other useful details.</p>"},{"location":"database/db_info/","title":"Info","text":"<p>This is the database meta table and contains 4 columns explained below.</p>"},{"location":"database/db_info/#name","title":"NAME","text":"<p><code>TEXT</code></p> <p>This is the name of the database.</p>"},{"location":"database/db_info/#data","title":"DATA","text":"<p><code>TEXT</code></p> <p>The creation date when the database has been initialised.</p>"},{"location":"database/db_info/#version","title":"VERSION","text":"<p><code>INTEGER</code></p> <p>A simple integer to denote the database version.</p>"},{"location":"database/db_info/#editable","title":"EDITABLE","text":"<p><code>INTEGER</code></p> <p>This field should serve as a writing protection on the database.</p> <ul> <li>0: read-only database</li> <li>1: database can be edited with no restrictions</li> </ul> <p>Experimental</p> <p>This feature is experimental and not yet implemented.</p>"},{"location":"database/db_location/","title":"Location","text":"<p>This is the location where the signal is distributed/received. Avoid the usage of the precise location of the TX station or very small town (very rare). It's a good habit to use nations/continents or special location (like <code>Worldwide</code>). The table contains 4 columns explained below.</p>"},{"location":"database/db_location/#loc_id","title":"LOC_ID","text":"<p><code>INTEGER</code> </p> <p>This is a unique identification number for each entry that is assigned during the creation of a new location. It is auto-incrementing and is not replaced in the event of deletion.</p>"},{"location":"database/db_location/#sig_id","title":"SIG_ID","text":"<p><code>INTEGER</code> </p> <p>This is a direct reference to the specific signal associated with the location. It links to the primary key of the Signals table that holds detailed information about the signals.</p>"},{"location":"database/db_location/#value","title":"VALUE","text":"<p><code>TEXT</code></p> <p>The location expressed as a string.</p>"},{"location":"database/db_location/#description","title":"DESCRIPTION","text":"<p><code>TEXT</code></p> <p>The short description is used to explain further details about the location.</p>"},{"location":"database/db_mode/","title":"Mode","text":"<p>This field reports the way how a signals has been decoded during the reception. The table contains 4 columns explained below.</p>"},{"location":"database/db_mode/#mod_id","title":"MOD_ID","text":"<p><code>INTEGER</code> </p> <p>This is a unique identification number for each entry that is assigned during the creation of a new mode. It is auto-incrementing and is not replaced in the event of deletion.</p>"},{"location":"database/db_mode/#sig_id","title":"SIG_ID","text":"<p><code>INTEGER</code> </p> <p>This is a direct reference to the specific signal associated with the modulation. It links to the primary key of the Signals table that holds detailed information about the signals.</p>"},{"location":"database/db_mode/#value","title":"VALUE","text":"<p><code>TEXT</code></p> <p>The mode expressed as a string.</p>"},{"location":"database/db_mode/#description","title":"DESCRIPTION","text":"<p><code>TEXT</code></p> <p>The short description is used to explain the purpose of the mode and any other useful details.</p>"},{"location":"database/db_modulation/","title":"Modulation","text":"<p>Modulation refers to the method by which information is encoded into the main signal (carrier). This process involves altering various properties of the carrier signal, such as amplitude, frequency, or phase. Multiple modulation techniques can be employed, and a TX station has the capability to utilize different modulation schemes. The table contains 4 columns explained below.</p>"},{"location":"database/db_modulation/#mdl_id","title":"MDL_ID","text":"<p><code>INTEGER</code> </p> <p>This is a unique identification number for each entry that is assigned during the creation of a new modulation. It is auto-incrementing and is not replaced in the event of deletion.</p>"},{"location":"database/db_modulation/#sig_id","title":"SIG_ID","text":"<p><code>INTEGER</code> </p> <p>This is a direct reference to the specific signal associated with the modulation. It links to the primary key of the Signals table that holds detailed information about the signals.</p>"},{"location":"database/db_modulation/#value","title":"VALUE","text":"<p><code>TEXT</code></p> <p>The modulation expressed as a string.</p>"},{"location":"database/db_modulation/#description","title":"DESCRIPTION","text":"<p><code>TEXT</code></p> <p>The short description is used to explain the purpose of the modulation and any other useful details.</p>"},{"location":"database/db_overview/","title":"Database","text":"<p>With the release of Artemis 4, we have made a significant upgrade in our data management system by transitioning from a CSV file to a full relational SQL database. This change brings a multitude of advantages that enhance the efficiency, scalability, and reliability of our system. In the following sections, we will explore, table by table, the structure of the new database.</p> <p></p>"},{"location":"database/db_signals/","title":"Signals","text":"<p>This is the main table and contains 4 columns explained below.</p>"},{"location":"database/db_signals/#sig_id","title":"SIG_ID","text":"<p><code>INTEGER</code> </p> <p>This is a unique identification number for each entry that is assigned during the creation of a signal. It is auto-incrementing and is not replaced in the event of signal deletion.</p>"},{"location":"database/db_signals/#name","title":"NAME","text":"<p><code>TEXT</code></p> <p>The name of the signal. A simple string that describes in short the analyzed signal. Special characters are allowed.</p>"},{"location":"database/db_signals/#description","title":"DESCRIPTION","text":"<p><code>TEXT</code></p> <p>The short description is used to explain the purpose of the signal and some other useful details.</p> <p>Tip</p> <p>The DESCRIPTION field supports Markdown, a simple markup language for creating rich text using plain text. Headers, emphasis, lists, links, code blocks and many more features for advanced text formtting. Markdown Basic Syntax </p>"},{"location":"database/db_signals/#url","title":"URL","text":"<p><code>TEXT</code></p> <p>The sigidwiki (SigID) URL of the selected signal. This is a direct connection to the online database where further details of the signal are collected.</p> <p>Info</p> <p>Internal Use Only This field is for the SigID database and not intended for user viewing or editing. Personal URLs can be stored in the signal description.</p>"},{"location":"database/sigid/","title":"SigID Wiki Database","text":"<p>Artemis serves as a valuable resource for both personal signal collection and leveraging a vast repository of pre-identified signals. This software application allows users to curate their own collections, but its true strength lies in its integration with a comprehensive database of known signals. This database is directly sourced from the Signal Identification Wiki, an open-source resource collaboratively maintained by a global community of radio enthusiasts.</p> <p>Database Revision</p> <p>For quality control purposes, the database undergoes a rigorous review process before integration into Artemis. This review adheres to established guidelines, ensuring the accuracy and completeness of the information presented to users. The specifics of this review process are outlined in the following section.</p>"},{"location":"database/sigid/#modulation","title":"Modulation","text":"<p>A good practise (reported also on ) is to write the primary type of modulation (if known) and not all the possible variants. A practical example is reported on Signal Identification Wiki: there is no need to write 8-PSK or QPSK, PSK is enough. The Artemis SigID database is provided without any modulation variants included. The recognized modulations are listed below:</p>"},{"location":"database/sigid/#analog","title":"Analog","text":"<ul> <li>AM: Amplitude Modulation</li> <li>FM: Frequency Modulation</li> <li>PM: Phase Modulation</li> <li>LSB: Lower Sideband</li> <li>USB: Upper Sideband</li> <li>VSB: Vestigial Sideband</li> <li>CW: Continuous Wave</li> </ul>"},{"location":"database/sigid/#digital","title":"Digital","text":"<ul> <li>QAM: Quadrature Amplitude Modulation</li> <li>PSK: Phase-Shift Keying</li> <li>FSK: Frequency-Shift Keying</li> <li>ASK: Amplitude-Shift Keying</li> <li>MSK: Minimum-Shift Keying</li> <li>IFK: Incremental Frequency Keying</li> <li>OOK: On-Off Keying</li> <li>FDM: Frequency-Division Multiplexing</li> <li>BOC: Binary Offset Carrier Modulation</li> <li>CDMA: Code Division Multiple Access</li> <li>TDMA: Time Division Multiple Access</li> <li>FBMC: Filter Bank Multi Carrier</li> <li>UFMC: Universal Filtered Multi Carrier</li> <li>PCM: Pulse Code Modulation</li> <li>PPM: Pulse Position Modulation</li> <li>FMCW: Frequency-Modulated Continuous Wave</li> <li>Pulse: Pulse</li> </ul>"},{"location":"database/sigid/#spread-spectrum","title":"Spread Spectrum","text":"<ul> <li>CSS: Chirp Spread Spectrum</li> <li>DSSS: Direct Sequence Spread Spectrum</li> <li>FHSS: Frequency Hopping Spread Spectrum</li> <li>THSS: Time Hopping Spread Spectrum</li> </ul>"},{"location":"database/sigid/#locations","title":"Locations","text":"<p>Locations are either countries or special token (<code>Worldwide</code>, <code>Europe</code>, etc.) . Precise location of the TX station, towns and cities are converted to their respective countries.</p>"},{"location":"space_weather/aurora/","title":"Aurora","text":"<p>This short-term aurora forecast predicts its location and intensity over the next 30 to 90 minutes, based on the OVATION model. The lead time of the forecast corresponds to the duration it takes for the solar wind to travel from the L1 observation point to Earth.</p> <p>Auroras indicate current geomagnetic storm conditions and provide situational awareness for various technologies: for example, they directly affect HF radio communication and GPS/GNSS satellite navigation and are related to ground-induced currents impacting electric power transmission.</p> <p>For many people, the aurora is a beautiful nighttime phenomenon that is worth traveling to arctic regions just to observe.  It is the only way for most people to actually experience space weather.</p>"},{"location":"space_weather/current/","title":"Current","text":""},{"location":"space_weather/current/#1-kp-index","title":"1. Kp Index","text":"<p>The K index is a number (from 0 to 9) that shows how much Earth's magnetic field is disturbed. A K index of 1 means things are calm, while a K index of 5 or higher indicates a geomagnetic storm. These disturbances are measured with magnetometers that track changes in Earth's magnetic field every three hours. The K itself comes from a German word \"Kennziffer\" meaning \"characteristic digit\". To get a big picture of what's happening around the world, an official planetary Kp index is calculated. This is done by averaging the K indices from a special network of 13 geomagnetic observatories located around the globe at mid-latitudes.</p>"},{"location":"space_weather/current/#2-a-index","title":"2. A Index","text":"<p>The A index represents the three-hourly equivalent amplitude of geomagnetic activity at a specific magnetometer station, derived from the station-specific K index. Due to the quasi-logarithmic nature of the K-scale in relation to magnetometer fluctuations, directly averaging a set of K indices is not really meaningful. Instead each K is converted back into a linear scale. The Ap index is determined by averaging the eight daily A values, providing a measure of geomagnetic activity for a specific day. Days with higher levels of geomagnetic activity correspond to higher daily Ap values.</p>"},{"location":"space_weather/current/#3-noaa-space-weather-scale","title":"3. NOAA Space Weather Scale","text":""},{"location":"space_weather/current/#geomagnetic-storm","title":"Geomagnetic Storm","text":"G5 (Extreme) <ul> <li>Physical measure: Kp = 9</li> <li>Average Frequency: 4 days per cycle (11 years)</li> </ul> <p>Power systems: Widespread voltage control problems and protective system problems can occur, some grid systems may experience complete collapse or blackouts. Transformers may experience damage.</p> <p>Spacecraft operations: May experience extensive surface charging, problems with orientation, uplink/downlink and tracking satellites.</p> <p>Other systems: Pipeline currents can reach hundreds of amps, HF (high frequency) radio propagation may be impossible in many areas for one to two days, satellite navigation may be degraded for days, low-frequency radio navigation can be out for hours, and aurora has been seen as low as Florida and southern Texas (typically 40\u00b0 geomagnetic lat.).</p> G4 (Severe) <ul> <li>Physical measure: Kp = 8 to 9-</li> <li>Average Frequency: 60 days per cycle (11 years)</li> </ul> <p>Power systems: Possible widespread voltage control problems and some protective systems will mistakenly trip out key assets from the grid.</p> <p>Spacecraft operations: May experience surface charging and tracking problems, corrections may be needed for orientation problems.</p> <p>Other systems: Induced pipeline currents affect preventive measures, HF radio propagation sporadic, satellite navigation degraded for hours, low-frequency radio navigation disrupted, and aurora has been seen as low as Alabama and northern California (typically 45\u00b0 geomagnetic lat.).</p> G3 (Strong) <ul> <li>Physical measure: Kp = 7</li> <li>Average Frequency: 130 days per cycle (11 years)</li> </ul> <p>Power systems: Voltage corrections may be required, false alarms triggered on some protection devices.</p> <p>Spacecraft operations: Surface charging may occur on satellite components, drag may increase on low-Earth-orbit satellites, and corrections may be needed for orientation problems.</p> <p>Other systems: Intermittent satellite navigation and low-frequency radio navigation problems may occur, HF radio may be intermittent, and aurora has been seen as low as Illinois and Oregon (typically 50\u00b0 geomagnetic lat.).</p> G2 (Moderate) <ul> <li>Physical measure: Kp = 6</li> <li>Average Frequency: 360 days per cycle (11 years)</li> </ul> <p>Power systems: High-latitude power systems may experience voltage alarms, long-duration storms may cause transformer damage.</p> <p>Spacecraft operations: Corrective actions to orientation may be required by ground control; possible changes in drag affect orbit predictions.</p> <p>Other systems: HF radio propagation can fade at higher latitudes, and aurora has been seen as low as New York and Idaho (typically 55\u00b0 geomagnetic lat.).</p> G1 (Minor) <ul> <li>Physical measure: Kp = 5</li> <li>Average Frequency: 900 days per cycle (11 years)</li> </ul> <p>Power systems: Weak power grid fluctuations can occur.</p> <p>Spacecraft operations: Minor impact on satellite operations possible.</p> <p>Other systems: Migratory animals are affected at this and higher levels; aurora is commonly visible at high latitudes (northern Michigan and Maine).</p>"},{"location":"space_weather/current/#solar-radiation-storms","title":"Solar Radiation Storms","text":"S5 (Extreme) <ul> <li>Physical measure: Flux level of \\(\\ge 10 MeV\\) particles = \\(10^5\\)</li> <li>Average Frequency: &lt; 1 event per cycle (11 years)</li> </ul> <p>Biological: Unavoidable high radiation hazard to astronauts on EVA (extra-vehicular activity); passengers and crew in high-flying aircraft at high latitudes may be exposed to radiation risk.</p> <p>Satellite operations: Satellites may be rendered useless, memory impacts can cause loss of control, may cause serious noise in image data, star-trackers may be unable to locate sources; permanent damage to solar panels possible.</p> <p>Other systems: Complete blackout of HF (high frequency) communications possible through the polar regions, and position errors make navigation operations extremely difficult.</p> S4 (Severe) <ul> <li>Physical measure: Flux level of \\(\\ge 10 MeV\\) particles = \\(10^4\\)</li> <li>Average Frequency: 3 events per cycle (11 years)</li> </ul> <p>Biological: Unavoidable radiation hazard to astronauts on EVA; passengers and crew in high-flying aircraft at high latitudes may be exposed to radiation risk.</p> <p>Satellite operations: May experience memory device problems and noise on imaging systems; star-tracker problems may cause orientation problems, and solar panel efficiency can be degraded.</p> <p>Other systems: Blackout of HF radio communications through the polar regions and increased navigation errors over several days are likely.</p> S3 (Strong) <ul> <li>Physical measure: Flux level of \\(\\ge 10 MeV\\) particles = \\(10^3\\)</li> <li>Average Frequency: 10 events per cycle (11 years)</li> </ul> <p>Biological: Radiation hazard avoidance recommended for astronauts on EVA; passengers and crew in high-flying aircraft at high latitudes may be exposed to radiation risk.</p> <p>Satellite operations: Single-event upsets, noise in imaging systems, and slight reduction of efficiency in solar panel are likely.</p> <p>Other systems: Degraded HF radio propagation through the polar regions and navigation position errors likely.</p> S2 (Moderate) <ul> <li>Physical measure: Flux level of \\(\\ge 10 MeV\\) particles = \\(10^2\\)</li> <li>Average Frequency: 25 events per cycle (11 years)</li> </ul> <p>Biological: Passengers and crew in high-flying aircraft at high latitudes may be exposed to elevated radiation risk.</p> <p>Satellite operations: Infrequent single-event upsets possible.</p> <p>Other systems: Small effects on HF propagation through the polar regions and navigation at polar cap locations possibly affected.</p> S1 (Minor) <ul> <li>Physical measure: Flux level of \\(\\ge 10 MeV\\) particles = \\(10\\)</li> <li>Average Frequency: 50 events per cycle (11 years)</li> </ul> <p>Biological: None.</p> <p>Satellite operations: None.</p> <p>Other systems: Minor impacts on HF radio in the polar regions.</p>"},{"location":"space_weather/current/#radio-blackouts","title":"Radio Blackouts","text":"R5 (Extreme) <ul> <li>Physical measure:* X20 (\\(2e^{-3} Wm^{-2}\\))</li> <li>Average Frequency: &lt; 1 days per cycle (11 years)</li> </ul> <p>HF Radio: Complete HF (high frequency**) radio blackout on the entire sunlit side of the Earth lasting for a number of hours. This results in no HF radio contact with mariners and en route aviators in this sector.</p> <p>Navigation: Low-frequency navigation signals used by maritime and general aviation systems experience outages on the sunlit side of the Earth for many hours, causing loss in positioning. Increased satellite navigation errors in positioning for several hours on the sunlit side of Earth, which may spread into the night side. </p> <p>*GOES X-ray peak brightness by class and by flux (measured in the 0.1-0.8 nm range, in W\u00b7m-2)</p> R4 (Severe) <ul> <li>Physical measure:* X10 (\\(10^{-3} Wm^{-2}\\))</li> <li>Average Frequency: 8 days per cycle (11 years)</li> </ul> <p>HF Radio: HF radio communication blackout on most of the sunlit side of Earth for one to two hours. HF radio contact lost during this time.</p> <p>Navigation: Outages of low-frequency navigation signals cause increased error in positioning for one to two hours. Minor disruptions of satellite navigation possible on the sunlit side of Earth.</p> <p>*GOES X-ray peak brightness by class and by flux (measured in the 0.1-0.8 nm range, in W\u00b7m-2)</p> R3 (Strong) <ul> <li>Physical measure:* X1 (\\(10^{-4} Wm^{-2}\\))</li> <li>Average Frequency: 140 days per cycle (11 years)</li> </ul> <p>HF Radio: Wide area blackout of HF radio communication, loss of radio contact for about an hour on sunlit side of Earth.</p> <p>Navigation: Low-frequency navigation signals degraded for about an hour. </p> <p>*GOES X-ray peak brightness by class and by flux (measured in the 0.1-0.8 nm range, in W\u00b7m-2)</p> R2 (Moderate) <ul> <li>Physical measure:* M5 (\\(5e^{-5} Wm^{-2}\\))</li> <li>Average Frequency: 300 days per cycle (11 years)</li> </ul> <p>HF Radio: Limited blackout of HF radio communication on sunlit side of the Earth, loss of radio contact for tens of minutes.</p> <p>Navigation: Degradation of low-frequency navigation signals for tens of minutes. </p> <p>*GOES X-ray peak brightness by class and by flux (measured in the 0.1-0.8 nm range, in W\u00b7m-2)</p> R1 (Minor) <ul> <li>Physical measure:* M1 (\\(10^{-5} Wm^{-2}\\))</li> <li>Average Frequency: 950 days per cycle (11 years)</li> </ul> <p>HF Radio: Weak or minor degradation of HF radio communication on sunlit side of the Earth, occasional loss of radio contact.</p> <p>Navigation: Low-frequency navigation signals degraded for brief intervals. </p> <p>*GOES X-ray peak brightness by class and by flux (measured in the 0.1-0.8 nm range, in W\u00b7m-2)</p>"},{"location":"space_weather/current/#4-x-ray-solar-activity","title":"4. X-Ray Solar Activity","text":"<p>This is a summary of the X-Ray Flare Class. Large solar X-ray flares can change the Earth\u2019s ionosphere, which blocks high-frequency (HF) radio transmissions on the sunlit side of the Earth. Solar flares are also associated with Coronal Mass Ejections (CMEs) which can ultimately lead to geomagnetic storms. SWPC sends out space weather alerts at the M5 level. Some large flares are accompanied by strong radio bursts that may interfere with other radio frequencies and cause problems for satellite communication and radio navigation (GPS).</p> Class Peak Strength (W/m<sup>2</sup>) Effects on Earth B I &lt; 10<sup>-6</sup> Too small to harm Earth C 10<sup>-6</sup> \u2264 I &lt; 10<sup>-5</sup> Small with few noticeable consequences M 10<sup>-5</sup> \u2264 I &lt; 10<sup>-4</sup> Brief radio blackouts in polar regions, minor radiation storms X I \u2265 10<sup>-4</sup> Planet-wide radio blackouts, long-lasting radiation storms"},{"location":"space_weather/current/#5-rf-propagation","title":"5. RF Propagation","text":""},{"location":"space_weather/current/#maximum-usable-frequency","title":"Maximum Usable Frequency","text":"<p>In radio transmission, the maximum usable frequency (MUF) is the highest frequency that can be effectively used for communication between two locations on Earth by reflecting off the ionosphere (via skywave or skip) at a given time, regardless of the transmitter's power. This measurement is particularly valuable for shortwave transmissions.</p>"},{"location":"space_weather/current/#earth-moon-earth","title":"Earth-Moon-Earth","text":"<p>Earth\u2013Moon\u2013Earth communication (EME), commonly referred to as Moon bounce, is a radio communication method in which radio waves are transmitted from an Earth-based station, reflected off the Moon's surface, and then received back on Earth. The value gives the probability of a succesfull connection.</p>"},{"location":"space_weather/current/#meteor-scatter","title":"Meteor Scatter","text":"<p>Meteor burst communications (MBC), also known as meteor scatter (MS) communications, is a radio propagation technique that uses the ionized trails created by meteors entering the atmosphere to establish brief communication links between radio stations up to 2,250 kilometers (1,400 miles) apart. This can involve either forward-scatter or back-scatter of the radio waves. Like EME, the value gives the probability of a succesfull connection.</p>"},{"location":"space_weather/current/#sporadic-e","title":"Sporadic-E","text":"<p>Report of the latest E-skip spots on 50, 70 &amp; 144 MHz by DXrobot</p> <p>Sporadic E (Es or SpE) is a rare type of radio propagation that uses a lower part of the Earth's ionosphere, which typically doesn't refract radio waves. It reflects signals off small \"clouds\" in the E region at altitudes of 95-150 km (50-100 miles). Unlike the regular F region skywave propagation, which depends on daily cycles of ionized layers from UV light, Sporadic E uses transient ionized patches. This allows for occasional long-distance VHF communication, usually during the six weeks around the summer solstice, beyond the normal line-of-sight range.</p>"},{"location":"space_weather/current/#aurora-spots","title":"Aurora Spots","text":"<p>Report of the latest aurora spots on 50, 70 &amp; 144 MHz by DXrobot</p> <p>Auroral propagation, or auroral backscatter, is a form of radio propagation that occurs during an auroral event, affecting VHF and UHF communications. Increased ionization in the E layer of the ionosphere reflects signals at much higher frequencies than usual, enabling communication up to 1000 MHz, though 500 MHz is more common. Signals are directed towards the auroral region and reflected back, but they are often distorted due to particle movement (the signal is roughly Doppler shifted of 1 kHz at around 150 MHz as the electrons stream down).</p>"},{"location":"space_weather/current/#expected-hf-noise","title":"Expected HF Noise","text":"<p>This is just the expected noise in HF based on the current Space Weather conditions.</p>"},{"location":"space_weather/current/#6-report-age","title":"6. Report Age","text":"<p>Poseidon Daemon is in charge of parse all the necessary data used for the Space Weather module. The data of the last generated report is written here.</p>"},{"location":"space_weather/drap/","title":"DRAP","text":"<p>The D-Region Absorption Product (DRAP) evaluates the effects of solar X-ray flux and solar energetic particle (SEP) events on HF radio communication. Long-distance communications using high frequency (HF) radio waves (3 - 30 MHz) rely on signal reflection in the ionosphere. Typically, radio waves reflect near the peak of the F2 layer (~300 km altitude), but during their journey to and from this peak, the signals experience attenuation due to absorption by the intervening ionosphere.</p> <p>The D-Region Absorption Prediction model provides guidance to understand the degradation and blackouts of HF radio communications that can result from these conditions.</p>"},{"location":"space_weather/forecasts/","title":"Forecasts","text":""},{"location":"space_weather/forecasts/#1-forecast-summary","title":"1. Forecast Summary","text":"<p>Geomagnetic activity, Solar Radiation Storms and Radio Blackouts probable events (in the next 3 days) are described in this section. </p>"},{"location":"space_weather/forecasts/#2-3-day-kp-index","title":"2. 3-Day Kp Index","text":"<p>This is a 3 day projection of the Kp index.</p>"},{"location":"space_weather/forecasts/#3-events-probability","title":"3. Events Probability","text":"<p>The probability (in percentage) of different events that can take place and generate some important conditions for RF propagation. All the event are explained here.</p> <p>Info</p> <p>Geomagnetic Activity has two percentual value per day: the left one refers to high-latitude location and the right one is for middle-latitude locations.</p>"}]}
\ No newline at end of file
+{"config":{"lang":["en"],"separator":"[\\s\\-]+","pipeline":["stopWordFilter"]},"docs":[{"location":"","title":"Documentation","text":"<p>Artemis is a software designed to assist radio frequency (RF) signal identification and storage. It simplifies real-time spectrum analysis by leveraging one of the most extensive and community-driven databases, containing nearly 500 recognized signals. This comprehensive software solution allows users to collect RF signals with specific parameters such as frequency, bandwidth, modulation, etc. Users can also store spectrum waterfalls, audio samples, and all types of documents for future reference. Artemis provides a robust platform to manage a wide range of RF data with precision and ease.</p>"},{"location":"acf_analysis/","title":"Autocorrelation Function (ACF)","text":""},{"location":"acf_analysis/#theoretical-introduction","title":"Theoretical Introduction","text":"<p>Correlation functions are valuable mathematical tools utilized across various scientific disciplines, including engineering, physics, and chemistry. The cross-correlation function, commonly defined as a sliding inner (dot) product, quantifies the similarity between two signals as a function of a temporal shift applied to one of them:</p> \\[ \\left[ k*l \\right]\\equiv \\int_{-\\infty}^{+\\infty}k^{*}(t)l(t+\\tau)dt \\] <p>where \\(k\\) and \\(l\\) are two general non-discrete functions without discontinuity, \\(k^{*}\\) is the complex conjugate of \\(k\\) and \\(\\tau\\) is the lag (time delay for signal analysis). This representation is closely related to the convolution theorem by the following relationship:</p> \\[ k(t)*l(t)\\equiv k^{*}(-t)*l(t) \\] <p>In our case, the signal must be compared with itself to identify periodic patterns or detect anomalous high degrees of similarity within a given time interval. To achieve this objective, we can employ the Autocorrelation Function (ACF), which is essentially the cross-correlation of a signal with itself, where \\(k(t)=l(t)\\). The following equation defines the ACF, derived from a straightforward modification of the initial equation:</p> \\[ \\left[ k*k \\right](\\tau)\\equiv \\int_{-\\infty}^{+\\infty}k^{*}(t)k(t+\\tau)dt \\] <p>Within a discrete data set composed by \\(Y(t)\\) records we can easily calculate autocorrelation from:</p> \\[ \\rho_{\\tau}=\\frac{\\sum_{i=1}^{N-\\tau}(Y_i-\\bar{Y})(Y_{i+\\tau}-\\bar{Y})}{\\sum_{i=1}^{N}(Y_i-\\bar{Y})^2} \\] <p>where \\(Y_{i+\u03c4}\\) is a lagged data by \\(\u03c4\\) of \\(Y_i\\) and \\(\\bar{Y}\\) is the average value of the original data set. Entire denominator is used to keep the normalization condition, indeed \u03c1\u03c4 can assume a value between -1 (exact anticorrelation) and +1 (exact correlation). A complete correlation can be only achieved with a perfect overlap of the analyzed function with it self; the simple way to verify that is when \\(\u03c4=0\\)</p> <p></p>"},{"location":"acf_analysis/#example-acf-analysis","title":"Example: ACF Analysis","text":""},{"location":"acf_analysis/#stanag-4285","title":"STANAG 4285","text":"<p>The first example will be a NATO standard known as STANAG 4285. You can download a .wav sample from HERE. We start to collect some information about the structure of this signal: a good starting point is the official declassified NATO document dated 1989. The main frame structure can be found at Annex A-3/5 with a graphical view at Annex A-7, also reported below:</p> <ul> <li>STANAG 4285 (i)</li> <li>STANAG 4285 A-3</li> <li>STANAG 4285 A-4</li> <li>STANAG 4285 A-5</li> <li>STANAG 4285 A-7</li> </ul> <p>Summary</p> <ul> <li>1 x 80 bits of synchronization pattern</li> <li>4 x 32 bits of data</li> <li>3 x 16 bits of reference</li> </ul> <p>Therefore, a full sequence will be composed as the sum of all symbols reported above: 256 symbols recursively transmitted at the ratio of 2400 bauds means a redundancy of 106.66 ms. To analyze an unknown signal I strongly recommend Signal Analyzer (SA). SA is actually one of the most valuable and priceless software available by Sergey Makarov (\u041c\u0430\u043a\u0430\u0440\u043e\u0432 \u0421\u0435\u0440\u0433\u0435\u0439 \u041c\u0438\u0445\u0430\u0439\u043b\u043e\u0432\u0438\u0447, sadly passed away on 29 May 2012) and it used to perform several tests on data sample coded as .wav or .mp3 file. The signal waterfall is reported below:</p> <p></p> <p>When an Autocorrelation function is applied on selected data frame (see above), the result shows a clear recursive pattern with a gap of 106.244 ms between every peak as expected. An ACF refinement can be done into WaveForm windows where we can also notice an identical structure as reported by the specifications</p> <p> </p> <p>Summary</p> <ol> <li>Synchronization pattern is composed by \\(2400*33.013E-3=79.2\\simeq 80\\) symbols</li> <li>Data group contain \\(2400*13.348E-3=32.0=32\\) symbols</li> <li>Reference sequence is formed by \\(2400*6.674E-3=16.02\\simeq 16\\) symbols</li> </ol>"},{"location":"basic_operations/","title":"Basic Operations","text":""},{"location":"basic_operations/#1-main-menu","title":"1. Main Menu","text":""},{"location":"basic_operations/#file","title":"File","text":"<ul> <li>New Database: Create a new database.</li> <li>Load Database: Open the Database Manager windows in order to open, rename, or delete a database.</li> <li>Import Database: Import an Artemis database with a standard .tar format.</li> <li>Export Database: Export the loaded database with a standard .tar format.</li> <li>Edit Tags: Open the tags editor window. From here, you can add, rename, or delete tags. The tags can be added to a signal from the tags menu</li> <li>Open Database Folder: Shows the folder of the currently loaded database in the explorer.</li> <li>Preferences: Open the program settings window.</li> <li>Exit: This will close the application.</li> </ul>"},{"location":"basic_operations/#signal","title":"Signal","text":"<ul> <li>New: Add a new signal to the database.</li> <li>Edit: Edit the current/selected signal from the loaded database.</li> </ul>"},{"location":"basic_operations/#space-weather","title":"Space Weather","text":"<ul> <li>Check Report: Open the main Space Weather window and retrieve all the live data from Poseidon Crawler.</li> </ul>"},{"location":"basic_operations/#2-signal-list","title":"2. Signal List","text":"<p>This is the signal list where all the database entries are shown. When a signal is selected, it will load on the right panel.</p>"},{"location":"basic_operations/#filter-by-namedescription","title":"Filter by Name/Description","text":"<p>On top of the list, there is a field for filtering signals by name or any keyword inside the description of the signal: this filter has the highest priority among all the filters.</p>"},{"location":"basic_operations/#3-signal-menu","title":"3. Signal Menu","text":"<p>Here you can swithc between the main signal window and the filter page.</p>"},{"location":"basic_operations/#4-tags","title":"4. Tags","text":"<ul> <li>Associate Tag: Custom tags can be associated to the selected signal with the  icon</li> <li>Remove Tag: In order to remove a tag, just click on its badge. </li> <li>Add/Rename Tag: To add a new tag open the Tags Editor in the main menu.</li> </ul>"},{"location":"basic_operations/#5-add-parameter","title":"5. Add Parameter","text":"<p>Click on the labels to add the corresponding parameter to the signal (e.g. click on Frequency to add a new frequency).</p>"},{"location":"basic_operations/#6-edit-parameter","title":"6. Edit Parameter","text":"<p>Click on the parameter badge to open the Signal Editor windows. From here, you can edit or delete the corresponding parameter.</p> <p>Parameter Description</p> <p>All the parameters have a description field: if some text is added, it will appear when the corresponding parameter badge is hovered with the mouse pointer.</p>"},{"location":"basic_operations/#7-description","title":"7. Description","text":"<p>This is the description of the signal and can be edited from the Main Menu (<code>Signal/Edit...</code>)</p> <p>Markdown Supported</p> <p>The Description field can render Markdown, a simple markup language for creating rich text using plain text. Headers, emphasis, lists, links, code blocks, and many more features for advanced text formatting. Markdown Basic Syntax </p>"},{"location":"basic_operations/#8-audio-sample","title":"8. Audio Sample","text":"<p>This is a player where an audio sample of the signal can be played. To associate an audio file to be shown as the main audio sample, check in the extra menu below the signal spectrum.</p>"},{"location":"basic_operations/#9-image-sample","title":"9. Image Sample","text":"<p>This is an image box that commonly contains the signal spectrum/waterfall. To associate an image file to be shown as the main image sample, check in the extra menu below the signal spectrum.</p>"},{"location":"basic_operations/#10-extra","title":"10. Extra","text":"<p> This button is only available for the standard SigID wiki database and connects the local signal to its counterpart on the sigidwiki website.</p> <p> This will open the Documents Manager. From here you can add any file (audio, image, pdf, etc.) to the signal entry. It is also possible to mark only one image and one audio to be shown on the main signal window.</p>"},{"location":"build_package/","title":"Build Package","text":"<p>Building a distributable package with an executable for Artemis creates a practical solution for end-users, as they can run the application without needing to interact with the terminal and they can easily share the application as a standalone package.</p>"},{"location":"build_package/#requirements","title":"Requirements","text":"<ul> <li>Python (3.11 or higher)</li> </ul> <p>Info</p> <p>We assume that Python is already installed on the system and the Artemis source code has been downloaded and extracted. If these prerequisites are not met, please follow steps 1 to 3 in the run from source section.</p> <p>Cross-Compilation</p> <p>An operating system that matches the target OS must be used to generate standalone packages, as Nuitka does not support cross-compilation. For example, you cannot build binaries on Windows that work on Linux or macOS.</p>"},{"location":"build_package/#windows","title":"Windows","text":""},{"location":"build_package/#procedure","title":"Procedure","text":"<ol> <li> <p>Open a PowerShell terminal in the main Artemis folder and execute the following command to start the build process:</p> <pre><code>.\\building\\Windows\\build_windows.ps1\n</code></pre> </li> <li> <p>Wait for the build process to complete. This may take a few minutes depending on your system's performance. Once the process finishes, check the <code>artemis.dist/</code> directory: it will contain the standalone software with the <code>artemis.exe</code> executable.</p> </li> </ol>"},{"location":"build_package/#linux","title":"Linux","text":""},{"location":"build_package/#procedure_1","title":"Procedure","text":"<ol> <li> <p>Open a terminal in the main Artemis folder and execute the following command to start the build process:     <pre><code>. ./building/Linux/build_linux.sh\n</code></pre></p> </li> <li> <p>Wait for the build process to complete. This may take a few minutes depending on your system's performance. Once the process finishes, check the <code>artemis.dist/</code> directory: it will contain the standalone software with the <code>app.bin</code> executable.</p> </li> <li>If you wish to create a shortcut, follows the procedure in the installation section</li> </ol>"},{"location":"build_package/#mac-os","title":"Mac OS","text":"<p>Warning</p> <p>The support for the macOS compiled version of the program is temporarily limited due to a lack of machines for extensive testing. Feel free to contribute by reporting any issues you encounter by opening an Issue.</p>"},{"location":"build_package/#procedure_2","title":"Procedure","text":"<ol> <li>Open a terminal in the main Artemis folder and execute the following command to start the build process:     <pre><code>. ./building/macOS/build_macos.sh\n</code></pre></li> </ol>"},{"location":"contribute/","title":"Contribute","text":"<p>Artemis is an open-source project, and every contribution, no matter how small, is valuable and greatly appreciated. Don't worry about getting everything perfect; we are happy to work with you on your contribution and help you along the way. This guide will help you get started by outlining various ways you can contribute.</p> <ul> <li> <p> Spot a bug?</p> <p>Please open an issue (or pull request) and let us know the problem you faced (or you're working on)</p> <p> Open an Issue</p> </li> <li> <p> Fork the repository</p> <p>Create a copy of the codebase from which you can modify and submit pull requests.</p> <p> Fork the repo</p> </li> <li> <p> Ideas?</p> <p>Idea for a new feature? Open an issue on the project's GitHub repository to describe your proposal.</p> <p> Open an Issue</p> </li> <li> <p> Spreading the word!</p> <p>Do you like Artemis? Remember to share it with your network and your friends!</p> </li> </ul>"},{"location":"credits/","title":"License &amp; Credits","text":""},{"location":"credits/#license","title":"License","text":"<p>Artemis is maintained by Marco Dalla Tiezza and released under the GPLv3 license.</p>"},{"location":"credits/#credits","title":"Credits","text":"<ul> <li>Marco Dalla Tiezza - Artemis I-II-IV developer, DB parsing, Website</li> <li>Alessandro Ceccato - Artemis III lead developer</li> <li>Paolo Romani (IZ1MLL) - Lead \u03b2 Tester, RF specialist</li> <li>Carl Colena - Sigidwiki admin, \u03b2 Tester, Signals expert</li> <li>Marco Bortoli - macOS deployment, \u03b2 Tester</li> <li>Eric Wiessner (KI7POL) - ARM port (Raspberry Pi3B+ and Pi4B)</li> <li>Pierpaolo Pravatto - Wiki page, \u03b2 Tester</li> <li>Francesco Capostagno, Luca, Pietro - \u03b2 Tester</li> </ul>"},{"location":"credits/#donators","title":"Donators","text":"<ul> <li>Eric Hahn</li> <li>Alan Lawrence</li> <li>Diego Gil Fernandez</li> <li>Torsten Teichert</li> <li>Charles Preston</li> <li>Brad Hein</li> <li>Paolo Romani</li> <li>Michelle Corbani</li> <li>Martin van Duinen</li> <li>Valentino Zardi</li> <li>Emmanuel Fabre</li> <li>Oscar Nilsson</li> <li>Pierre Declercq</li> <li>Detlef Jahn</li> <li>Oliver Schellenberg</li> <li>Stephane Imbertone</li> <li>Roel Ketelaars</li> <li>Timothy Ehrhart</li> <li>George Mager</li> <li>Gerhard Amon</li> <li>Gerald Schmidt</li> <li>Carlos Rocha</li> <li>Joshua Frohberg</li> <li>Bill Riches</li> <li>Jeffrey Krehbiel</li> <li>\u0412\u043e\u043b\u043e\u0434\u0438\u043c\u0438\u0440 \u0411\u0430\u0433\u043c\u0435\u0442</li> <li>Philip Hamlin</li> <li>David Davies</li> <li>Nigel P. Lawrence</li> <li>Marco Rissi (PP5ZX)</li> <li>Martin van Duinen</li> <li>Alex Diamantopulo</li> <li>Joseph Winter</li> <li>Mark Bender</li> <li>Rolf Gerhardt</li> <li>Denese Harris</li> <li>Benjamin Steele</li> <li>Alexander Irmscher</li> <li>Jonathan Chang</li> <li>Torsten Lipke</li> <li>Massimo Petrantoni</li> <li>William Arcand</li> <li>Jon Carp</li> <li>Robert Crone</li> <li>William Houston</li> <li>Richard Quasne</li> <li>Tom Krugliakov</li> <li>Francisco Neira Basso</li> <li>Alistair Macrae</li> <li>Kevin Arburn</li> <li>Marek Bar\u0142\u00f3g</li> <li>Gabriel Gl\u00f6smann</li> <li>Corbin Williams</li> <li>Ton Machielsen</li> <li>Ivan Rancic</li> <li>Alipio Fernandez</li> <li>Matt Eisele</li> <li>Martin Dudel</li> <li>Harald Geier</li> </ul>"},{"location":"installation/","title":"Installation","text":"<p>Requirements:</p> <ul> <li>Windows 8 or later</li> <li>Linux Ubuntu 20.04+ / Mint 20+ / Fedora 32+ and many other</li> <li>macOS 11+ (Big Sur or later)</li> </ul>"},{"location":"installation/#windows","title":"Windows","text":"<ol> <li>Download the installer <code>Artemis-Windows-x86_64-4.x.x.exe</code> in the Assets menu from the  LATEST RELEASE and follow the guided procedure to complete the installation process.</li> </ol>"},{"location":"installation/#linux","title":"Linux","text":"<ol> <li>Download <code>Artemis-Linux-x86_64-4.x.x.tar</code> in the Assets menu from the  LATEST RELEASE and extract the tarball archive in a folder of your choice and run the executable <code>app.bin</code>.</li> </ol>"},{"location":"installation/#create-a-shortcut","title":"Create a Shortcut","text":"<ol> <li> <p>To create a direct shortcut (in the main menu) launch the bash script in the terminal with the command:</p> <pre><code>. create_shortcut.sh\n</code></pre> </li> </ol> <p>This script will:</p> <ul> <li>Set the correct read/write privileges of the Artemis folder</li> <li>Create the artemis.desktop file (shortcut) in /home/$USER/.local/share/applications</li> <li>Move the Artemis icon file to /usr/share/icons</li> </ul>"},{"location":"installation/#mac-os","title":"Mac OS","text":"<p>Warning</p> <p>The macOS support is temporarily limited!</p> <p>The support for the macOS compiled version of the program is temporarily limited due to a lack of machines for extensive testing. To use Artemis on a macOS device, you have the following options:</p> <ul> <li>Run the program directly from the source: Follow the instructions provided in this chapter to launch the program from the source code.</li> <li>Compile the Artemis 4 binaries on your machine: In this case, you can contribute by reporting any issues you encounter by opening an Issue.</li> <li>Use the last available compiled version (3.2.1): Although this version is no longer officially supported, it remains available for use:  Artemis-3.2.1.dmg.</li> </ul>"},{"location":"run_from_source/","title":"Run from source code","text":"<p>Running Artemis directly from the source code using the Python interpreter is considered the most reliable and least problematic method. This approach ensures maximum compatibility and reduces the likelihood of encountering runtime issues. However, it is also the less practical option, as it requires the use of the terminal for the execution.</p>"},{"location":"run_from_source/#requirements","title":"Requirements","text":"<ul> <li>Python (3.11 or higher)</li> </ul>"},{"location":"run_from_source/#procedure","title":"Procedure","text":"<ol> <li> <p>Download and install Python (3.11 or higher) from the official website. Be sure to select the flag <code>Add Python 3.x to PATH</code> during the first part of the installation.</p> </li> <li> <p>Download Artemis source code from the latest release in the GitHub repository.</p> </li> <li> <p>Extract the downloaded archive.</p> </li> <li> <p>Open the terminal in Artemis folder and install the required Python libraries with PIP:     <pre><code>pip install -r requirements.txt --user\n</code></pre></p> </li> <li> <p>Launch Artemis:     <pre><code>python app.py\n</code></pre></p> </li> </ol> <p>Note for Developers</p> <p>Whenever modifications are made to any .qml file or any assets (such as images, icons, etc.), it is essential to recompile the resource.py file to ensure that the changes are reflected in the application. To achieve this, execute the following command: <pre><code>pyside6-rcc ./artemis.qrc -o artemis/resources.py\n</code></pre></p>"},{"location":"run_from_source/#folders-structure","title":"Folders Structure","text":"<p>Artemis can be safely executed and/or installed in any folder (even protected ones, such as <code>Program Files (x86)</code> in Windows) because Artemis performs read-only operations in the <code>BASE_DIR</code> folder from where it runs. All the reading-writing operations (such as database ops, logging, etc.) are performed in standard folders as follow:</p>"},{"location":"run_from_source/#windows","title":"Windows","text":"<ul> <li>Data, Cache, Configurations: <code>$USER\\AppData\\Local\\AresValley\\Artemis</code></li> <li>Logs: <code>$USER\\AppData\\Local\\Temp</code></li> </ul>"},{"location":"run_from_source/#linux","title":"Linux","text":"<ul> <li>Data, Cache, Configurations: <code>~/.local/share/AresValley/Artemis</code></li> <li>Logs: <code>/tmp</code></li> </ul>"},{"location":"run_from_source/#mac-os","title":"Mac OS","text":"<ul> <li>Data, Cache, Configurations: <code>~/Library/Application Support/AresValley/Artemis</code></li> <li>Logs: <code>/tmp</code></li> </ul>"},{"location":"database/db_acf/","title":"ACF","text":"<p>The table contains 4 columns explained below.</p> <p>Example</p> <p>A technical explanation on how autocorrelation function works along with a practical example is reported HERE</p>"},{"location":"database/db_acf/#acf_id","title":"ACF_ID","text":"<p><code>INTEGER</code> </p> <p>This is a unique identification number for each entry that is assigned during the creation of a new ACF. It is auto-incrementing and is not replaced in the event of deletion.</p>"},{"location":"database/db_acf/#sig_id","title":"SIG_ID","text":"<p><code>INTEGER</code> </p> <p>This is a direct reference to the specific signal associated with the ACF. It links to the primary key of the Signals table that holds detailed information about the signals.</p>"},{"location":"database/db_acf/#value","title":"VALUE","text":"<p><code>FLOAT</code></p> <p>The autocorrelation time expressed in ms.</p>"},{"location":"database/db_acf/#description","title":"DESCRIPTION","text":"<p><code>TEXT</code></p> <p>The short description is used to explain the details about the autocorrelation value, e.g. <code>Frame</code>, <code>Superframe</code>, etc.</p>"},{"location":"database/db_bandwidth/","title":"Bandwidth","text":"<p>The table contains 4 columns explained below.</p>"},{"location":"database/db_bandwidth/#band_id","title":"BAND_ID","text":"<p><code>INTEGER</code> </p> <p>This is a unique identification number for each entry that is assigned during the creation of a new bandwidth. It is auto-incrementing and is not replaced in the event of deletion.</p>"},{"location":"database/db_bandwidth/#sig_id","title":"SIG_ID","text":"<p><code>INTEGER</code> </p> <p>This is a direct reference to the specific signal associated with the bandwidth. It links to the primary key of the Signals table that holds detailed information about the signals.</p>"},{"location":"database/db_bandwidth/#value","title":"VALUE","text":"<p><code>INTEGER</code></p> <p>The bandwidth in Hz expressed as an integer.</p>"},{"location":"database/db_bandwidth/#description","title":"DESCRIPTION","text":"<p><code>TEXT</code></p> <p>The short description is used to explain the purpose of the bandwidth and any other useful details.</p>"},{"location":"database/db_cat_label/","title":"Category Label","text":"<p>This table contains only the name of the category/tag. The table contains 2 columns explained below.</p>"},{"location":"database/db_cat_label/#clb_id","title":"CLB_ID","text":"<p><code>INTEGER</code> </p> <p>This is a unique identification number for each entry that is assigned during the creation of a new category tag. It is auto-incrementing and is not replaced in the event of deletion.</p>"},{"location":"database/db_cat_label/#value","title":"VALUE","text":"<p><code>TEXT</code></p> <p>The name of the category/tag expressed as a string.</p>"},{"location":"database/db_category/","title":"Category","text":"<p>The primary function of this table is to facilitate the classification of the signal by assigning it to its appropriate family or category. Can be used with any tag. The table contains 3 columns explained below.</p>"},{"location":"database/db_category/#cat_id","title":"CAT_ID","text":"<p><code>INTEGER</code> </p> <p>This is a unique identification number for each entry that is assigned during the creation of a new category/tag. It is auto-incrementing and is not replaced in the event of deletion.</p>"},{"location":"database/db_category/#sig_id","title":"SIG_ID","text":"<p><code>INTEGER</code> </p> <p>This is a direct reference to the specific signal associated with the category. It links to the primary key of the Signals table that holds detailed information about the signals.</p>"},{"location":"database/db_category/#clb_id","title":"CLB_ID","text":"<p><code>INTEGER</code> </p> <p>This is a direct reference to the specific category label associated with the category. It links to the primary key of the Category Label table that holds the name of the category.</p>"},{"location":"database/db_frequency/","title":"Frequency","text":"<p>The table contains 4 columns explained below.</p>"},{"location":"database/db_frequency/#freq_id","title":"FREQ_ID","text":"<p><code>INTEGER</code> </p> <p>This is a unique identification number for each entry that is assigned during the creation of a new frequency. It is auto-incrementing and is not replaced in the event of deletion.</p>"},{"location":"database/db_frequency/#sig_id","title":"SIG_ID","text":"<p><code>INTEGER</code> </p> <p>This is a direct reference to the specific signal associated with the frequency. It links to the primary key of the Signals table that holds detailed information about the signals.</p>"},{"location":"database/db_frequency/#value","title":"VALUE","text":"<p><code>INTEGER</code></p> <p>The freqeuncy in Hz expressed as an integer.</p>"},{"location":"database/db_frequency/#description","title":"DESCRIPTION","text":"<p><code>TEXT</code></p> <p>The short description is used to explain the purpose of the bandwidth and any other useful details.</p>"},{"location":"database/db_info/","title":"Info","text":"<p>This is the database meta table and contains 4 columns explained below.</p>"},{"location":"database/db_info/#name","title":"NAME","text":"<p><code>TEXT</code></p> <p>This is the name of the database.</p>"},{"location":"database/db_info/#data","title":"DATA","text":"<p><code>TEXT</code></p> <p>The creation date when the database has been initialised.</p>"},{"location":"database/db_info/#version","title":"VERSION","text":"<p><code>INTEGER</code></p> <p>A simple integer to denote the database version.</p>"},{"location":"database/db_info/#editable","title":"EDITABLE","text":"<p><code>INTEGER</code></p> <p>This field should serve as a writing protection on the database.</p> <ul> <li>0: read-only database</li> <li>1: database can be edited with no restrictions</li> </ul> <p>Experimental</p> <p>This feature is experimental and not yet implemented.</p>"},{"location":"database/db_location/","title":"Location","text":"<p>This is the location where the signal is distributed/received. Avoid the usage of the precise location of the TX station or very small town (very rare). It's a good habit to use nations/continents or special location (like <code>Worldwide</code>). The table contains 4 columns explained below.</p>"},{"location":"database/db_location/#loc_id","title":"LOC_ID","text":"<p><code>INTEGER</code> </p> <p>This is a unique identification number for each entry that is assigned during the creation of a new location. It is auto-incrementing and is not replaced in the event of deletion.</p>"},{"location":"database/db_location/#sig_id","title":"SIG_ID","text":"<p><code>INTEGER</code> </p> <p>This is a direct reference to the specific signal associated with the location. It links to the primary key of the Signals table that holds detailed information about the signals.</p>"},{"location":"database/db_location/#value","title":"VALUE","text":"<p><code>TEXT</code></p> <p>The location expressed as a string.</p>"},{"location":"database/db_location/#description","title":"DESCRIPTION","text":"<p><code>TEXT</code></p> <p>The short description is used to explain further details about the location.</p>"},{"location":"database/db_mode/","title":"Mode","text":"<p>This field reports the way how a signals has been decoded during the reception. The table contains 4 columns explained below.</p>"},{"location":"database/db_mode/#mod_id","title":"MOD_ID","text":"<p><code>INTEGER</code> </p> <p>This is a unique identification number for each entry that is assigned during the creation of a new mode. It is auto-incrementing and is not replaced in the event of deletion.</p>"},{"location":"database/db_mode/#sig_id","title":"SIG_ID","text":"<p><code>INTEGER</code> </p> <p>This is a direct reference to the specific signal associated with the modulation. It links to the primary key of the Signals table that holds detailed information about the signals.</p>"},{"location":"database/db_mode/#value","title":"VALUE","text":"<p><code>TEXT</code></p> <p>The mode expressed as a string.</p>"},{"location":"database/db_mode/#description","title":"DESCRIPTION","text":"<p><code>TEXT</code></p> <p>The short description is used to explain the purpose of the mode and any other useful details.</p>"},{"location":"database/db_modulation/","title":"Modulation","text":"<p>Modulation refers to the method by which information is encoded into the main signal (carrier). This process involves altering various properties of the carrier signal, such as amplitude, frequency, or phase. Multiple modulation techniques can be employed, and a TX station has the capability to utilize different modulation schemes. The table contains 4 columns explained below.</p>"},{"location":"database/db_modulation/#mdl_id","title":"MDL_ID","text":"<p><code>INTEGER</code> </p> <p>This is a unique identification number for each entry that is assigned during the creation of a new modulation. It is auto-incrementing and is not replaced in the event of deletion.</p>"},{"location":"database/db_modulation/#sig_id","title":"SIG_ID","text":"<p><code>INTEGER</code> </p> <p>This is a direct reference to the specific signal associated with the modulation. It links to the primary key of the Signals table that holds detailed information about the signals.</p>"},{"location":"database/db_modulation/#value","title":"VALUE","text":"<p><code>TEXT</code></p> <p>The modulation expressed as a string.</p>"},{"location":"database/db_modulation/#description","title":"DESCRIPTION","text":"<p><code>TEXT</code></p> <p>The short description is used to explain the purpose of the modulation and any other useful details.</p>"},{"location":"database/db_overview/","title":"Database","text":"<p>With the release of Artemis 4, we have made a significant upgrade in our data management system by transitioning from a CSV file to a full relational SQL database. This change brings a multitude of advantages that enhance the efficiency, scalability, and reliability of our system. In the following sections, we will explore, table by table, the structure of the new database.</p> <p></p>"},{"location":"database/db_signals/","title":"Signals","text":"<p>This is the main table and contains 4 columns explained below.</p>"},{"location":"database/db_signals/#sig_id","title":"SIG_ID","text":"<p><code>INTEGER</code> </p> <p>This is a unique identification number for each entry that is assigned during the creation of a signal. It is auto-incrementing and is not replaced in the event of signal deletion.</p>"},{"location":"database/db_signals/#name","title":"NAME","text":"<p><code>TEXT</code></p> <p>The name of the signal. A simple string that describes in short the analyzed signal. Special characters are allowed.</p>"},{"location":"database/db_signals/#description","title":"DESCRIPTION","text":"<p><code>TEXT</code></p> <p>The short description is used to explain the purpose of the signal and some other useful details.</p> <p>Tip</p> <p>The DESCRIPTION field supports Markdown, a simple markup language for creating rich text using plain text. Headers, emphasis, lists, links, code blocks and many more features for advanced text formtting. Markdown Basic Syntax </p>"},{"location":"database/db_signals/#url","title":"URL","text":"<p><code>TEXT</code></p> <p>The sigidwiki (SigID) URL of the selected signal. This is a direct connection to the online database where further details of the signal are collected.</p> <p>Info</p> <p>Internal Use Only This field is for the SigID database and not intended for user viewing or editing. Personal URLs can be stored in the signal description.</p>"},{"location":"database/sigid/","title":"SigID Wiki Database","text":"<p>Artemis serves as a valuable resource for both personal signal collection and leveraging a vast repository of pre-identified signals. This software application allows users to curate their own collections, but its true strength lies in its integration with a comprehensive database of known signals. This database is directly sourced from the Signal Identification Wiki, an open-source resource collaboratively maintained by a global community of radio enthusiasts.</p> <p>Database Revision</p> <p>For quality control purposes, the database undergoes a rigorous review process before integration into Artemis. This review adheres to established guidelines, ensuring the accuracy and completeness of the information presented to users. The specifics of this review process are outlined in the following section.</p>"},{"location":"database/sigid/#modulation","title":"Modulation","text":"<p>A good practise (reported also on ) is to write the primary type of modulation (if known) and not all the possible variants. A practical example is reported on Signal Identification Wiki: there is no need to write 8-PSK or QPSK, PSK is enough. The Artemis SigID database is provided without any modulation variants included. The recognized modulations are listed below:</p>"},{"location":"database/sigid/#analog","title":"Analog","text":"<ul> <li>AM: Amplitude Modulation</li> <li>FM: Frequency Modulation</li> <li>PM: Phase Modulation</li> <li>LSB: Lower Sideband</li> <li>USB: Upper Sideband</li> <li>VSB: Vestigial Sideband</li> <li>CW: Continuous Wave</li> </ul>"},{"location":"database/sigid/#digital","title":"Digital","text":"<ul> <li>QAM: Quadrature Amplitude Modulation</li> <li>PSK: Phase-Shift Keying</li> <li>FSK: Frequency-Shift Keying</li> <li>ASK: Amplitude-Shift Keying</li> <li>MSK: Minimum-Shift Keying</li> <li>IFK: Incremental Frequency Keying</li> <li>OOK: On-Off Keying</li> <li>FDM: Frequency-Division Multiplexing</li> <li>BOC: Binary Offset Carrier Modulation</li> <li>CDMA: Code Division Multiple Access</li> <li>TDMA: Time Division Multiple Access</li> <li>FBMC: Filter Bank Multi Carrier</li> <li>UFMC: Universal Filtered Multi Carrier</li> <li>PCM: Pulse Code Modulation</li> <li>PPM: Pulse Position Modulation</li> <li>FMCW: Frequency-Modulated Continuous Wave</li> <li>Pulse: Pulse</li> </ul>"},{"location":"database/sigid/#spread-spectrum","title":"Spread Spectrum","text":"<ul> <li>CSS: Chirp Spread Spectrum</li> <li>DSSS: Direct Sequence Spread Spectrum</li> <li>FHSS: Frequency Hopping Spread Spectrum</li> <li>THSS: Time Hopping Spread Spectrum</li> </ul>"},{"location":"database/sigid/#locations","title":"Locations","text":"<p>Locations are either countries or special token (<code>Worldwide</code>, <code>Europe</code>, etc.) . Precise location of the TX station, towns and cities are converted to their respective countries.</p>"},{"location":"space_weather/aurora/","title":"Aurora","text":"<p>This short-term aurora forecast predicts its location and intensity over the next 30 to 90 minutes, based on the OVATION model. The lead time of the forecast corresponds to the duration it takes for the solar wind to travel from the L1 observation point to Earth.</p> <p>Auroras indicate current geomagnetic storm conditions and provide situational awareness for various technologies: for example, they directly affect HF radio communication and GPS/GNSS satellite navigation and are related to ground-induced currents impacting electric power transmission.</p> <p>For many people, the aurora is a beautiful nighttime phenomenon that is worth traveling to arctic regions just to observe.  It is the only way for most people to actually experience space weather.</p>"},{"location":"space_weather/current/","title":"Current","text":""},{"location":"space_weather/current/#1-kp-index","title":"1. Kp Index","text":"<p>The K index is a number (from 0 to 9) that shows how much Earth's magnetic field is disturbed. A K index of 1 means things are calm, while a K index of 5 or higher indicates a geomagnetic storm. These disturbances are measured with magnetometers that track changes in Earth's magnetic field every three hours. The K itself comes from a German word \"Kennziffer\" meaning \"characteristic digit\". To get a big picture of what's happening around the world, an official planetary Kp index is calculated. This is done by averaging the K indices from a special network of 13 geomagnetic observatories located around the globe at mid-latitudes.</p>"},{"location":"space_weather/current/#2-a-index","title":"2. A Index","text":"<p>The A index represents the three-hourly equivalent amplitude of geomagnetic activity at a specific magnetometer station, derived from the station-specific K index. Due to the quasi-logarithmic nature of the K-scale in relation to magnetometer fluctuations, directly averaging a set of K indices is not really meaningful. Instead each K is converted back into a linear scale. The Ap index is determined by averaging the eight daily A values, providing a measure of geomagnetic activity for a specific day. Days with higher levels of geomagnetic activity correspond to higher daily Ap values.</p>"},{"location":"space_weather/current/#3-noaa-space-weather-scale","title":"3. NOAA Space Weather Scale","text":""},{"location":"space_weather/current/#geomagnetic-storm","title":"Geomagnetic Storm","text":"G5 (Extreme) <ul> <li>Physical measure: Kp = 9</li> <li>Average Frequency: 4 days per cycle (11 years)</li> </ul> <p>Power systems: Widespread voltage control problems and protective system problems can occur, some grid systems may experience complete collapse or blackouts. Transformers may experience damage.</p> <p>Spacecraft operations: May experience extensive surface charging, problems with orientation, uplink/downlink and tracking satellites.</p> <p>Other systems: Pipeline currents can reach hundreds of amps, HF (high frequency) radio propagation may be impossible in many areas for one to two days, satellite navigation may be degraded for days, low-frequency radio navigation can be out for hours, and aurora has been seen as low as Florida and southern Texas (typically 40\u00b0 geomagnetic lat.).</p> G4 (Severe) <ul> <li>Physical measure: Kp = 8 to 9-</li> <li>Average Frequency: 60 days per cycle (11 years)</li> </ul> <p>Power systems: Possible widespread voltage control problems and some protective systems will mistakenly trip out key assets from the grid.</p> <p>Spacecraft operations: May experience surface charging and tracking problems, corrections may be needed for orientation problems.</p> <p>Other systems: Induced pipeline currents affect preventive measures, HF radio propagation sporadic, satellite navigation degraded for hours, low-frequency radio navigation disrupted, and aurora has been seen as low as Alabama and northern California (typically 45\u00b0 geomagnetic lat.).</p> G3 (Strong) <ul> <li>Physical measure: Kp = 7</li> <li>Average Frequency: 130 days per cycle (11 years)</li> </ul> <p>Power systems: Voltage corrections may be required, false alarms triggered on some protection devices.</p> <p>Spacecraft operations: Surface charging may occur on satellite components, drag may increase on low-Earth-orbit satellites, and corrections may be needed for orientation problems.</p> <p>Other systems: Intermittent satellite navigation and low-frequency radio navigation problems may occur, HF radio may be intermittent, and aurora has been seen as low as Illinois and Oregon (typically 50\u00b0 geomagnetic lat.).</p> G2 (Moderate) <ul> <li>Physical measure: Kp = 6</li> <li>Average Frequency: 360 days per cycle (11 years)</li> </ul> <p>Power systems: High-latitude power systems may experience voltage alarms, long-duration storms may cause transformer damage.</p> <p>Spacecraft operations: Corrective actions to orientation may be required by ground control; possible changes in drag affect orbit predictions.</p> <p>Other systems: HF radio propagation can fade at higher latitudes, and aurora has been seen as low as New York and Idaho (typically 55\u00b0 geomagnetic lat.).</p> G1 (Minor) <ul> <li>Physical measure: Kp = 5</li> <li>Average Frequency: 900 days per cycle (11 years)</li> </ul> <p>Power systems: Weak power grid fluctuations can occur.</p> <p>Spacecraft operations: Minor impact on satellite operations possible.</p> <p>Other systems: Migratory animals are affected at this and higher levels; aurora is commonly visible at high latitudes (northern Michigan and Maine).</p>"},{"location":"space_weather/current/#solar-radiation-storms","title":"Solar Radiation Storms","text":"S5 (Extreme) <ul> <li>Physical measure: Flux level of \\(\\ge 10 MeV\\) particles = \\(10^5\\)</li> <li>Average Frequency: &lt; 1 event per cycle (11 years)</li> </ul> <p>Biological: Unavoidable high radiation hazard to astronauts on EVA (extra-vehicular activity); passengers and crew in high-flying aircraft at high latitudes may be exposed to radiation risk.</p> <p>Satellite operations: Satellites may be rendered useless, memory impacts can cause loss of control, may cause serious noise in image data, star-trackers may be unable to locate sources; permanent damage to solar panels possible.</p> <p>Other systems: Complete blackout of HF (high frequency) communications possible through the polar regions, and position errors make navigation operations extremely difficult.</p> S4 (Severe) <ul> <li>Physical measure: Flux level of \\(\\ge 10 MeV\\) particles = \\(10^4\\)</li> <li>Average Frequency: 3 events per cycle (11 years)</li> </ul> <p>Biological: Unavoidable radiation hazard to astronauts on EVA; passengers and crew in high-flying aircraft at high latitudes may be exposed to radiation risk.</p> <p>Satellite operations: May experience memory device problems and noise on imaging systems; star-tracker problems may cause orientation problems, and solar panel efficiency can be degraded.</p> <p>Other systems: Blackout of HF radio communications through the polar regions and increased navigation errors over several days are likely.</p> S3 (Strong) <ul> <li>Physical measure: Flux level of \\(\\ge 10 MeV\\) particles = \\(10^3\\)</li> <li>Average Frequency: 10 events per cycle (11 years)</li> </ul> <p>Biological: Radiation hazard avoidance recommended for astronauts on EVA; passengers and crew in high-flying aircraft at high latitudes may be exposed to radiation risk.</p> <p>Satellite operations: Single-event upsets, noise in imaging systems, and slight reduction of efficiency in solar panel are likely.</p> <p>Other systems: Degraded HF radio propagation through the polar regions and navigation position errors likely.</p> S2 (Moderate) <ul> <li>Physical measure: Flux level of \\(\\ge 10 MeV\\) particles = \\(10^2\\)</li> <li>Average Frequency: 25 events per cycle (11 years)</li> </ul> <p>Biological: Passengers and crew in high-flying aircraft at high latitudes may be exposed to elevated radiation risk.</p> <p>Satellite operations: Infrequent single-event upsets possible.</p> <p>Other systems: Small effects on HF propagation through the polar regions and navigation at polar cap locations possibly affected.</p> S1 (Minor) <ul> <li>Physical measure: Flux level of \\(\\ge 10 MeV\\) particles = \\(10\\)</li> <li>Average Frequency: 50 events per cycle (11 years)</li> </ul> <p>Biological: None.</p> <p>Satellite operations: None.</p> <p>Other systems: Minor impacts on HF radio in the polar regions.</p>"},{"location":"space_weather/current/#radio-blackouts","title":"Radio Blackouts","text":"R5 (Extreme) <ul> <li>Physical measure:* X20 (\\(2e^{-3} Wm^{-2}\\))</li> <li>Average Frequency: &lt; 1 days per cycle (11 years)</li> </ul> <p>HF Radio: Complete HF (high frequency**) radio blackout on the entire sunlit side of the Earth lasting for a number of hours. This results in no HF radio contact with mariners and en route aviators in this sector.</p> <p>Navigation: Low-frequency navigation signals used by maritime and general aviation systems experience outages on the sunlit side of the Earth for many hours, causing loss in positioning. Increased satellite navigation errors in positioning for several hours on the sunlit side of Earth, which may spread into the night side. </p> <p>*GOES X-ray peak brightness by class and by flux (measured in the 0.1-0.8 nm range, in W\u00b7m-2)</p> R4 (Severe) <ul> <li>Physical measure:* X10 (\\(10^{-3} Wm^{-2}\\))</li> <li>Average Frequency: 8 days per cycle (11 years)</li> </ul> <p>HF Radio: HF radio communication blackout on most of the sunlit side of Earth for one to two hours. HF radio contact lost during this time.</p> <p>Navigation: Outages of low-frequency navigation signals cause increased error in positioning for one to two hours. Minor disruptions of satellite navigation possible on the sunlit side of Earth.</p> <p>*GOES X-ray peak brightness by class and by flux (measured in the 0.1-0.8 nm range, in W\u00b7m-2)</p> R3 (Strong) <ul> <li>Physical measure:* X1 (\\(10^{-4} Wm^{-2}\\))</li> <li>Average Frequency: 140 days per cycle (11 years)</li> </ul> <p>HF Radio: Wide area blackout of HF radio communication, loss of radio contact for about an hour on sunlit side of Earth.</p> <p>Navigation: Low-frequency navigation signals degraded for about an hour. </p> <p>*GOES X-ray peak brightness by class and by flux (measured in the 0.1-0.8 nm range, in W\u00b7m-2)</p> R2 (Moderate) <ul> <li>Physical measure:* M5 (\\(5e^{-5} Wm^{-2}\\))</li> <li>Average Frequency: 300 days per cycle (11 years)</li> </ul> <p>HF Radio: Limited blackout of HF radio communication on sunlit side of the Earth, loss of radio contact for tens of minutes.</p> <p>Navigation: Degradation of low-frequency navigation signals for tens of minutes. </p> <p>*GOES X-ray peak brightness by class and by flux (measured in the 0.1-0.8 nm range, in W\u00b7m-2)</p> R1 (Minor) <ul> <li>Physical measure:* M1 (\\(10^{-5} Wm^{-2}\\))</li> <li>Average Frequency: 950 days per cycle (11 years)</li> </ul> <p>HF Radio: Weak or minor degradation of HF radio communication on sunlit side of the Earth, occasional loss of radio contact.</p> <p>Navigation: Low-frequency navigation signals degraded for brief intervals. </p> <p>*GOES X-ray peak brightness by class and by flux (measured in the 0.1-0.8 nm range, in W\u00b7m-2)</p>"},{"location":"space_weather/current/#4-x-ray-solar-activity","title":"4. X-Ray Solar Activity","text":"<p>This is a summary of the X-Ray Flare Class. Large solar X-ray flares can change the Earth\u2019s ionosphere, which blocks high-frequency (HF) radio transmissions on the sunlit side of the Earth. Solar flares are also associated with Coronal Mass Ejections (CMEs) which can ultimately lead to geomagnetic storms. SWPC sends out space weather alerts at the M5 level. Some large flares are accompanied by strong radio bursts that may interfere with other radio frequencies and cause problems for satellite communication and radio navigation (GPS).</p> Class Peak Strength (W/m<sup>2</sup>) Effects on Earth B I &lt; 10<sup>-6</sup> Too small to harm Earth C 10<sup>-6</sup> \u2264 I &lt; 10<sup>-5</sup> Small with few noticeable consequences M 10<sup>-5</sup> \u2264 I &lt; 10<sup>-4</sup> Brief radio blackouts in polar regions, minor radiation storms X I \u2265 10<sup>-4</sup> Planet-wide radio blackouts, long-lasting radiation storms"},{"location":"space_weather/current/#5-rf-propagation","title":"5. RF Propagation","text":""},{"location":"space_weather/current/#maximum-usable-frequency","title":"Maximum Usable Frequency","text":"<p>In radio transmission, the maximum usable frequency (MUF) is the highest frequency that can be effectively used for communication between two locations on Earth by reflecting off the ionosphere (via skywave or skip) at a given time, regardless of the transmitter's power. This measurement is particularly valuable for shortwave transmissions.</p>"},{"location":"space_weather/current/#earth-moon-earth","title":"Earth-Moon-Earth","text":"<p>Earth\u2013Moon\u2013Earth communication (EME), commonly referred to as Moon bounce, is a radio communication method in which radio waves are transmitted from an Earth-based station, reflected off the Moon's surface, and then received back on Earth. The value gives the probability of a succesfull connection.</p>"},{"location":"space_weather/current/#meteor-scatter","title":"Meteor Scatter","text":"<p>Meteor burst communications (MBC), also known as meteor scatter (MS) communications, is a radio propagation technique that uses the ionized trails created by meteors entering the atmosphere to establish brief communication links between radio stations up to 2,250 kilometers (1,400 miles) apart. This can involve either forward-scatter or back-scatter of the radio waves. Like EME, the value gives the probability of a succesfull connection.</p>"},{"location":"space_weather/current/#sporadic-e","title":"Sporadic-E","text":"<p>Report of the latest E-skip spots on 50, 70 &amp; 144 MHz by DXrobot</p> <p>Sporadic E (Es or SpE) is a rare type of radio propagation that uses a lower part of the Earth's ionosphere, which typically doesn't refract radio waves. It reflects signals off small \"clouds\" in the E region at altitudes of 95-150 km (50-100 miles). Unlike the regular F region skywave propagation, which depends on daily cycles of ionized layers from UV light, Sporadic E uses transient ionized patches. This allows for occasional long-distance VHF communication, usually during the six weeks around the summer solstice, beyond the normal line-of-sight range.</p>"},{"location":"space_weather/current/#aurora-spots","title":"Aurora Spots","text":"<p>Report of the latest aurora spots on 50, 70 &amp; 144 MHz by DXrobot</p> <p>Auroral propagation, or auroral backscatter, is a form of radio propagation that occurs during an auroral event, affecting VHF and UHF communications. Increased ionization in the E layer of the ionosphere reflects signals at much higher frequencies than usual, enabling communication up to 1000 MHz, though 500 MHz is more common. Signals are directed towards the auroral region and reflected back, but they are often distorted due to particle movement (the signal is roughly Doppler shifted of 1 kHz at around 150 MHz as the electrons stream down).</p>"},{"location":"space_weather/current/#expected-hf-noise","title":"Expected HF Noise","text":"<p>This is just the expected noise in HF based on the current Space Weather conditions.</p>"},{"location":"space_weather/current/#6-report-age","title":"6. Report Age","text":"<p>Poseidon Daemon is in charge of parse all the necessary data used for the Space Weather module. The data of the last generated report is written here.</p>"},{"location":"space_weather/drap/","title":"DRAP","text":"<p>The D-Region Absorption Product (DRAP) evaluates the effects of solar X-ray flux and solar energetic particle (SEP) events on HF radio communication. Long-distance communications using high frequency (HF) radio waves (3 - 30 MHz) rely on signal reflection in the ionosphere. Typically, radio waves reflect near the peak of the F2 layer (~300 km altitude), but during their journey to and from this peak, the signals experience attenuation due to absorption by the intervening ionosphere.</p> <p>The D-Region Absorption Prediction model provides guidance to understand the degradation and blackouts of HF radio communications that can result from these conditions.</p>"},{"location":"space_weather/forecasts/","title":"Forecasts","text":""},{"location":"space_weather/forecasts/#1-forecast-summary","title":"1. Forecast Summary","text":"<p>Geomagnetic activity, Solar Radiation Storms and Radio Blackouts probable events (in the next 3 days) are described in this section. </p>"},{"location":"space_weather/forecasts/#2-3-day-kp-index","title":"2. 3-Day Kp Index","text":"<p>This is a 3 day projection of the Kp index.</p>"},{"location":"space_weather/forecasts/#3-events-probability","title":"3. Events Probability","text":"<p>The probability (in percentage) of different events that can take place and generate some important conditions for RF propagation. All the event are explained here.</p> <p>Info</p> <p>Geomagnetic Activity has two percentual value per day: the left one refers to high-latitude location and the right one is for middle-latitude locations.</p>"}]}
\ No newline at end of file
diff --git a/sitemap.xml.gz b/sitemap.xml.gz
index f9949571fd552f921676b7250e07a408a1a4284e..5a4c4d71229798a90de5cb76ec5154f561a8cbbf 100755
GIT binary patch
delta 13
Ucmb=gXP58h;7I6;pU7ST02~bj9RL6T

delta 13
Ucmb=gXP58h;CNsYH<7&p03B}xN&o-=