e-mail :

Registered in England and Wales company # 03449181.
 This website does not use cookies.

 © Copyright: Conwy Valley Systems Limited  2000-2024

Conwy Valley Systems Limited,

West Acre, Llys Helyg, Deganwy

CONWY LL31 9BN, United Kingdom.

VAT# GB 741 5190 48

A Geoscience Wales  founding member.

PETROG includes patent protected technology.

PETROG & PetrogLite 5.4.0

Release date : 2024-02-19

Improvements

The workflow for setting a new elliptical Area of Interest (AoI), and for editing an existing elliptical AoI, has been improved.  It is now possible to set the left end of the major axis, followed by the upper or lower end of the minor axis, and then to edit any of the left/right end of the major axis or upper/lower end of the minor axis without affecting any of the other defined AoI axis points.

The Colour analysis tool (main menu Data Analysis | Colour Space) can now use region selection when creating output layers, making it simpler to generate effective output layers that are to be applied to images.

In Stitching  | Apply Output Layer, exporting the image at a sampling factor greater than one now includes application of Colour Analysis, if active.

Bug fixes

Fixed problem of not displaying "target reached" message in standalone textural logging.  

When resuming Quantitative Textural Data Entry, how many points had been logged previously was not correctly reported.

When creating a new report to Excel, there could have been blank lines in the report list (benign but could be confusing).

Grain size histogram in phi & Wentworth units were not drawing.

Microscope definition dialog had problems when adding or removing a microscope; also changed the dialog, new button for adding an objective.

When logging from an image, the image has to be calibrated as if it were a camera and microscope; this had not been working correctly (only affecting logging from imported images).

Fixes and improvements to setting and modifying hardware combinations

Creating a Keyboard Mapping from data logged previously for a sample had a bug, now fixed.

Some textural data was trying to display as the wrong type (as text rather than a number) in reporting.

Using the external stitching option (i.e. exporting to ImageJ) could sometimes get confused about the names of files on export and re-import; now made more robust.

Colour analysis (main menu Data Analysis | Colour Space) required some bug fixes and improvements to the setting up of an image for this analysis.

Camera calibration and grabbing an image during point counting both required changes due to changes in the handling of Mouse movements during live image display.

There was a memory leak when clearing tags from all polygons, now fixed.

Fix for bug in Revisit Selected Points - now only points of interest that correspond to the active sample are displayed.

Changes Necessitated by the software environment

We do not always mention changes in this category. Each release there are typically many changes which may be hidden or may be pre-emptive but are necessary for one of several possible reasons, including:

- An operating-system-level change to the way some Windows are ordered on screen meant that some PETROG messages were being hidden, causing an apparent 'hanging' situation. We have re-structured the messaging system to avoid this happening. This affects information/warning/error messages and some user-interaction (question-response) dialogues.

- Camera manufacturers occasionally issue a new Software Development Kit (SDK), the interface software used by PETROG to communicate with the camera. This is typically when there is a new release of Windows or the manufacturer introduces a new camera model. This always requires considerable re-testing of PETROG and often some re-engineering.

- Each piece of hardware has its own drivers for communicating with applications. In the case of older equipment, such as our early models of stepping stage, these can require updates and resultant changes to PETROG.

- We are always looking out for trends in software development and possible future changes to underlying technologies that could affect PETROG. A major trend at present is driven by mobile devices and a desire for standardisation across mobile and traditional computing devices. We are gradually introducing changes to PETROG that should avoid serious problems in future. As a positive side-effect, some of these new developments can significantly improve the speed of image display and image analysis in PETROG.

In this release:

There has been a major re-working of the way in which messages (information/warning/error messages and some user-interaction or question-response dialogues) are handled.

Device conflicts and multiple cameras are now handled better.

New cameras being supported has required some changes to accommodate both the new ones and the already-supported cameras.

This category does emphasise the benefits of keeping software up-to-date.

PetrogLite v5.4.0

Improvements

When resuming logging mid-way through a point count, the sequence of SteppingStage commands to return to the next location on the slide to be logged was convoluted, and therefore the slide was not re-positioning as accurately as it should.  This has now been fixed, so the slide is quicker to reach the intended position and does so more accurately.  This includes the addition of an option to manage whether or not to the SteppingStage should visit the bottom-left of the AoI first when doing a resume, before it moves on to the location from which to resume logging.  This option is available from menu option Slide | Logging Options - the default behaviour is for this to be switched on (as in previous releases), but this can now be switched off for speed/accuracy purposes.

The workflow for setting a new elliptical Area of Interest (AoI), and for editing an existing elliptical AoI, has been improved.  It is now possible to set the left end of the major axis, followed by the upper or lower end of the minor axis, and then to edit any of the left/right end of the major axis or upper/lower end of the minor axis without

affecting any of the other defined AoI axis points.

Changes Necessitated by the Software Environment

In each release there are typically some changes which may be hidden or may be pre-emptive but are necessary for one of several possible reasons, usually being changes in either the Windows operating system or the device drivers that allow hardware to communicate with Windows. In this release we have had to change our software to accommodate a change to the way the stepping stage is allocated a 'handle'. This should not affect you, unless you were one of the unlucky ones who noticed it before we had the fix in place, but it does emphasise the benefits of keeping software up-to-date.