Roadmap: Difference between revisions

From Tygron Preview Support Wiki
Jump to navigation Jump to search
Line 34: Line 34:
* Improvements for groundwater calculations such as microrelief and uploading seepage pressure and resistance
* Improvements for groundwater calculations such as microrelief and uploading seepage pressure and resistance
* Improved possibilities for organising Indicators and Overlays
* Improved possibilities for organising Indicators and Overlays
 
For the most recent overview of released and planned features see https://www.tygron.com/roadmap/


{| class="wikitable"
{| class="wikitable"
Line 59: Line 59:
|Hopper
|Hopper
|}
|}
For the most recent overview of released and planned features see https://www.tygron.com/roadmap/


==Further developments==
==Further developments==

Revision as of 11:32, 25 September 2023

The R&D department of Tygron develops new technology for the Tygron Platform. The long term planning which shows the introduction of new features and versions is what we call the Roadmap. Your user feedback is crucial for us to determine the roadmap. Currently we are working on new features according to this Roadmap, minor updates, bug fixes, etc.

Servers

The online availability of the Tygron Platform is split up between three different server environments, each with their own dedicated purpose.

engine.tygron.com (Long Term Support)

Updated approximately once per year, the Long Term Support server (LTS) at engine.tygron.com is the most stable version of the Tygron Platform, and is specifically for long term projects that need a stable environment. Sometimes circumstances lead to extra updates or hot fixes outside the Roadmap, often due to hardware, driver or Operating System updates.

preview.tygron.com (Preview)

The preview server (preview.tygron.com) is updated more often and will contain more recent new features. Because these new features are not fully tested and optimized yet, and are prone to change based on end user feedback, the preview server is not well suited for long term projects. The release cycle on this preview server usually consists of 2 months of roadmap development and 1 month of user feedback fixes and additional bug fixes.

All registered users have access to both the LTS and the preview servers. The main menu offers an option to switch to the other server by downloading the appropriate client.


Test server

The third server is our dedicated development and test environment. New features are first published in this environment, and tested internally for functionality, compatibility and stability. End users do not automatically have access to this development and test environment.

What to expect

Some new functionalities we are planning to release on the Tygron LTS Server 2024 are:

  • 3D Cesium Web Viewer
  • Improvements for groundwater calculations such as microrelief and uploading seepage pressure and resistance
  • Improved possibilities for organising Indicators and Overlays

For the most recent overview of released and planned features see https://www.tygron.com/roadmap/

LTS 2018 LTS 2019 LTS 2020 LTS 2021 LTS 2022 LTS 2023
25 million 250 million 1 billion 4 billion 16 billion 64 billion
Pascal Volta Ampere Hopper

Further developments

We are continuously working on improving the Tygron Platform, largely based on user feedback. The following developments are still in the planning stage:

  • Remodeling of the current level system to a system in where multiple scenarios can be evaluated. This increases the possibility to do more analysis on the model.
  • More R&D into GPU accelerated calculations.
  • Improving the User Interface based on user feedback.

We are always open for your feedback on our roadmap.

Version numbers

The version numbers consist of 4 digits: For example: 2017.1.4.2

  • 2017: The main number represents the year of LTS release.
  • 1: This represents the preview release, in this case the first quarter of the year.
  • 4: Represents a small update for a feature/bug where the API has been changed.
  • 2: Represents an even smaller update or hotfix where the API explicitly does NOT change