You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The provided conf.pth-files seem inconsistent with the provided dataset (cmp. Example below). The dataloader PartGraphShapesDataset uses the provided argument data_path for self.data_dir. Later, in the function __getitem__(...) the geometric data geo_data is loaded given the provided data path. Unfortunately, all .npz-files are located in Chair_dgeo directory and not in the Chair_dhier directory.
Is my assumption correct, that we need to manually update the configuration files to make it consistent with the provided dataset (or vice versa)?
It seems like the provided models need to be called with different evaluation scripts. eval.py uses the Chair_dgeo dir and eval_recon_sn.py uses Chair_dhier.
I start to suspect, that the derivation sn is used for StructureNet and the default evaluation scripts eval_vae_chair.sh runs a StructureNet example and not the model described in the published paper.
P.S.
I think it is the described SN-Mesh model, which uses a different dataset encoding/format.
Description:
The provided
conf.pth
-files seem inconsistent with the provided dataset (cmp. Example below). The dataloaderPartGraphShapesDataset
uses the provided argumentdata_path
forself.data_dir
. Later, in the function__getitem__(...)
the geometric datageo_data
is loaded given the provided data path. Unfortunately, all.npz
-files are located inChair_dgeo
directory and not in theChair_dhier
directory.Is my assumption correct, that we need to manually update the configuration files to make it consistent with the provided dataset (or vice versa)?
Example (exp_ae_Chair):
DSG-Net/code/datav1.py
Lines 464 to 465 in 6c6d117
The text was updated successfully, but these errors were encountered: