Closed schlich closed 3 days ago
Hi @schlich! Welcome to pyOpenSci.
I can tell you have put a ton of work into PsychoAnalyze. Everything you have so far looks great! Without bringing my own bias into the review: I've done some work in psychometrics and I've wanted there to be a Python package developed like this for some time.
That said, there's some things we need you to address before we start the review.
Specifically, we need much more detail in the documentation.
Below I have put in the Editor in Chief checks.
You will see you have passed almost all of them with flying colors!
Except for the checks about documentation.
I have provided more detail about what we need in my comments following the checklist.
Please let me know if those are clear, and please check our Python packaging guide for more information.
Once we get those things addressed, I will be more than happy to find an editor and reviewers to help you bring PsychoAnalyze to the next level.
import package-name
.README.md
file with clear explanation of what the package does, instructions on how to install it, and a link to development instructions.CONTRIBUTING.md
file that details how to install and contribute to the package.Code of Conduct
file.YAML
header of the issue (located at the top of the issue template).psychoanalyze
--and a list of features. See for example this readme for what I mean by concrete examples: https://github.com/garethjns/PsychometricCurveFitting, and the pandera docs for an example of lists of features: https://pandera.readthedocs.io/en/stable/. We need to have some initial description of what the package does, who it is for, and how it provides them what they need (features/functionality) before we start the review--doesn't have to be perfect but it has to be there.>>> import psychoanalyze
>>> dir(psychoanalyze)
['__builtins__', '__cached__', '__doc__', '__file__', '__loader__', '__name__', '__package__', '__path__', '__spec__']
Is this intentional?
The package level docstring describes top-level modules here:
https://github.com/psychoanalyze/psychoanalyze/blob/0a28562dd9bbe267d62fe01608276e96d2d13127/psychoanalyze/__init__.py#L17
Why not import those inside psychoanalyze/__init__.py
? To avoid making users import things directly, and to help them understand your intended API.
Hi @schlich just checking back. Please let me know if there's anything we can clear up about the initial checks.
Once those requirements are taken care of, I'll be happy to get started finding an editor and reviewers.
Hi Dave, thanks for the follow up, sorry for the delay! And thanks for the checks. To be honest, this submission was put out slightly earlier than anticipated due to graduation requirements for my PhD program. I'm focused on defending in the short term, but I anticipate being able to make these changes within the next few weeks-to-couple-months-ish. All great feedback, thank you! If this slight delay causes any issues with the process timeline, please let me know.
Very understood! I haven't forgot the, uh, fun of defending just yet.
Thank you for your reply -- let's keep this open for now. I will change the status to "on hold" and we'll give it a couple months.
Good luck with the PhD defense! If your maintainer chops are any indication, I think you'll be alright 🙂
hi everyone 👋🏻 i'm going through old / on hold issue where there has been no activity for over a year and closing them. It looks like this review did not fully begin. @schlich if you wish to kick off a review again in the future you are more than welcome to. I hope all is well!
I'll be back, no worries! Thanks!
Submitting Author: Tyler Schlichenmeyer (@schlich) All current maintainers: (@schlich) Package Name: psychoanalyze One-Line Description of Package: Interactive simulation & analysis for psychophysics. Repository Link: https://github.com/psychoanalyze/psychoanalyze Version submitted: 1.0.0a1 Editor: TBD
Reviewer 1: TBD
Reviewer 2: TBD
Archive: TBD
Version accepted: TBD Date accepted (month/day/year): TBD
Code of Conduct & Commitment to Maintain Package
Description
PsychoAnalyze is a data manipulation and visualization toolset to assist researchers in the broad domain of psychophysics and other areas of behavioral psychology and neuroscience. It provides methods and infrastructure for commonly performed analyses in the field, which includes curve fitting to the psychometric function as a model of sensory threshold. Powered by the
psychoanalyze
package, the project also provides a web-accessible interactive visualization dashboard built with the Dash framework and a self-hosted JupyterHub instance with executable example tutorials notebooks. Future iterations of work will incorporate more complex analyses, with a hierarchical Bayesian inferencing pipeline being the target for beta release.Scope
Please indicate which category or categories. Check out our package scope page to learn more about our scope. (If you are unsure of which category you fit, we suggest you make a pre-submission inquiry):
Domain Specific & Community Partnerships
Community Partnerships
If your package is associated with an existing community please check below:
For all submissions, explain how the and why the package falls under the categories you indicated above. In your explanation, please address the following points (briefly, 1-2 sentences for each):
Technical checks
For details about the pyOpenSci packaging requirements, see our packaging guide. Confirm each of the following by checking the box. This package:
Publication Options
JOSS Checks
- [x] The package has an **obvious research application** according to JOSS's definition in their [submission requirements][JossSubmissionRequirements]. Be aware that completing the pyOpenSci review process **does not** guarantee acceptance to JOSS. Be sure to read their submission requirements (linked above) if you are interested in submitting to JOSS. - [x] The package is not a "minor utility" as defined by JOSS's [submission requirements][JossSubmissionRequirements]: "Minor ‘utility’ packages, including ‘thin’ API clients, are not acceptable." pyOpenSci welcomes these packages under "Data Retrieval", but JOSS has slightly different criteria. - [x] The package contains a `paper.md` matching [JOSS's requirements][JossPaperRequirements] with a high-level description in the package root or in `inst/`. - [ ] The package is deposited in a long-term repository with the DOI: *Note: JOSS accepts our review as theirs. You will NOT need to go through another full review. JOSS will only review your paper.md file. Be sure to link to this pyOpenSci issue when a JOSS issue is opened for your package. Also be sure to tell the JOSS editor that this is a pyOpenSci reviewed package once you reach this step.*Are you OK with Reviewers Submitting Issues and/or pull requests to your Repo Directly?
This option will allow reviewers to open smaller issues that can then be linked to PR's rather than submitting a more dense text based review. It will also allow you to demonstrate addressing the issue via PR links.
Confirm each of the following by checking the box.
Please fill out our survey
P.S. Have feedback/comments about our review process? Leave a comment here
Editor and Review Templates
The editor template can be found here.
The review template can be found here.