We used EnSight to open a Nexus database and explore the example database that is available in the EnSight installation. Then, we pushed data Report Items into the Nexus database from an interactive EnSight session. We used the Nexus database to browse the Report Items and saw the usefulness of tags. We deleted a Report Item from the database. We then pulled an HTML file in as a Report Item. We looked at existing templates and used one to generate a report. We then created a template and made a report using our three Report Items.
In a realistic scenario, an engineer works not with a single dataset, but a set of them. In this scenario, the engineer could open a new session of EnSight for each dataset, and interactively push the report Items into Nexus. While this is possible, it is not recommended as the manual work is error prone and not easily reproducible. Instead, the user should consider moving to scripting and batch operations. With this approach, the set of operations to be performed will always be exactly the same between datasets (making comparisons easier), and the amount of workload for the engineer will not increase with the number of datasets to analyze. Nexus is ideal for inserting into complex engineering workflows.
Using Nexus in a batch and scripting fashion is covered in the Intermediate Getting Started.
For more information, please explore the following and contact support for additional assistance: