-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
error about training code #2
Comments
It seems one of the dataloader's outputs is of type trimesh.caching.TrackedArray instead the expected type of numpy.ndarray. This is most likely caused by the wrong version of trimesh installed. It's not possible for me to tell which specific item from the dataloader is wrong with your information. Can you check which version of trimesh you installed in your environment? On the other hand, the trimesh.caching.TrackedArray is most likely a result of the following lines: arah-release/im2mesh/data/zju_mocap.py Line 486 in d3bc1c3
arah-release/im2mesh/data/zju_mocap.py Line 534 in d3bc1c3
Can you add |
One more question, does training with a single gpu and four gpus have any effect on the performance of the model? |
To reproduce the numbers reported in the paper you need 4 GPUs, or more specifically, a batch size of 4 - the current implementation allows only one batch per GPU, so using a batch size of 4 is equivalent to using 4 GPUs Training with a single GPU (a batch size of 1) could result in degraded accuracy and may lead to unstable gradients during training |
Hi! I would like to ask you about the calculation of the geometric evaluation metrics, i.e. CD and NC. The paper states that the pseudo-ground-truth geometry is used in the calculation of these metrics. I would like to ask how these pseudo-ground-truth geometries are obtained. |
We used NeuS with all cameras to construct pseudo-ground-truth. For reproducibility, please use the commit 2708e43ed71bcd18dc26b2a1a9a92ac15884111c - they fixed some minor bug for background NeRF in a later commit; this shouldn't affect the final results in any significant way, but I did not test their new commit. The official NeuS code should work out of the box for ZJU-MoCap data. You only need to preprocess ZJU's camera parameters. I've attached my preprocessing script as follows, the interface should be self-explanatory. Note this works on raw ZJU-MoCap dataset, not the dataset preprocessed by our script.
|
Thanks! |
I encountered a programming error in
arah-release/train.py
Line 135 in d3bc1c3
TypeError: default_collate: batch must contain tensors, numpy arrays, numbers, dicts or lists; found <class 'trimesh.caching.TrackedArray'>
The text was updated successfully, but these errors were encountered: