# Final Submissions Due Sunday

**URL:** <https://community.drivendata.org/t/final-submissions-due-sunday/5518>\
**Category:** Differential Privacy Temporal Map Challenge\
**Created:** [November 13, 2020, 7:41pm UTC](https://community.drivendata.org/t/final-submissions-due-sunday/5518 "2020-11-13T19:41:17Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![Christine\_Task](https://avatars.discourse-cdn.com/v4/letter/c/43a26b/32.png) [@Christine\_Task](https://community.drivendata.org/u/Christine_Task)\
**Post date:** [November 13, 2020, 7:41pm UTC](https://community.drivendata.org/t/final-submissions-due-sunday/5518/1 "2020-11-13T19:41:17Z")

</div>

You’re already aware of this, but just to be official about things-- Final submissions (with executable, source code, final write-up/proof, and code-guide) are due into to the prescreened leaderboard this sunday, 11/15. It’s a lovely weekend for privacy-preserving data science!

Let us know if you have any last minute questions, or run into any difficulty submitting. I’ll check in on this thread periodically over the weekend.

---

<div class="post-metadata">

**Author:** ![cuongk14](https://avatars.discourse-cdn.com/v4/letter/c/838e76/32.png) [@cuongk14](https://community.drivendata.org/u/cuongk14)\
**Post date:** [November 14, 2020, 8:09am UTC](https://community.drivendata.org/t/final-submissions-due-sunday/5518/2 "2020-11-14T08:09:37Z")

</div>

To confirm, the deadlines for submission is on Sunday, 8 PM EST time (NewYork time). Is that correct ?  
In case our methods differs with the previous submission, we need to submit both new write-up and new executable codes. We will try to submit new write-up clear, but in case there are some parts that are unclear, we still can explain (via email) after the deadline time. Is that correct.

---

<div class="post-metadata">

**Author:** ![glipstein](https://yyz2.discourse-cdn.com/flex028/user_avatar/community.drivendata.org/glipstein/32/920_2.png) [@glipstein](https://community.drivendata.org/u/glipstein)\
**Post date:** [November 14, 2020, 8:08pm UTC](https://community.drivendata.org/t/final-submissions-due-sunday/5518/3 "2020-11-14T20:08:51Z")

</div>

Hi @cuongk14 - Thanks for confirming. The deadline is indeed 8 PM EST on 11/15/20. Regardless of whether your approach has changed from your pre-screening submission, your final scoring submission should include everything outlined in the [Final Scoring section](https://www.drivendata.org/competitions/69/deid2-sprint-1-prescreened/page/263/#submissions) of the Problem Description.

Reviewers may follow up for clarifications if needed, but this is not required and you should make your materials as clear and complete as possible as a self-contained submission.

Good luck!

---

<div class="post-metadata">

**Author:** ![rmckenna](https://avatars.discourse-cdn.com/v4/letter/r/e36b37/32.png) [@rmckenna](https://community.drivendata.org/u/rmckenna)\
**Post date:** [November 14, 2020, 9:02pm UTC](https://community.drivendata.org/t/final-submissions-due-sunday/5518/4 "2020-11-14T21:02:48Z")

</div>

Our solution requires an extra dependency, we made a pull request on GitHub yesterday, but when can we expect that to be accepted/allow us to submit a valid submission to prescreened arena?

> <https://github.com/drivendataorg/deid2-runtime/pull/24/commits>

---

<div class="post-metadata">

**Author:** ![mshubhankar](https://avatars.discourse-cdn.com/v4/letter/m/8e8cbc/32.png) [@mshubhankar](https://community.drivendata.org/u/mshubhankar)\
**Post date:** [November 14, 2020, 9:59pm UTC](https://community.drivendata.org/t/final-submissions-due-sunday/5518/6 "2020-11-14T21:59:12Z")

</div>

We have a similar situation for our solution.  
I believe the Github repository instructions were for local testing only and does not have anything to do with the final contest code submission.  
However, the prescreened code .zip does not ask for the `py-cpu.yml` file, and it is confusing how our codes will run in their environment.

---

<div class="post-metadata">

**Author:** ![isms](https://yyz2.discourse-cdn.com/flex028/user_avatar/community.drivendata.org/isms/32/9_2.png) [@isms](https://community.drivendata.org/u/isms)\
**Post date:** [November 14, 2020, 10:49pm UTC](https://community.drivendata.org/t/final-submissions-due-sunday/5518/7 "2020-11-14T22:49:16Z")

</div>

@rmckenna The pull request has been accepted.

---

<div class="post-metadata">

**Author:** ![isms](https://yyz2.discourse-cdn.com/flex028/user_avatar/community.drivendata.org/isms/32/9_2.png) [@isms](https://community.drivendata.org/u/isms)\
**Post date:** [November 14, 2020, 10:56pm UTC](https://community.drivendata.org/t/final-submissions-due-sunday/5518/8 "2020-11-14T22:56:55Z")

</div>

The Docker environment that your code runs in is identical to that created from the master branch of the repo. That means if a certain Python requirement needs to be installed in the environment but is not in the .yml file, you will need to submit a pull request to get it changed.

Let’s assume you need package “statsmodels” but it’s not already in the .yml file. Obviously you can just make changes locally and rebuild your local version of the Docker container to get things working on your machine. But when your code tries to `import statsmodels` in the actual evaluation environment that we are running, it will fail because that isn’t in our official image yet. To get it into our official image you would submit a PR like [this one](https://github.com/drivendataorg/deid2-runtime/pull/22) on GitHub.

Does that make sense?

---

<div class="post-metadata">

**Author:** ![mshubhankar](https://avatars.discourse-cdn.com/v4/letter/m/8e8cbc/32.png) [@mshubhankar](https://community.drivendata.org/u/mshubhankar)\
**Post date:** [November 14, 2020, 11:37pm UTC](https://community.drivendata.org/t/final-submissions-due-sunday/5518/9 "2020-11-14T23:37:43Z")

</div>

Yup. That makes sense.  
I have added a pull request to the repository.

---

<div class="post-metadata">

**Author:** ![isms](https://yyz2.discourse-cdn.com/flex028/user_avatar/community.drivendata.org/isms/32/9_2.png) [@isms](https://community.drivendata.org/u/isms)\
**Post date:** [November 14, 2020, 11:56pm UTC](https://community.drivendata.org/t/final-submissions-due-sunday/5518/10 "2020-11-14T23:56:03Z")

</div>

@mshubhankar Hm, I don’t see any open pull requests – [https://github.com/drivendataorg/deid2-runtime/pulls](https://github.com/drivendataorg/deid2-runtime/pulls)

---

<div class="post-metadata">

**Author:** ![yuchaotao](https://avatars.discourse-cdn.com/v4/letter/y/ed8c4c/32.png) [@yuchaotao](https://community.drivendata.org/u/yuchaotao)\
**Post date:** [November 15, 2020, 3:13pm UTC](https://community.drivendata.org/t/final-submissions-due-sunday/5518/11 "2020-11-15T15:13:22Z")

</div>

The submission portal is currently closed. Will it reopen until 8 PM EST?

---

<div class="post-metadata">

**Author:** ![zschutzman](https://avatars.discourse-cdn.com/v4/letter/z/76d3ee/32.png) [@zschutzman](https://community.drivendata.org/u/zschutzman)\
**Post date:** [November 15, 2020, 3:14pm UTC](https://community.drivendata.org/t/final-submissions-due-sunday/5518/12 "2020-11-15T15:14:33Z")

</div>

Where are we supposed to make our final submissions? The prescreened leaderboard says that it’s closed.

---

<div class="post-metadata">

**Author:** ![Christine\_Task](https://avatars.discourse-cdn.com/v4/letter/c/43a26b/32.png) [@Christine\_Task](https://community.drivendata.org/u/Christine_Task)\
**Post date:** [November 15, 2020, 3:25pm UTC](https://community.drivendata.org/t/final-submissions-due-sunday/5518/13 "2020-11-15T15:25:20Z")

</div>

Hey all, apologies on that, we’ll get it sorted promptly!

---

<div class="post-metadata">

**Author:** ![glipstein](https://yyz2.discourse-cdn.com/flex028/user_avatar/community.drivendata.org/glipstein/32/920_2.png) [@glipstein](https://community.drivendata.org/u/glipstein)\
**Post date:** [November 15, 2020, 5:10pm UTC](https://community.drivendata.org/t/final-submissions-due-sunday/5518/14 "2020-11-15T17:10:49Z")

</div>

@yuchaotao @zschutzman Check now - should be fixed!

---

<div class="post-metadata">

**Author:** ![joiewu](https://avatars.discourse-cdn.com/v4/letter/j/a6a055/32.png) [@joiewu](https://community.drivendata.org/u/joiewu)\
**Post date:** [November 15, 2020, 8:03pm UTC](https://community.drivendata.org/t/final-submissions-due-sunday/5518/15 "2020-11-15T20:03:42Z")

</div>

Hi, we’re wondering how we would submit our proof of privacy, would it be separate from the containerized source code or would everything just be submitted through the prescreened arena?

---

<div class="post-metadata">

**Author:** ![isms](https://yyz2.discourse-cdn.com/flex028/user_avatar/community.drivendata.org/isms/32/9_2.png) [@isms](https://community.drivendata.org/u/isms)\
**Post date:** [November 15, 2020, 8:30pm UTC](https://community.drivendata.org/t/final-submissions-due-sunday/5518/17 "2020-11-15T20:30:05Z")

</div>

@joiewu Please check the [instructions](https://www.drivendata.org/competitions/69/deid2-sprint-1-prescreened/page/263/#submissions). Everything should be submitted through the Prescreened Arena.

---

<div class="post-metadata">

**Author:** ![Christine\_Task](https://avatars.discourse-cdn.com/v4/letter/c/43a26b/32.png) [@Christine\_Task](https://community.drivendata.org/u/Christine_Task)\
**Post date:** [November 15, 2020, 8:31pm UTC](https://community.drivendata.org/t/final-submissions-due-sunday/5518/18 "2020-11-15T20:31:26Z")

</div>

And don’t forget to include a code guide along with your updated privacy proof (see the overview of final submission contents here: [Preparing for the Nov 9th Sprint #1 Final Scoring Invitation](http://community.drivendata.org/t/preparing-for-the-nov-9th-sprint-1-final-scoring-invitation/5417) )

---

<div class="post-metadata">

**Author:** ![mshubhankar](https://avatars.discourse-cdn.com/v4/letter/m/8e8cbc/32.png) [@mshubhankar](https://community.drivendata.org/u/mshubhankar)\
**Post date:** [November 15, 2020, 8:36pm UTC](https://community.drivendata.org/t/final-submissions-due-sunday/5518/19 "2020-11-15T20:36:12Z")

</div>

It didn’t go through the last time. You should see it now.

---

<div class="post-metadata">

**Author:** ![joiewu](https://avatars.discourse-cdn.com/v4/letter/j/a6a055/32.png) [@joiewu](https://community.drivendata.org/u/joiewu)\
**Post date:** [November 15, 2020, 9:02pm UTC](https://community.drivendata.org/t/final-submissions-due-sunday/5518/20 "2020-11-15T21:02:50Z")

</div>

> [@Christine\_Task](#):
>
> And don’t forget to include a code guide along with your updated privacy proof (see the overview of final submission contents here: [Preparing for the Nov 9th Sprint #1 Final Scoring Invitation](http://community.drivendata.org/t/preparing-for-the-nov-9th-sprint-1-final-scoring-invitation/5417) )

Should the code guide be inside the privacy write up, or should it be separate file? Asking because the final submission instructions listed [here](https://www.drivendata.org/competitions/69/deid2-sprint-1-prescreened/page/263/#submissions), it states the former. But in the instructions posted on the forum, it states the later.

---

<div class="post-metadata">

**Author:** ![Christine\_Task](https://avatars.discourse-cdn.com/v4/letter/c/43a26b/32.png) [@Christine\_Task](https://community.drivendata.org/u/Christine_Task)\
**Post date:** [November 15, 2020, 9:18pm UTC](https://community.drivendata.org/t/final-submissions-due-sunday/5518/21 "2020-11-15T21:18:33Z")

</div>

Either one is just fine, as long as you get the required information covered someplace and we can find it easily.

---

<div class="post-metadata">

**Author:** ![isms](https://yyz2.discourse-cdn.com/flex028/user_avatar/community.drivendata.org/isms/32/9_2.png) [@isms](https://community.drivendata.org/u/isms)\
**Post date:** [November 15, 2020, 11:22pm UTC](https://community.drivendata.org/t/final-submissions-due-sunday/5518/22 "2020-11-15T23:22:52Z")

</div>

@mshubhankar PR has been accepted. The updated environment should be live in a few minutes.

[Next page](https://community.drivendata.org/t/final-submissions-due-sunday/5518.md?page=2)
