Skip to content
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

'PJFDataset' object has no attribute 'geek_direct' Error #3

Open
benm-dev opened this issue Nov 12, 2022 · 11 comments
Open

'PJFDataset' object has no attribute 'geek_direct' Error #3

benm-dev opened this issue Nov 12, 2022 · 11 comments

Comments

@benm-dev
Copy link

benm-dev commented Nov 12, 2022

Hello when i run DPGNN with the kaggle jobrec dataset i get this error
image

i am using recbole 1.0.0 and all the requirements are correct

@flust
Copy link
Collaborator

flust commented Nov 12, 2022

Could you please show me your configuration file? (overall.yaml and jobrec.yaml)

@benm-dev
Copy link
Author

okay so the error has changed to this now i upgraded my recbole version
image

Here are the config files
image

image

@flust
Copy link
Collaborator

flust commented Nov 12, 2022

I fixed the problem, you can pull the latest code to try again.

This problem is because in the latest version of RecBole, there is a default configuration file "sample.yaml" for all dataset and in this file, the "DIRECT_FIELD" is defined as "field".

We're also doing some code updates and maintenance recently and If you have any more questions, please feel free to contact me~

@benm-dev
Copy link
Author

benm-dev commented Nov 13, 2022

Hey so i am not receiving the direct error anymore but I am now receiving this error again

image

Here are the config files again
image

image

@flust
Copy link
Collaborator

flust commented Nov 14, 2022

This means that the model DPGNN requires active behavior on both sides in the data, and therefore, it requires the data to have the feature "DIRECT_FIELD".(Refer to the original paper, it need directed behavior to construct the interaction graph)
In order to achieve this, in the "DIRECT_FIELD" feature, we use '0' to represent the user's active behavior("geek_direct" in the code), and "1" to represent the employer's active behavior, which may not available in the jobrec dataset.

@flust
Copy link
Collaborator

flust commented Nov 15, 2022 via email

@benm-dev
Copy link
Author

okay thanks so much so there aren't any other English datasets I could use with the DPGNN Model

@flust
Copy link
Collaborator

flust commented Nov 16, 2022 via email

@benm-dev
Copy link
Author

hey so i am now trying to run DPGNN with the zillhan dataset and i am still receiving the same error but zillhan does have the feature direct filed
image

@benm-dev
Copy link
Author

benm-dev commented Jan 16, 2023

i also receive this error when i run APJFNN with zhilian
image

do you guys have any other datasets that could be used with this
like the boss_search dataset

@flust
Copy link
Collaborator

flust commented Feb 9, 2023

Sorry it took so long to reply.

We check the 'yaml' file and fix bugs in the code.
We updated the code and provided configuration files that can be run directly with dataset zhilian.

For the model DPGNN, the experimental datasets we used are not available for the privacy policy of the company.
In order for you to run the model code properly, we have modified the zhilian data processing procedure.
Before that, it takes a long time for computing bert encoding before. So in order to run at an acceptable time, we just keep a small part of it. If you don't need the bert part, just set it to false in the 'DPGNN.yaml'.
In addition, We randomly added directional information to this dataset to run DPGNN correctly.
You can now run the DPGNN model directly under the right environment.

Besides, this dataset is just an example and the features it contains may not necessarily fit all models.
For better experiments, we recommend that you work with your own dataset and the format can be referred to zhilian.

Moreover, most bugs are due to configuration files not being set up properly(including 'overall.yaml', 'dataset/zhilian.yaml' and 'model/DPGNN.yaml') like the bug of "direct_field". You can check them first if you run into any other problems.

Sorry again for taking so long to reply.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants