search

IN-CORE / incore-docs

IN-CORE documentations
9 stars 13 forks source link

Release 4.8.2 #332

Closed longshuicy closed 5 months ago

robkooper commented 5 months ago

can this be executed in a container notebook instead of @Vismayak machine, notice the path to the files. I want to make sure this is what the user will see when they execute and it works as expected in the notebook docker image.

navarroc commented 5 months ago

can this be executed in a container notebook instead of @Vismayak machine, notice the path to the files. I want to make sure this is what the user will see when they execute and it works as expected in the notebook docker image.

I'm not sure what you mean by executed in a container notebook. Do you mean executed on something like IN-CORE lab so the paths are similar to what a user would see?

robkooper commented 5 months ago

correct, and also that would make sure it is the same environment the user will use, not a conda environment that is on the developers machine.

longshuicy commented 5 months ago

correct, and also that would make sure it is the same environment the user will use, not a conda environment that is on the developers machine.

sorry late to the game. What do we need to do for that?

navarroc commented 5 months ago

IMO - we open an issue and for the next release, we run all the example testbed notebooks on incore-lab to get a consistent user path.

longshuicy commented 5 months ago

IMO - we open an issue and for the next release, we run all the example testbed notebooks on incore-lab to get a consistent user path.

Ah I think I understand. Some of the notebook output cell has local paths? Yes agree we should use incore-lab or a "anounmous" environment to run the notebooks that have outputs. Will create a task.