RRL: Recommendation Reverse Learning
Authors: Xiaoyu You, Jianwei Xu, Mi Zhang, Zechen Gao, Min Yang
AAAI 2024 | Conference PDF | Archive PDF | Plain Text | LLM Run Details
| Reproducibility Variable | Result | LLM Response |
|---|---|---|
| Research Type | Experimental | We conduct experiments on two representative recommendation models and three public benchmark datasets to verify the efficiency of RRL. |
| Researcher Affiliation | Academia | Xiaoyu You, Jianwei Xu, Mi Zhang*, Zechen Gao, Min Yang* Fudan University 17212010047@fudan.edu.cn, 21210240379@m.fudan.edu.cn, mi zhang@fudan.edu.cn, 22210240151@m.fudan.edu.cn, m yang@fudan.edu.cn, |
| Pseudocode | No | The paper provides mathematical equations for its framework but does not include structured pseudocode or an algorithm block. |
| Open Source Code | No | The paper does not provide concrete access to source code for the methodology described. |
| Open Datasets | Yes | We use three real-world recommendation datasets, i.e., Gowalla (Liang et al. 2016), Yelp2018 (Wang et al. 2019), and Movilens-1m (dubbed as ML-1M)3 which are widely used for benchmarking. 3https://grouplens.org/datasets/movielens/1m/ |
| Dataset Splits | Yes | Each dataset is split into training/validation/testing sets by the ratio of 70/10/20%. Validation sets are used to tune hyper-parameters. |
| Hardware Specification | No | The paper does not provide specific hardware details (exact GPU/CPU models, processor types, or memory amounts) used for running its experiments. |
| Software Dependencies | No | The paper does not provide specific ancillary software details (e.g., library or solver names with version numbers) needed to replicate the experiment. |
| Experiment Setup | Yes | The depth Light GCN is set to 3, and the size of the embeddings of recommendation models is set as 128. For each baseline model, we mostly follow the suggested experimental settings and set the hyper-parameters as suggested in the original papers, including but not limited to the learning rate, the regularization coefficient, etc. For shilling attacks used to verify removal completeness, we randomly choose an unpopular item as the target item to measure #Rec, and the number of malicious users is set as 10% of all users. |