Closed rstoki closed 2 months ago
@rstoki thanks for pointing this out! So it looks like in your case, you don't have a BRATS dataset, and that's why fx plan init
fails. BRATS dataset could not be downloaded automatically by our scripts (as it done for other samples), because of legal issues since you need to register to obtain it. @itrushkin added special note in tf_2dunet
example, in order to have more meaningful output.
Hello @alexey-gruzdev, thank you for your reply, but I am afraid, that the proposed solution do not fully cover the problem. The fact is that I have BraTS dataset downloaded (2018, 2019 and 2020). And also, I have copied data folders in a proper place (in my opinion).
The problems are:
/raid/datasets/BraTS17/by_institution_NIfTY/*
So what needs to be resolved:
ad 1. How user will learn, that he needs to change paths in the data.yaml
file? How the user will know, that he should expect the first fx plan initialize
launch to fail, then he needs to change the content of data.yaml
and then run the fx plan initialize
again?
Or why not to use a local <workspace>/data
directory path in the template's data.yaml
? And the instructions for the users should explicitly mention where the BraTS data should be placed (and how).
ad 2. I have created a local structure in '{parent_dir} does not contain subdirectories.
" will not help the user anyhow. So what is the exact expected data format? Could it be written in the documentation, and/or the messages for the users?
ad 3. Have you tested the tutorial setup for the use-case in which the aggregator does not posses any data? Could the description how to setup the federation in such use-case be added to the documentation? How to work-around the total failure (crash) of fx plan initialize
in such case? Maybe you can add a new flag for fx plan initialize
which would disable the check for the data existence on the aggregator?
I would suggest to re-open the ticked, as it is (IMHO) not solved fully yet.
Screenshot of my data-folder structure, which I believe should be sufficient. Each BraTS20_Training_*\
folder is a 1:1 copy of the respective folder from BraTS 2020 dataset (i.e., containing 5 *.nii.gz files).
Having the exact same problem. Can someone please update, what is the 'right' structure to place the BraTS data?
Hi I also have the same error in plan/data.yaml FileNotFoundError: [Errno 2] No such file or directory: "'/raid/datasets/BraTS17/by_institution_NIfTY/1'", I changed the path but it does not work, Please Elaborate the CORRECT Directory structure and data folder paths
@rstoki @suleimank @dskhanirfan Thank you for being interested in our project! Please see the instructions on how to run BraTS training in #99. You still have to apply changes from the PR to your local code for training to work. I have tested it locally with BraTS19. Feel free to report issues if you still have any.
In this case, collaborator data_path
s must be .../federation-0.1/data/client-XX
.
Closing due to inactivity.
Describe the bug I am trying to setup a federation based on the '' following the documentation written here
The problem is, that the command
fx plan initialize
(as mentioned in the point 7) fails due to the checks for non-existing data folders. In default setup, it looks for path (which seems to be some 'leftovers' from your development environment), and even after specifying the local paths, it tries to look for them somewhere else.To Reproduce
Steps to reproduce the behavior:
tf_2dunet
export WORKSPACE_TEMPLATE=tf_2dunet
export WORKSPACE_PATH=${HOME}/projects/my-work/openfl-federations/federation_0.2
cd ${WORKSPACE_PATH}
fx workspace create --prefix ${WORKSPACE_PATH} --template ${WORKSPACE_TEMPLATE}
requirements.txt
are installed via pip.pip install -r requirements.txt
manually, as mentioned in the point 6, of the tutorial is not necessary => I would suggest thatfx
command will not update pip requirements.fx plan initialize
ends with the error:EXCEPTION : [Errno 2] No such file or directory: "'/raid/datasets/BraTS17/by_institution_NIfTY/1'"
plan/data.yaml
to point to the existing directories, it fails:Expected behavior 1) I would expect that all steps in the tutorial will succeed 2) I would expect that at the end of the tutorial, I will end up with a working federated environment 3) I would expect that the setup tools will not require access to the data (since the setup is performed on the aggregator, and the data are on the nodes, to which the aggregator does not have access to)
Screenshots If applicable, add screenshots to help explain your problem.
Error with defaults paths:
Error with modified and correct paths:
Desktop (please complete the following information):