an example to visualize segment and connection structure for multisegment wells. #4886
Conversation
GitPaean
added
the
manual:irrelevant
|
jenkins build this please |
GitPaean
force-pushed
the
visualizing_multisegment_wells
branch
from
f37da0b to
001eef3
Compare
|
jenkins build this please |
|
jenkins build this please |
bska
left a comment
bska
left a comment
There was a problem hiding this comment.
I think I'd personally use fmt::format() instead of operator<<() for the individual output statements, but other than that this looks good to me.
You might want to use std:cerr instead of std::cout for the diagnostic information though.
| std::cout << "\n\n***** Caught an exception: " << e.what() << std::endl; | ||
| std::cout << "\n\n***** Printing log: "<< std::endl; | ||
| std::cout << os.str(); | ||
| std::cout << "\n\n***** Exiting due to errors." << std::endl; |
There was a problem hiding this comment.
This kind of diagnostic information should probably go to std::cerr instead of std::cout.
There was a problem hiding this comment.
now I read that many are suggesting to use std::cerr for even progress reporting output and claims it to be the better approach due to its unbuffered nature. What is your take on this? I can do that if suggested so while I do not think it is so critical though.
There was a problem hiding this comment.
now I read that many are suggesting to use std::cerr for even progress reporting output and claims it to be the better approach due to its unbuffered nature. What is your take on this?
I mean, generally, yes std::cerr is preferable for that kind of reporting.
I can do that if suggested so while I do not think it is so critical though.
No need. The current version is good enough for me.
|
Please provide a help page to make this usable for others and intall the binary |
GitPaean
force-pushed
the
visualizing_multisegment_wells
branch
2 times, most recently
from
7e213a4 to
5c7c1d4
Compare
visulizing the segment structure for multisegment wells and also the connections attached to the segments.
removing a few unused headers.
following the reviewing comments.
GitPaean
force-pushed
the
visualizing_multisegment_wells
branch
from
5c7c1d4 to
032554b
Compare
|
jenkins build this please |
bska
left a comment
bska
left a comment
There was a problem hiding this comment.
Thanks a lot for the updates. This looks good to me now and is a very welcome tool. I'll merge into master.
4 participants
In the real applications, there are some rather complicated multisegment well structure. Having a visual understanding of the segment structure can provide insight to the iteration behavoir and solution of the well.
For simple cases, it is possible to run
plot_ms_well CASE.DATAto get .gv output for all the multisegment wells,with
dot -Tpdf PROD01.gv -o PROD01.pdfto generate the pdf visualization.pdfcan also bepnghere.For some cases that generates the wells on the flight, you might need to call the function
writeWellStructure()directly in the proper place to generate the .gv for the wells you want.Many code is following the example
wellgraph.Below are some visualization examples,