-
Notifications
You must be signed in to change notification settings - Fork 3
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
An Error Occurs when reproducing CAF & A question about Data Normalization #3
Comments
Sorry for the late reply. I am busy these days. Now I have time to check this issue. |
I will solve it this weekend. Sorry for the waiting. |
Hi. |
Sorry for the waiting. Can you come up with a PR and I can review the changes? |
Hi, I haven't changed anything, since I'm not so familiar with Pytorch-Lightning. |
Hello, I also encountered the same problem, has it been solved now? |
@dalianshiyi Not yet. Can you post the reproduce guidelines to help me locate the problem? |
Hi.
1, An Error Occurs when reproducing CAF
An error occurs when I reproduce CAF, in line
trainer.fit(model, datamodule=data_module)
:2. A question about Data Normalization
And I think this line$s$ to $s\in \lbrace0,1 \rbrace$ . Since this is done before the normalization.
self.data.x[:, sens_idx] = self.data.sens
does not re-asign the sensitive valueTo be specific, in the implementation of torch_geometric.data.Dataset,
which means that:
when executing
dataset = Bail(...,transform=NormalizeFeatures())
, featuresdataset[0].x
are not normalized.when executing
data = dataset[0]
(i.e. accessing data object), featuresdata.x
are implicitly normalized.Yet this line$s$ : $s \in (0,1)$ . e.g. might be $0.18$ , $0.23$ depending on other features' values of this individual.
self.data.x[:, sens_idx] = self.data.sens
is executed indataset = Bail(...,transform=NormalizeFeatures())
, in other words, the re-asigning of sensitive values are executed beform feature normalization.And you use Row-Normalization (
torch_geometric.transforms.NormalizeFeatures
) in your code, resulting in a variety values ofThe text was updated successfully, but these errors were encountered: