Add USENIX and ACM Styles to SciencePlots (Fixes #129) #130
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request Description
Title: Add Styles for USENIX and ACM Conferences
Related Issue: New style for USENIX and ACM
Overview:
This pull request introduces two new style files for the USENIX and ACM conferences within the SciencePlots repository. These styles are designed for use with Matplotlib and offer configurations tailored specifically for two-column journal formats, addressing the request mentioned in Issue #129.
Changes Made:
Created New Style Files:
usenix.mplstyle
: This file includes settings optimal for USENIX conference submissions, allowing users to generate plots that meet the required dimensions and font specifications.acm.mplstyle
: Similar to the USENIX style, this file is tailored for ACM conferences with its own set of configurations.Specifications Include:
Updated
.gitignore
:.aider*
to ensure that unnecessary files are not tracked in the repository.Example Output:
An example plot generated from the newly added USENIX style can be visualized below:
Next Steps:
Note:
This contribution addresses the request in Issue #129, and upon merging, it will resolve this issue.
Fixes #129
Thank you for considering this pull request! Looking forward to your feedback.