v0.1.0

[ericdrosas87]

What's Changed

• Epo 6783 by @ericdrosas87 in Epo 6783 #1
• Adding DP0.2 cutout option by @clareh in Adding DP0.2 cutout option #2
• Updated notes and added debugging by @clareh in Updated notes and added debugging #3
• Removed duplicate info messages, now added steps by @ericdrosas87 in Removed duplicate info messages, now added steps #4
• Abstracted away citSci SDK to its own notebook by @ericdrosas87 in Abstracted away citSci SDK to its own notebook #5
• Changed logging style of errors and warnings by @ericdrosas87 in Changed logging style of errors and warnings #6
• Fixed SDK notebook bug that caused a stack trace by @ericdrosas87 in Fixed SDK notebook bug that caused a stack trace #7
• Added functionality for creating manifest and by @ericdrosas87 in Added functionality for creating manifest and #8
• Added changelog and updated SDK notebook by @ericdrosas87 in Added changelog and updated SDK notebook #11
• Utils by @beckynevin in Utils #33
• Added flexible manifest creation/modification by @ericdrosas87 in Added flexible manifest creation/modification #36
• Fetch classifications by @beckynevin in Fetch classifications #39
• Removed unnecessary data type variable by @ericdrosas87 in Removed unnecessary data type variable #46
• Clarifying pedagogy by @beckynevin in Clarifying pedagogy #48
• Epo 8274 by @ericdrosas87 in Epo 8274 #49
• Epo 8318 by @ericdrosas87 in Epo 8318 #51
• Updated path to key by @ericdrosas87 in Updated path to key #54
• adding details in README file by @beckynevin in adding details in README file #50
• Temporarily removing tabular notebook by @ericdrosas87 in Temporarily removing tabular notebook #55
• Updated the .gitignore based on pcw feedback by @ericdrosas87 in Updated the .gitignore based on pcw feedback #56
• Removed depr notebooks, pip install citsci package by @ericdrosas87 in Removed depr notebooks, pip install citsci package #52
• Referencing new package and import namespace by @ericdrosas87 in Referencing new package and import namespace #65
• Added code to clas. cell to render panda df by @ericdrosas87 in Added code to clas. cell to render panda df #72

New Contributors

• @clareh made their first contribution in Adding DP0.2 cutout option #2
• @beckynevin made their first contribution in Utils #33

Full Changelog: https://github.com/lsst-epo/citizen-science-notebooks/commits/v0.1.0

---

This discussion was created from the release v0.1.0.

[ericdrosas87]

@clareh @bnord @jsv1206 @beckynevin I am going to start using releases to denote when major functionality has been implemented. In the case of this release, Clare and I have been chatting with Chris of Zooniverse about how best to audit and detect similar data across Zooniverse projects.

In this release, you may notice additional output in the send_image_data() cell:

If a match has been found - based on object ID - between the data you just sent to Zooniverse and data that has already been sent to Zooniverse for other projects, you will receive a message indicating between 0 and 1 the percentage match.

This is still very much a work-in-progress and feedback is welcome and anticipated, and I plan to iterate on the development of this feature moving forward.

Let me know if you have any questions!

[jsv1206]

Any reason to have a percentage match instead of 0/1 ? Is this because it is looking for matches for all the object IDs within a dataset being sent?

Should we check for matches among the different subject sets within the same project ? This is in case we are planning to send data in chunks into the same project.

[ericdrosas87]

Any reason to have a percentage match instead of 0/1 ? Is this because it is looking for matches for all the object IDs within a dataset being sent?

Correct - it's looking for any matches on object ID in the current dataset (subject set) being transferred against all data already sent to the Zooniverse using the citSci pipeline - except for the current RSP user's previous datasets.

Should we check for matches among the different subject sets within the same project ?

There's no reason why the code can't be changed to also match against the current user's previous datasets, I think it's a UX question - is that useful to the PI? etc.

This is in case we are planning to send data in chunks into the same project.

I defer to what @clareh, @bnord, @beckynevin and yourself think is most useful and I can code as such.