Team-comm-tools

Latest version: v0.1.4.post2

Safety actively analyzes 681775 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 1 of 2

0.1.4.post2

Defaults in FeatureBuilder were incorrectly specified, leading to undesirable behavior when relying on the default values of the `vector_directory`. The format is now correct.

0.1.4.post1

Post-Release: Update README with new function call example for `output_file_base`.

0.1.4

1. **Progress Bars:** Loading bar during feature generation helps users better understand the status of the features/estimated completion time.
2. **Vector Updates:** Vectors are now batched for faster generation.
3. Vectors are now generated by default WITH punctuation, allowing for more accurate gauging of sentiment.
4. **Denormalizing LIWC:** LIWC is no longer normalized as a rate (i.e., per 100 words), and is instead returned as raw count per utterance. This ensures that the aggregated values of LIWC are more sensible/interpretable. ([306](https://github.com/Watts-Lab/team_comm_tools/issues/306))
5. **Labeling Feature Columns with the Source:** Politeness and Receptiveness features are labeled with the source (e.g., “politeness_convokit” and “receptiveness_yeomans”) ([300](https://github.com/Watts-Lab/team_comm_tools/issues/300)).
6. **Easy Access to List of Generated Features:** There is now an easier way to access the names of features and columns generated (by using my_feature_builder.feature_names) as well as to access the names of the columns generated (`my_feature_builder.chat_features`, `my_feature_builder.conv_features_base`, `my_feature_builder.conv_features_all`) ([304](https://github.com/Watts-Lab/team_comm_tools/issues/304))
7. **More Defaults for Input Params:** Input parameters have defaults, so it’s easier than ever to use the FeatureBuilder (all you need is the input dataframe). ([286](https://github.com/Watts-Lab/team_comm_tools/issues/286))
8. **One File Path to Rule Them All:** You can generate files at all three levels automatically using the “output_file_base” parameter, rather than separately specifying the output paths for all three files. This also creates a more streamlined workaround than the current way of specifying paths, which is a bit counterintuitive. (However, we maintain full backwards-compatibility; this patch release does not change the behavior in which outputs are saved in the `output/chat/...` path. ([299](https://github.com/Watts-Lab/team_comm_tools/issues/299)).
9. **Website Auto-Updating:** The project website will now auto-update alongside changes in dev, and documentation has been updated alongside these changes.
10. **Other Bug Fixes:** Bug fixes for NLTK punkt: [302](https://github.com/Watts-Lab/team_comm_tools/issues/302)

0.1.3

[v0.1.3](https://pypi.org/project/team-comm-tools/0.1.3/) - 2024-09-16

Added
- **Documentation**: Updated documentation and our requirement files

Fixed
- **Dependency**: Our current required version of torch (2.4.0) has a known issue that causes an error for Windows users; we have updated the requirement to 2.4.1 to resolve this issue.

What's Changed
* Patch Release 0.1.3 by xehu in https://github.com/Watts-Lab/team_comm_tools/pull/292


**Full Changelog**: https://github.com/Watts-Lab/team_comm_tools/compare/v0.1.2...v0.1.3

0.1.2

Security patch ensuring privacy of LIWC lexicons.

0.1.1

* Yuxuan/dependency issue by xehu and sundy1994 in https://github.com/Watts-Lab/team_comm_tools/pull/275


**Full Changelog**: https://github.com/Watts-Lab/team_comm_tools/compare/v0.1.0...v0.1.1

Page 1 of 2

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.