To follow the visualization parts, you must have ResInsight<\/a> installed.<\/p>\n <\/p>\n After the first tutorial, you should have a copy of the latest master branch of the opm-data repository. If you followed the instructions in that tutorial<\/a> it will be named “opm-data-master”. Go to the Norne case by entering its directory:<\/p>\n From here you could start a Norne run immediately by entering the following command:<\/p>\n Note that there should be no spaces between the parameter key (“output_dir”) and the associated value. It is quite possible to leave out the “output_dir” parameter, that way all your output files will end up in the current directory. If, instead, you choose to use the parameter all output files will end up in the directory you name (and the directory will be created), “out_serial” in the example.<\/p>\n Running the case will take some time, depending on the speed of your computer. Expect around half an hour on reasonably modern computers.<\/p>\n Next, we will take a look at the output being produced by the simulator.<\/p>\n <\/p>\n The Flow simulator produces several logs:<\/p>\n The most important messages are written to the terminal. This includes warning and error messages, timesteps and timestep summaries. Warnings are printed in blue, errors in red, and numerical problems (typically leading to timestep chopping) in pink.<\/p>\n By default, the terminal is limited to displaying a certain number of messages of the same type (note, warning, problem, error etc.), so after displaying a large number of warnings for example it will cease reporting them. Similarly, it will stop repeating similar messages (technical detail: messages with the same “tag”) after 10 such messages have been displayed. For example, you can see that after report step\u00a04, Flow prints the message: “Warning: Message limit reached for message tag: Unhandled output keyword”.<\/p>\n Other than the time steps, the most interesting messages printed to the terminal are the well-control messages printed when wells are switched from one control setting to another due to breaking one or more constraints, and numerical problems encountered. If Flow fails to solve the current timestep for any reason it will retry with a smaller step size. That will be reported like this:<\/p>\n The PRT log file contains a lot more than is printed to the terminal.<\/p>\n First, there are no message limits, so warnings that are eventually silenced in the terminal output, will remains as warnings here.<\/p>\n Second, the log is a bit\u00a0more verbose. Initially, an overview of all command-line options used is printed. Also, fluid-in-place reports are printed for all fluid-in-place region after every time-step.<\/p>\n The main difference between this and the PRT log is that this will contain absolutely all messages, including debug messages. In particular, the residuals are printed after every iteration, making it possible to follow the Newton-like nonlinear iteration process. This makes it useful to developers, less so for regular users. If you have a problem however, this log can be valuable in diagnosing your issue. One of the main outputs from the simulator is the summary file (NORNE_ATW2013.UNSMRY), the ending UNSMRY means it is a unified summary file, i.e. containing data for all time-steps in a single unified file.<\/p>\n In this file you will typically find data that are likely to be useful to plot as a function of time, such as well rates, bottom hole pressures or fluid-in-place quantities. Flow allows the input deck to configure what should be written to the summary file. To look at the summary you may use the ecl_summary<\/tt> tool as was explained in the first tutorial<\/a>\u00a0(also you can use the\u00a0summaryplot<\/tt> tool to visualize well curves as explained there):<\/p>\n This will give a huge list of keywords corresponding to quantities written to the summary. Some of the more important ideas to get from this are:<\/p>\n To get a particular quantity, for example the bottom hole pressure of the well C-4H, issue the command<\/p>\n Note that when the well is closed, the BHP is reported as zero.<\/p>\n The units used in all summary (and restart) output files correspond to the unit family chosen in the input deck. For Norne, METRIC units are used, and so the BHP output is in bars, rates are in cubic meters per day etc. When FIELD units are used, BHP output will be in psi, rates in barrels per day for oil and water or 1000 cubic feet per day (yes, really!) for gas etc.<\/p>\n <\/p>\n Note: the rest of this guide was made with a version of ResInsight that is no longer current, the current version looks different, although the principles should be the same.<\/em><\/p>\n The field data (3D data, typically per cell) is typically written to restart files. For the current case, you will find this in the file NORNE_ATW2013.UNRST (a unified restart file).<\/p>\n We will now open the case in ResInsight to look at some solution variables. You can click on the pictures to see a larger version.<\/p>\n First we need to import the case. Click the Import Eclipse Case<\/em> button.<\/p>\n Navigate to the directory containing the output (out_serial if you followed the instructions earlier) and choose the EGRID file.<\/p>\n The case should open, looking like this:<\/p>\n You can rotate and zoom to get a better view. Use the right mouse button to rotate, the middle button to zoom and the left button to move the view.<\/p>\n By default, we are looking at the oil saturation. Now we want to look at all phase saturations using a ternary color scheme. Click on the TERNARY<\/em> line in the property editor.<\/p>\n The wells are not as visible as we’d like, so we will change how they are displayed. Click Simulation Wells<\/em> in the Project Tree<\/em> view, then choose Top of active cells BB<\/em> for Well head position<\/em>. Now the well heads are shown at the edge of the full bounding box, and stand out better. Also we’ll change the Well label color<\/em> to white.<\/p>\n Then we’ll animate the results, click the Play<\/em> button as shown.<\/p>\n By clicking Pause<\/em> you can stop at any timestep of your choosing. Note that the number of wells change during the simulation.<\/p>\n <\/p>\n The ResInsight visualization tool can also display well curves and other summary data interactively. To do this, click the Import Summary Case<\/em> button.<\/p>\n Navigate to the output directory and choose the SMSPEC file.<\/p>\n By default, field production rates for gas, oil, water and liquid (oil + water) are shown. The gas production curve\u00a0dominates the others in this case, as should be expected since it is a case using METRIC and rates\u00a0are therefore shown in cubic meters per day.<\/p>\n We’d like to inspect the bottom-hole pressure of the well B-1H. Expand Summary plot 1<\/em> in the Project Tree<\/em>, delete the production curves and add the well BHP curve as shown below.<\/p>\n Now we are looking at the BHP curve we wanted to.<\/p>\n If we want to look at properties for a particular well, or a particular property, we can use a filter. Type the well name C-2H in the Well name<\/em> field and the list of choices will be restricted to those relevant to that well. Choose WBHP:C-2H<\/em> to see its BHP curve.<\/p>\n ResInsight can export these images easily. In the Edit<\/em> menu, choose Snapshot To File<\/em> to export them to files. You can see a few examples below.<\/p>\n Flow supports running simulations in parallel using MPI. To use this\u00a0run Flow with mpi_run<\/tt>: (note that the next command should be a single line)<\/p>\n The above command runs the simulator with four processes, so you should have at least four cores or hardware threads available to gain from this (adjust the parameter to suit your computer). The simulator should then run quite a bit faster (if not 4 times faster). It should be noted that since the input deck format and output file formats are serial in nature, input and output has not been parallelized.<\/p>\n The resulting output should be equivalent to the output from the serial run. It will not be identical however, since the linear solver will not behave identically between the serial and parallel runs.<\/p>\n","protected":false},"excerpt":{"rendered":" This tutorial will guide you through running and visualizing the Norne case, which is an open benchmark case of a real Norwegian Sea oilfield. It will also demonstrate how to run Flow in parallel, take a look at some available run-time parameters, and discuss the logging facilities of Flow. The tutorial assumes that you have … Continue reading Running the Norne case with Flow<\/span> Running the Norne case<\/h3>\n
cd opm-data-master\/norne\r\n<\/pre>\n
flow NORNE_ATW2013.DATA --output-dir=out_serial\r\n<\/pre>\n
Simulator log\u00a0output<\/h3>\n
\n
Terminal output<\/h5>\n
Problem: Solver convergence failure - Iteration limit reached\r\nTimestep chopped to 3.630000 days\r\n<\/pre>\n
The PRT log (NORNE_ATW2013.PRT)<\/h5>\n
The DBG\u00a0log (NORNE_ATW2013.DBG)<\/h5>\n
\n<\/p>\nSummary output<\/h3>\n
cd out_serial\r\necl_summary --list NORNE_ATW2013\r\n<\/pre>\n
\n
\n
ecl_summary NORNE_ATW2013 WBHP:C-4H\r\n<\/pre>\n
Visualizing the solution\u00a0with ResInsight<\/h3>\n
![\"1_import_eclipse_case\"](\"\/\/opm-project.org\/wp-content\/uploads\/2016\/12\/1_import_eclipse_case.png\")
<\/a><\/p>\n![\"2_open_egrid_file\"](\"\/\/opm-project.org\/wp-content\/uploads\/2016\/12\/2_open_egrid_file.png\")
<\/a><\/p>\n![\"3_loaded\"](\"\/\/opm-project.org\/wp-content\/uploads\/2016\/12\/3_loaded1.png\")
<\/a><\/p>\n![\"4_zoom_and_rotated\"](\"\/\/opm-project.org\/wp-content\/uploads\/2016\/12\/4_zoom_and_rotated.png\")
<\/a><\/p>\n![\"5_ternary_display\"](\"\/\/opm-project.org\/wp-content\/uploads\/2016\/12\/5_ternary_display.png\")
<\/a><\/p>\n![\"6_well_setting_display\"](\"\/\/opm-project.org\/wp-content\/uploads\/2016\/12\/6_well_setting_display.png\")
<\/a><\/p>\n![\"7_play\"](\"\/\/opm-project.org\/wp-content\/uploads\/2016\/12\/7_play.png\")
<\/a><\/p>\n![\"8_pause\"](\"\/\/opm-project.org\/wp-content\/uploads\/2016\/12\/8_pause.png\")
<\/a><\/p>\nVisualizing summary data\u00a0with ResInsight<\/h3>\n
![\"1_open\"](\"\/\/opm-project.org\/wp-content\/uploads\/2016\/12\/1_open.png\")
<\/a><\/p>\n![\"2_open_smspec\"](\"\/\/opm-project.org\/wp-content\/uploads\/2016\/12\/2_open_smspec.png\")
<\/a><\/p>\n![\"3_loaded\"](\"\/\/opm-project.org\/wp-content\/uploads\/2016\/12\/3_loaded.png\")
<\/a><\/p>\n![\"4_loaded\"](\"\/\/opm-project.org\/wp-content\/uploads\/2016\/12\/4_loaded.png\")
<\/a><\/p>\n![\"5_select_well_curves\"](\"\/\/opm-project.org\/wp-content\/uploads\/2016\/12\/5_select_well_curves.png\")
<\/a><\/p>\n![\"6_select_well_filter\"](\"\/\/opm-project.org\/wp-content\/uploads\/2016\/12\/6_select_well_filter.png\")
<\/a><\/p>\n![\"c-2h_wbhp\"](\"\/\/opm-project.org\/wp-content\/uploads\/2016\/12\/C-2H_WBHP.png\")
<\/a><\/p>\n![\"f-1h_wwir\"](\"\/\/opm-project.org\/wp-content\/uploads\/2016\/12\/F-1H_WWIR.png\")
<\/a>
\n<\/p>\nRunning Flow in parallel<\/h3>\n
mpirun -np 4 flow NORNE_ATW2013.DATA --output-dir=out_parallel\r\n<\/pre>\n