PI code check list - Githubissues

AdrianaTorres / Irregular_Terrains

0 stars 1 forks source link

PI code check list #1

Open aremazeilles opened 4 years ago

aremazeilles commented 4 years ago

To be validated:

[x] 1. Readme available (purpose, install, use, acknowledgment)
[x] 2. identify test files (input --> output)
[x] 3. confirm main program structure (input, output)
[ ] 4. check input-output file format
[x] 5. insert docker generation files (TEC)
[x] 6. insert CI process (TEC)
[x] 7. insert docker hub secret (TEC)
[ ] 8. double check template spec again

AdrianaTorres commented 4 years ago

I have been working in this code. I tried it on my computer and it is working. I updated the algorithm of the MoS calculation because the version there was uploaded was not updated. Now I'm working in the algorithm to convert the Vicon output into EUROBENCH Data Format so that it can be the input for this code. As @DavidPintoFernandez said in other commentary, I found some parameters to include in the EUROBENCH Data Format. I will start an issue on that file so that they can be inlcuded.

aremazeilles commented 4 years ago

ok. I would suggest to shar also the code for going from Vicon to eurobench format. It could be also useful for others.

AdrianaTorres commented 4 years ago

Ok. I will upload it as soon as I have it.

aremazeilles commented 3 years ago

FYI, I created a fork of your repository, here. From there, I create manually a release, which automatically (CI) generates again the docker image, and bring it to the Docker hub This is from there that the server will get the docker image of your code.

Every time significant changes are done, I will bring it from your repo to the fork, create a release, and get this way an update of the docker image in Docker hub.

AdrianaTorres commented 3 years ago

Ok!