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

Adds datafile text field for Data File object query #15

Merged
merged 1 commit into from
Sep 17, 2024
Merged

Conversation

ktehranchi
Copy link
Collaborator

For querying Data File objects- I added the field that properly specifies the text of that datafile.

@codecov-commenter
Copy link

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.01%. Comparing base (e64620b) to head (89c72cf).

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #15   +/-   ##
=======================================
  Coverage   96.01%   96.01%           
=======================================
  Files           6        6           
  Lines         602      602           
=======================================
  Hits          578      578           
  Misses         24       24           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@pesap pesap merged commit 4ea5263 into main Sep 17, 2024
7 checks passed
@pesap pesap deleted the kt/datafile branch September 17, 2024 19:33
pesap pushed a commit to NREL/R2X that referenced this pull request Sep 18, 2024
…io Filtering (#38)

- Ensures ext data can be exported by cleansing it of data which cannot
be serialized
- Adds variable default property value for cases when variables do not
point to a data file
- Adds a separate datafile query in `get_model_data` to perform
filtering of datafiles where one data_file_tag can specify multiple
scenarios of datafiles. This is attached to this PR in plexosdb
NREL/plexosdb#15


NOTE: The current implementation for variable and data_file querying is
due for a refactor and cleanse... I will make a GitHub issue to specify
my thoughts on the best path forward. The current implementation works,
with one funky artifact- fields which have datafile scenarios specified,
will have their properties duplicated in the output of `get_model_data`.
This impacts very few fields since most scenarios are applied to
variables instead of datafiles.

No impact on results but I throw a warning when duplicate fields replace
each others data, but its all correct data replacing other correct data.
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.

3 participants