update readme

.vscode/settings.json

-{
+{
     "files.exclude":
     {
         "**/.DS_Store":true,
@@ -52,5 +52,6 @@
         "ProjectSettings/":true,
         "temp/":true,
         "Temp/":true
-    }
+    },
+    "dotnet.defaultSolution": "prototype_drones_simulator.sln"
 }
\ No newline at end of file

Assets/Log/log_1682580218_V0_Test1682580452_V0_Test1682580541_V0_Test1682580633_V0_Test1682580712_V0_Test1682580795_V0_Test1682588022_V0_Test1682588228_V0_Test1682588321_V0_Test1682588373_V0_Test

-timestamp,  type,  temps en seconde,   nbPoints,   nbDronesActifs, nbAlarmesActives
\ No newline at end of file

Assets/Log/log_1682580218_V0_Test1682580452_V0_Test1682580541_V0_Test1682580633_V0_Test1682580712_V0_Test1682580795_V0_Test1682588022_V0_Test1682588228_V0_Test1682588321_V0_Test1682588373_V0_Test.meta

-fileFormatVersion: 2
-guid: 33a8fd5ab38d18f42bc60e3773823323
-DefaultImporter:
-  externalObjects: {}
-  userData: 
-  assetBundleName: 
-  assetBundleVariant: 

Assets/Scripts/Alert.cs

@@ -12,7 +12,7 @@ public class Alert : MonoBehaviour
     protected bool isAlert = false;
     private bool inTraitement = false;
     protected long timeInit;
-    public int lenght = 5; // Duration of the alert in second
+    public int length = 5; // Duration of the alert in second
 
     public int proba = 20;
 
@@ -94,13 +94,13 @@ public class Alert : MonoBehaviour
     }
 
     IEnumerator waitForEndAlert () {    
-        yield return new WaitForSeconds(lenght);
+        yield return new WaitForSeconds(length);
     
         if (isAlert) {
             Points.setPoints(Points.getPoints() - 5);
             GameObject.Find("Points").GetComponent<Text>().text = "Points " + Points.getPoints().ToString();
 
-            Log.AddLog(3, drone.getNbDronesActifs(), getAlertStatus(), lenght, lenght);
+            Log.AddLog(3, drone.getNbDronesActifs(), getAlertStatus(), length, length);
 
             GameObject.Find("Feedback").GetComponent<Feedback>().launchFeedback("-5");
             SetInitialState();

Assets/Scripts/AlertV1.cs

@@ -6,7 +6,7 @@ using UnityEngine.UI;
 public class AlertV1 : Alert
 {
     private void OnMouseDown () {
-        Log.AddLog(1, drone.getNbDronesActifs(), getAlertStatus(), System.DateTimeOffset.UtcNow.ToUnixTimeSeconds() - timeInit, lenght);
+        Log.AddLog(1, drone.getNbDronesActifs(), getAlertStatus(), System.DateTimeOffset.UtcNow.ToUnixTimeSeconds() - timeInit, length);
 
         SetInitialState();
     }

Packages/packages-lock.json

 {
   "dependencies": {
-    "com.network": {
-      "version": "file:submodule_network",
-      "depth": 0,
-      "source": "embedded",
-      "dependencies": {}
-    },
     "com.unity.collab-proxy": {
       "version": "1.15.1",
       "depth": 0,

submodule_network @ c15f0f9e

-Subproject commit c15f0f9eefbaf21333a7fe345821caa2b66f4721

README.md

 # Prototype_drones_simulator
 
 
+## Installation
 
-## Getting started
+```
+git clone https://gitlab.imt-atlantique.fr/sos-dm/prototype_drones_simulator.git
+```
 
-To make it easy for you to get started with GitLab, here's a list of recommended next steps.
+Installer Unity Hub : https://unity.com/fr/download
 
-Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
+Installer la version d'Unity 2020.3.23f1
 
-## Add your files
+Ouvrir le projet avec Unity Hub 
 
-- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
-- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
 
-```
-cd existing_repo
-git remote add origin https://gitlab.imt-atlantique.fr/a23daigr/prototype_drones_simulator.git
-git branch -M main
-git push -uf origin main
-```
-
-## Integrate with your tools
+## Demarrage
 
-- [ ] [Set up project integrations](https://gitlab.imt-atlantique.fr/a23daigr/prototype_drones_simulator/-/settings/integrations)
+Dans Unity App Sim Target > Target > Device > Play
 
-## Collaborate with your team
+Cliquer sur play pour lancer la simulation
 
-- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
-- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
-- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
-- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
-- [ ] [Automatically merge when pipeline succeeds](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)
 
-## Test and Deploy
+## Configuration
 
-Use the built-in continuous integration in GitLab.
+### Les drones
 
-- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html)
-- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing(SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
-- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
-- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
-- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
+#### Nombres
 
-***
+Fenetre Project > Assets > Prefab > Table > Initialize Env > Total Number Of Drone
 
-# Editing this README
+(By default 10)
 
-When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thank you to [makeareadme.com](https://www.makeareadme.com/) for this template.
+#### Temps d'actions
 
-## Suggestions for a good README
-Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
+Fenetre Project > Assets > Prefab > Drone > Cylinder > Drone AI Sc 1_V1 > Event Duration
 
-## Name
-Choose a self-explaining name for your project.
+(By default 15s)
 
-## Description
-Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
+#### Proba d'action
 
-## Badges
-On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
+Fenetre Project > Assets > Prefab > Drone > Cylinder > Drone AI Sc 1_V1 > Proba
 
-## Visuals
-Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
+(By default 1 chance / 20 per seconde)
 
-## Installation
-Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
+### Les alertes
 
-## Usage
-Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
+#### Nombres
 
-## Support
-Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
+Fenetre Project > Assets > Prefab > Table > Initialize Env > Total Number Of Alarme
 
-## Roadmap
-If you have ideas for releases in the future, it is a good idea to list them in the README.
+(By default 4)
 
-## Contributing
-State if you are open to contributions and what your requirements are for accepting them.
+#### Temps d'actions
 
-For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
+Fenetre Project > Assets > Prefab > Alert > Alert V1 > length
 
-You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
+(By default 5s)
 
-## Authors and acknowledgment
-Show your appreciation to those who have contributed to the project.
+#### Proba d'action
 
-## License
-For open source projects, say how it is licensed.
+Fenetre Project > Assets > Prefab > Alert > Alert V1 > Proba
 
-## Project status
-If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.
+(By default 1 chance / 20 per seconde)