Watts-Lab / team-process-map

MIT License

0 stars 4 forks source link

Testing folder featurizer file #225

Closed agshruti12 closed 1 month ago

agshruti12 commented 1 month ago

Pull Request Template: If you are merging in a feature or other major change, use this template to check your pull request!

Basic Info

What's this pull request about?

Added featurize.py file in the testing folder in order to compartmentalize test runs from other datasets. Fixed small bug in within_person_discursive_range.py to get the nan_vector.txt from a static directory, rather than dynamically assigned.

Feature Documentation

Did you document your feature? Make sure you do the following before you pull request!

[ ] Copy the Template. Go to the Feature Wiki and Copy/Paste the Feature Template into a new page.
[ ] Fill out the Template. Fill out the basic information for the feature in the template. Use the template to document your plan for implementation and major design decisions; if anything changes along the way, update the documentation as you go.
[ ] At the top of my feature, I indicate whether the feature is conversation level or chat level.

Code Basics

[ ] My feature is a .py file.
[ ] My feature uses snake case in the name. That means the name of the format is my_feature, NOT myFeature (camel case).
[ ] My feature has the name, NAME_features.py, where NAME is the name of my feature.
[ ] My feature is located in feature_engine/features.

Testing

[ ] I have thought about test cases for my features, with inputs and expected outputs.
[ ] I have linked to a location (e.g., .py or .ipynb) where I can run my test cases and show they work (inputs match expected outputs).

The location of my tests are here:

[PASTE LINK HERE]

If you check all the boxes above, then you ready to merge!