***WARNING***

With the current settings and hardware, you will be able to 
use an estimated image-size of 0 pixels during the last iteration...

...but your input box-size (image_size) is however 384. This means that 
you will likely run out of memory on the GPU(s), and will have to then re-start 
from the last completed iteration (i.e. continue from it) *without* the use of GPUs.
 


ERROR: out of memory in /public/EM/RELION/relion-4.0-dev/src/acc/acc_projector_impl.h at line 62 (error-code 2)
in: /public/EM/RELION/relion-4.0-dev/src/acc/cuda/cuda_settings.h, line 65
ERROR: 

A GPU-function failed to execute.

 If this occured at the start of a run, you might have GPUs which
are incompatible with either the data or your installation of relion.
If you 

	-> INSTALLED RELION YOURSELF: if you e.g. specified -DCUDA_ARCH=50
	   and are trying ot run on a compute 3.5 GPU (-DCUDA_ARCH=3.5), 
	   this may happen.

	-> HAVE MULTIPLE GPUS OF DIFFERNT VERSIONS: relion needs GPUS with
	   at least compute 3.5. You may be trying to use a GPU older than
	   this. If you have multiple generations, try specifying --gpu <X>
	   with X=0. Then try X=1 in a new run, and so on. The numbering of
	   GPUs may not be obvious from the driver or intuition. For a list
	   of GPU compute generations, see 

	   en.wikipedia.org/wiki/CUDA#Version_features_and_specifications

	-> ARE USING DOUBLE-PRECISION GPU CODE: relion was been written so
	   as to not require this, and may thus have unforeseen requirements
	   when run in this mode. If you think it is nonetheless necessary,
	   please consult the developers with this error.

If this occurred at the middle or end of a run, it might be that

	-> YOUR DATA OR PARAMETERS WERE UNEXPECTED: execution on GPUs is 
	   subject to many restrictions, and relion is written to work within
	   common restraints. If you have exotic data or settings, unexpected
	   configurations may occur. See also above point regarding 
	   double precision.
If none of the above applies, please report the error to the relion
developers at    github.com/3dem/relion/issues


=== Backtrace  ===
/public/EM/RELION/relion-4.0-dev/build/bin/relion_refine_mpi(_ZN11RelionErrorC2ERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES7_l+0x66) [0x4452e6]
/public/EM/RELION/relion-4.0-dev/build/bin/relion_refine_mpi() [0x6c5db0]
/public/EM/RELION/relion-4.0-dev/build/bin/relion_refine_mpi(_ZN12AccProjector9setMdlDimEiiiiiif+0x18f) [0x6c655f]
/public/EM/RELION/relion-4.0-dev/build/bin/relion_refine_mpi(_ZN14MlDeviceBundle22setupFixedSizedObjectsEv+0x1cd) [0x68709d]
/public/EM/RELION/relion-4.0-dev/build/bin/relion_refine_mpi(_ZN14MlOptimiserMpi11expectationEv+0x2afd) [0x467f4d]
/public/EM/RELION/relion-4.0-dev/build/bin/relion_refine_mpi(_ZN14MlOptimiserMpi7iterateEv+0x1b3) [0x477be3]
/public/EM/RELION/relion-4.0-dev/build/bin/relion_refine_mpi(main+0x5f) [0x43397f]
/lib64/libc.so.6(__libc_start_main+0xf5) [0x14c52b836555]
/public/EM/RELION/relion-4.0-dev/build/bin/relion_refine_mpi() [0x4365ef]
==================
ERROR: 

A GPU-function failed to execute.

 If this occured at the start of a run, you might have GPUs which
are incompatible with either the data or your installation of relion.
If you 

	-> INSTALLED RELION YOURSELF: if you e.g. specified -DCUDA_ARCH=50
	   and are trying ot run on a compute 3.5 GPU (-DCUDA_ARCH=3.5), 
	   this may happen.

	-> HAVE MULTIPLE GPUS OF DIFFERNT VERSIONS: relion needs GPUS with
	   at least compute 3.5. You may be trying to use a GPU older than
	   this. If you have multiple generations, try specifying --gpu <X>
	   with X=0. Then try X=1 in a new run, and so on. The numbering of
	   GPUs may not be obvious from the driver or intuition. For a list
	   of GPU compute generations, see 

	   en.wikipedia.org/wiki/CUDA#Version_features_and_specifications

	-> ARE USING DOUBLE-PRECISION GPU CODE: relion was been written so
	   as to not require this, and may thus have unforeseen requirements
	   when run in this mode. If you think it is nonetheless necessary,
	   please consult the developers with this error.

If this occurred at the middle or end of a run, it might be that

	-> YOUR DATA OR PARAMETERS WERE UNEXPECTED: execution on GPUs is 
	   subject to many restrictions, and relion is written to work within
	   common restraints. If you have exotic data or settings, unexpected
	   configurations may occur. See also above point regarding 
	   double precision.
If none of the above applies, please report the error to the relion
developers at    github.com/3dem/relion/issues


in: /public/EM/RELION/relion-4.0-dev/src/image.h, line 522
ERROR: 
ERROR: trying to read image with empty file name!
=== Backtrace  ===
/public/EM/RELION/relion-4.0-dev/build/bin/relion_refine_mpi(_ZN11RelionErrorC2ERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES7_l+0x66) [0x4452e6]
/public/EM/RELION/relion-4.0-dev/build/bin/relion_refine_mpi() [0x5e7738]
/public/EM/RELION/relion-4.0-dev/build/bin/relion_refine_mpi(_ZN7MlModel20initialiseFromImagesE8FileNamebR10ExperimentRbS3_S3_dbbbb+0xafa) [0x5f153a]
/public/EM/RELION/relion-4.0-dev/build/bin/relion_refine_mpi(_ZN11MlOptimiser17initialiseGeneralEi+0x59e) [0x63958e]
/public/EM/RELION/relion-4.0-dev/build/bin/relion_refine_mpi(_ZN14MlOptimiserMpi10initialiseEv+0xa1) [0x46e8d1]
/public/EM/RELION/relion-4.0-dev/build/bin/relion_refine_mpi(main+0x55) [0x433975]
/lib64/libc.so.6(__libc_start_main+0xf5) [0x14a8dc7493d5]
/public/EM/RELION/relion-4.0-dev/build/bin/relion_refine_mpi() [0x4365ef]
==================
ERROR: 
ERROR: trying to read image with empty file name!