Conversation
|
|
||
| with open("case_name_list.dat", "w", encoding="utf-8") as f: | ||
| for line in case_name_list: | ||
| f.write(f"{line}\n") |
There was a problem hiding this comment.
[Optional][TBD] Perhaps we can dump both case name and case id into the dat file? Just in case the new user who's unfamiliar with Flow360 submit multiples cases with the same case name.
I see the logic in download_data.py, I think it's OK to keep the script as it is
However, it seems all 4 quick starts are using the case name to identify the case we'd like to download. Perhaps we can pick one of the quick starts. Dump both case name and case id into the *.dat file and fetch the case according to the case id?
There was a problem hiding this comment.
Sure I like this idea. I would like to keep the case names for folders within a directory and plotting, but I like the idea of still fetching the case using case ID.
| axes = [] | ||
|
|
||
|
|
||
| def plot_sectional_forces(data, plot_name): |
There was a problem hiding this comment.
Would be nice if we can display the sectional loading on a single blade.
Or at least set the xlim = [root,tip]. Currently between [0, root] we're showing the sectional loading from other blades --> kind of confusing for new users
2 participants
Quick start examples that are relevant to python (no WebUI quick starts). The examples are updated based on recent Flow360Scripts guidelines.
Mesh files same as on documentation page. (apart from XV15 as volume zones still don't work in new python client)
Options for case submission are both from Mesh ID (added to examples in admin portal, but not visible in new python client. To use this, log-in to examples account directly) and upload from S3
XV15 adaptive CFL contains two JSON files as "volume zones" still doesn't work in new python client. We will remove legacy json and replace mesh URL link, once it does
Some pylint issues still exist due to capitalization.