-
Notifications
You must be signed in to change notification settings - Fork 13
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
Remove .osm workflow from workers #227
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking good. Note that #223 will remove some of the osmName items. I haven't merged yet because we'll need to release an updated version of alfalfa-client.
@@ -141,38 +139,6 @@ def insert_os_tags(self, points_json_path, mapping_json_path): | |||
# add points to database | |||
self.ac.add_site_to_mongo(points_json, self.upload_id) | |||
|
|||
def add_osm(self): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧹!
@nllong just merged in the osm rename, everything appears to be working on my end |
noice! this is going to be an amazing PR with nice cleanup! |
@TShapinsky -- is this still a WIP, or can we merge? |
I think this is good if we're ready to merge the client change as well |
sweet, let me do a review of it by tomorrow's meeting. I'm happy merging the client down, but will want to wait to release. Do you think it is an issue having people (via poetry) use the Github version of the client? |
Also, I think the workflow.tar.gz can be removed since it was used in the OSM workflow? True? That also means |
I can make those changes and see if the tests still pass |
@nllong we also still have |
I would leave those as is because I'm going to rename the files to just "simulate.py" and "step.py" or something like that. That way the worker "API" just knows to call simulate in the shared mounted directory for FMU or OSWs. |
@nllong added the changes, everything appears to still work |
sweet, can you fix the pre-commit checks? probably formatting. |
Looks like I didn't have pre-commit set up on my machine. Should pass now |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks great! Thanks!
#201
There is still some OSM language existing in alfalfa. Some is dealing with the seed models for OSWs and some is on the front end. I haven't touched the front end due to being unclear as to what is actually referring OSMs and what is an OSW workflow condition that is called "osm".