1. General Rules
1.1 One Account per Participant
You cannot sign up to Kaggle from multiple accounts and therefore you cannot submit from multiple accounts.

1.2 No Private Sharing Outside Teams
Privately sharing code or data outside of teams is not permitted. It's okay to share code if made available to all participants on the forums or by publishing a Kaggle Notebook.

1.3 Team Mergers
Team mergers are allowed and can be performed by the team leader. Team merges will not be allowed after the Team Merger Deadline. In order to merge, the combined team must have a total submission count less than or equal to the maximum allowed as of the merge date. The maximum allowed is the number of submissions per day multiplied by the number of days the competition has been running.

1.4 Team LimitsThe maximum team size is 5 members.

1.5 Submission LimitsYou may submit a maximum of 5 entries per day. You may select up to 2 final submissions for judging.

2. Competition Timeline
Start Date: [Insert Start Date]

Team Merger Deadline: [Insert Date - typically 1 week before close]

Entry Deadline: You must accept the competition rules before this date in order to compete. [Insert Date - typically 1 week before close]

End Date (Final Submission Deadline): [Insert End Date]

All deadlines are at 11:59 PM UTC on the corresponding day unless otherwise noted. The competition organizers reserve the right to update the contest timeline if they deem it necessary.

3. Eligibility
This competition is open to all registered Kaggle users. Employees, interns, contractors, and official office-holders of the Host organization (if applicable), as well as their immediate families, are ineligible to participate or win prizes.

4. Data Usage and Restrictions
4.1 External Data
Unless otherwise specified on the Data Page, participants may not use data other than the provided diamonds.csv dataset to develop and test their models and submissions. The use of external data is strictly prohibited unless publicly posted in the official competition forum and explicitly approved by the competition organizers.

4.2 Data Security
Participants must agree to use the provided dataset solely for the purpose of participating in this competition. Participants may not use the dataset for commercial purposes or any other academic/research purposes outside the scope of this Kaggle challenge.

5. Evaluation and Leaderboard
5.1 Metric
Submissions are evaluated on Root Mean Squared Error (RMSE) between the predicted diamond price and the actual diamond price.

5.2 Submission Format
For every diamond in the dataset, submission files should contain two columns: id and price. The id corresponds to the unique identifier for each diamond in the test set, and price should be your predicted value in USD. The file should contain a header and have the following format:

Extrait de code
id,price
1,326.50
2,350.00
3,410.25
...
5.3 Public and Private Leaderboard
The leaderboard is split into a Public Leaderboard and a Private Leaderboard. The Public Leaderboard is calculated on approximately 30% of the test data. The Private Leaderboard is calculated on the remaining 70% of the test data. The final competition standings will be based solely on the Private Leaderboard.

6. Code Requirements
6.1 Open Source
To be eligible for prizes (if applicable), the winning teams must provide the competition host with the final model software code and documentation. The code must be licensed under a recognized Open Source Initiative (OSI) license (e.g., MIT, Apache 2.0).

6.2 Reproducibility
The provided code must be fully reproducible. The organizers must be able to run the code and reproduce the exact submissions that were selected for final scoring. Hardware specifications, random seeds, and environment dependencies (e.g., requirements.txt or a Dockerfile) must be clearly documented.

7. Winner Obligations
To claim a prize, the winning participants must:

Deliver the final model's software code as used to generate the winning submission and associated documentation.

Sign and return all prize acceptance documents as may be required by the Sponsor or Administrator.

Provide a brief, high-level summary of the methodology used to achieve the winning score, which will be shared with the Kaggle community.

8. Disqualification
The Host and Kaggle reserve the right to disqualify any participant or team from the Competition if they reasonably believe that the participant has attempted to undermine the legitimate operation of the Competition by cheating, deception, or other unfair playing practices, or abuses, threatens, or harasses any other participants, Host, or Kaggle.