Skip to content

Commit

Permalink
Fixing md files
Browse files Browse the repository at this point in the history
  • Loading branch information
fchuffar committed Nov 13, 2024
1 parent 984f5af commit 7f450f0
Show file tree
Hide file tree
Showing 2 changed files with 40 additions and 27 deletions.
61 changes: 36 additions & 25 deletions phase-0-smoothie/bundle/FAQ.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,51 +2,62 @@


**Why dis my submission failed ? -> Have a look at the logs on Codabench**
## Why did my submission failed ?

Have a look at the logs on Codabench.
If your submission fails on Codabench, don't panic, review the logs! You can access them via the Codabench user interface:

1. Go to the "Submission" tab and scroll to the end of the page to find your submission.
2. Click on the row corresponding to your submission.
3. Select the "Logs" tab.
4. Browse the various types of logs available: `stdout`, `stderr`, `Ingestion stdout`, and `Ingestion stderr`, for both the ingestion and scoring steps.

**How to configure my environment ? Try interactive docker or conda environnement: (Especially useful for python user !)**
## How to configure my environment?

A conda evnironnement is provided follow this steps to install and activate it:
- retrieve the file environment-r.yml from github : [environment-r.yml](https://github.com/bcm-uga/hadaca3/blob/main/docker/codabench_hadaca3_pyr/environment/environment-r.yml) :
- `wget https://raw.githubusercontent.com/bcm-uga/hadaca3/main/docker/codabench_hadaca3_pyr/environment/environment-r.yml`
- and run: `conda env create -f environment-r.yml && conda activate h3`
Try interactive docker or conda environnement, it is especially useful for python user!

A conda environment is provided follow this steps to install and activate it. Retrieve the file [environment-r.yml](https://github.com/bcm-uga/hadaca3/blob/main/docker/codabench_hadaca3_pyr/environment/environment-r.yml) from github as follow:

To run the docker interactively you can run with :
- `sudo docker run -it -v .:/hadaca3 -w /hadaca3 hombergn/hadaca3_pyr R` and then `source("submission_script.R")` for the R version
- `sudo docker run -it -v .:/hadaca3 -w /hadaca3 hombergn/hadaca3_pyr python` and then `import submission_script` for the python version.
```
wget https://raw.githubusercontent.com/bcm-uga/hadaca3/main/docker/codabench_hadaca3_pyr/environment/environment-r.yml
conda env create -f environment-r.yml && conda activate h3
```

Due to the usage of the super user (sudo) all files created by docker will be owned by root. In order to retrieve ownership, you can use this command : `sudo chown -R $USER submissions`.
To run the docker interactively you can run with:

```
# for the R version
sudo docker run -it -v .:/hadaca3 -w /hadaca3 hombergn/hadaca3_pyr R` and then `source("submission_script.R")
# for the python version
sudo docker run -it -v .:/hadaca3 -w /hadaca3 hombergn/hadaca3_pyr python` and then `import submission_script
```

Due to the usage of the super user (sudo) all files created by docker will be owned by root. In order to retrieve ownership, you can use this command:

```
sudo chown -R $USER submissions
```

Beware that Mac users with M1 processors might encounter problems.


**How to run submissions ingestion and scoring locally with Docker ?**
## How to run submissions ingestion and scoring locally with Docker?

To speed up the debugging process and avoid the full submission workflow, you can run your submission program locally using **FAKE** data. The fake data serves two purposes: first, it allows testing without relying on the actual scoring program (which requires the ground truth), and second, it speeds up computation.

To test locally, follow these steps:

1. Clone the challenge repository:
```
git clone https://github.com/bcm-uga/hadaca3.git
cd hadaca3
```
2. Set up the environment and activate it:
```
conda env create -f environment-r.yml && conda activate h3
```
3. Run the automated Docker test script:
```
sh automated_docker_test.sh
```
```
# Clone the challenge repository:
git clone https://github.com/bcm-uga/hadaca3.git
cd hadaca3
# Set up the environment and activate it:
conda env create -f environment-r.yml && conda activate h3
# Run the automated Docker test script:
sh automated_docker_test.sh
```

Please note that this script will use the `submission_script.R` from the `hadaca3/starting_kit/` folder. **Ensure that your script is placed inside the `hadaca3/starting_kit/` folder or modify the existing script at `hadaca3/starting_kit/submission_script.R`**.

Expand All @@ -55,7 +66,7 @@ The script `automated_docker_test.sh` first executes the R submission script loc

If you wish to test each step independently or run the Python script locally, refer to the `README.md` in the `hadaca3` GitHub repository.

**How to include an external file to be used in the submission script ?**
## How to include an external file to be used in the submission script?

It is possible to include an external file that is sourced in the submission script and correctly included in the zip file to be submitted on the Codabench platform.
Beware, when unziped the file 'program.R' has to be on the current directory and not inside a folder. Aditionnal files can in other folder with the correct relative path
Expand Down
6 changes: 4 additions & 2 deletions phase-0-smoothie/bundle/evaluation-and-scoring.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,13 +12,15 @@ To see your score:
By clicking on your submission in the submissions summary table, you will access to:

- details of your submission (downloaded)
- submitted files,

- submitted files
- prediction results (ingestion output)
- scoring results (scoring outputs)

- some execution logs
- a submission metadata edition menu

[3] Check the leaderboard in the *Results* menu
Check the leaderboard in the *Results* menu

To compare your score with other participants, go to the challenge page and navigate to the *Leaderboard* or *Results* section.
Here, you can see how your submission ranks.
Expand Down

0 comments on commit 7f450f0

Please sign in to comment.