Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft | prototype for a rule optimiser #5

Open
wants to merge 37 commits into
base: main
Choose a base branch
from

Conversation

MartiPuigV
Copy link
Contributor

Loads a rule (coming from the miniscanner or real datascanner, and returns a clean rule without redundacnies and useless expressions. Doesn't work 100%, but does the trick for most complicated and repetitive rules.

MartiPuigV and others added 30 commits July 3, 2024 14:49
…m height and causing it to stretch. It also does not reload the page, causing a useless miniscan() from the backend.
… for text input field is hard-coded at 2000 in checkTextSize.js
…js file that handled that before as well as prior translations.
…s/miniscanner/miniscan_results.html

Co-authored-by: Alexander Faithfull <[email protected]>
…d test_miniscanner now have variable and function names in snake_case.
…so fixed the redundant class problem in the test file.
…ry in advance for anyone reading this. It works tho on most edge cases.
@MartiPuigV
Copy link
Contributor Author

Usage : input file with the rule given by the user, and output file for temporary storage. It doesn't get deleted yet for testing purposes and to check out the results, but can probably be stored in some tmp/tmpdir later on and removed. Check optimiser_usage.py for how to run the rule optimiser.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant