@jesusff and @miturbide I have created a branch named jupyterbook from changes from David's TFG repo PhantomAurelia/Atlas@adaeb9754012466134422b82b21dcbeb32b536d3 and merged changes from devel and main
Then all branches and repos are in sync, but I need from you to review them on jupyterbook branch before make them definitive and merge back to main and devel. The review it's needed because bibliography and cross-references and links to local repo files and notebooks has been refactored. Also existing README.md and repo directories haven renamed and refactored.
Because David's fork was an old fork, then we need to be sure any changes after it's already merged.
Also, the notebooks have been connected to the Jupyterhub at GANYMEDE, but some issues exist fetching the ATLAS repos. This needs to be analysed, because the repo probably needs a re-foundation ....
@jesusff and @miturbide I have created a branch named
jupyterbookfrom changes from David's TFG repo PhantomAurelia/Atlas@adaeb9754012466134422b82b21dcbeb32b536d3 and merged changes fromdevelandmainThen all branches and repos are in sync, but I need from you to review them on
jupyterbookbranch before make them definitive and merge back tomainanddevel. The review it's needed because bibliography and cross-references and links to local repo files and notebooks has been refactored. Also existingREADME.mdand repo directories haven renamed and refactored.Because David's fork was an old fork, then we need to be sure any changes after it's already merged.
Any commit to branch
jupyterbookit's been automatically building the book and publishing it at: https://santandermetgroup.github.io/ATLASAlso, the notebooks have been connected to the Jupyterhub at GANYMEDE, but some issues exist fetching the ATLAS repos. This needs to be analysed, because the repo probably needs a re-foundation ....