Update main to latest version for Feb 5, 2025, training and workshop#12
Merged
Conversation
Some sources were listed under ST2 and CKAN. This change explicitly names the individual sources. This will help with development because some organizations plan to add data to CKAN (Santa Fe expressed interest). So by explicitly naming the sources, we can better communicate to users where the data is coming from. Also, each source now has a link to where the data is hosted.
…comes from in config report There are some sources that only report water levels or analyte measurements. Prior to this update, for example, if the user requested water level data, the sources that only reported analyte measurements would say that data was being pulled from them. Now, the sources that only report water level or analyte measurements are separated so that the user can see where the data is coming from.
More sources will be added to CKAN, so it will no longer only be NM OSE Roswell data. So, NM OSE Roswell should be excluded/included based on the source, not that the data is hosted on CKAN.
Source names have been updated to indicate the organization and not
where the data is hosted (such as CKAN or ST2). State agencies have
also been prepended to OSE Roswell, ISC Seven Rivers, AMP, and DWB for
clarity.
Set source to False if the source is not in use. With this change, however,
the user can still set `--no-{source}` even if it doesn't report that
parameter. This will prevent unecessary crashes
This enables location data to be easily determined for all sites
Even if a site has only one measurement, its data will be in a standalone csv to have exports be standardized and findable
Saving the code for now in case we want to add it back
The user must now specify --output summary, --output timeseried_unfied, or --output timeseries_separated to explicitly request the output format
This change was done to have the output type and the functions that write the outputs have corresponding names
catalogItems are no longer returned in the location response. They are, however, still necessary to retrieve data and records. They are now explicitly found by querying the associated catalogRecords endpoint
This is done to standardize the way queries are called. This will allow for easier use of the command line interface and will make the code more readable.
This allows the user to call `weave {parameter name}` for ease of use,
rather than `weave parameter {parameter name}`
Now weave is called with `die weave {parameter}` instead of `weave {parameter}`
so that `sources` and `wells` are die commands.
This is done so that the tables are the same for both analytes and waterlevels. The information isn't changing, but the two table now have the same column headers
This is to get rid of floating point errors and keep results consistent with old data
This is done so that outputs don't override each other. All outputs are now found in directories titled `output`. If the output directory already exists, the output will be placed in a directory with the same name but with a number appended to the end. For example, if the output directory `output` already exists, the output will be placed in `output_1`. If `output_1` already exists, the output will be placed in `output_2`, and so on. die.log is also placed in the output directory so that each tool call is recorded in a single log file.
Before this only the DIE only accounted for results with "< MRL". If "< MDL" was in the result it would crash
This will make it so when the user invokes `die sources` the name will be printed instead of the object's memory location.
This commit changes the parameter options to lowercase for consistency and to make the code easier to maintain since we won't have to worry about case sensitivity. The inputs are still case insensitive
Waterlevels and analytes are now included in parameters and their export tables are now the same
convert_units returns the converted results and a warning message, so use the first element of the returned tuple
Version 0.3.1
Updated string padding for long names | publish to pypi on merges to Main
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
No description provided.