What is new in CooRecorder 9.8.0?

Last update 23 March 2022.

March 23 2022:

New CDendro version 9.8.1, 23 March 2022

An error in version 9.8.0 has been corrected: When using the button "Select best matching members" of a collection and then closing or cancelling that small window "Uncheck members on bad matching..." then your collection suddenly CLOSES. That error made the "Select best matching members" button command not work at all! This error has been corrected with version 9.8.1

An error in versions 9.6 to 9.8.0 has been corrected:
When working with "Plotting windows settings/Enable automatic positioning of windows" TURNED OFF (unchecked) and relying on the WindowsList for switching between samples, then screen updates became very SLOOOOW when having many ( >10 ) open samples. This was caused by an error introduced in November 2020 and was not reported before now.

In short

  • You can make the helpline snap to (i.e. start at) the nearest point. This makes for better precision when it comes to placing points along a straight line.
  • The AutoPlace helpline can be made to both snap to the nearest point and to stay on your screen after the AutoPlace points are set. This facilitates adding points missed by the AutoPlace mechanism as the helpline is still in place.
  • There is a new command to split a single point into a pair of points. This is useful when you want to change the startpoint for the next series of points as you do not have to delete your last single point - you will just replace it automatically with the first point of a new pair.
  • Blue channel measurements:

  • Frames showing where blue channel data will be collected can be made more clear (thick white borders) to enable quick identification of "points in error".
  • There is now a mechanism to Export parts of each ring to a new image file. This gives you a way to collect image data with CooRecorder for later feeding it into your own software algorithms for development of blue intensity calculations. To facilitate your programming effort the ring images have been rotated so that all rings lay in a common direction. A separate file contains pixel addresses for each ring frame.  An example program is available on request.

AutoPlace (A) help line and (standard) Help Line (Q,P) made more useful:

Diagram 1
  • As a new option, the helpline drawn during an AutoPlace (A) of points can be left on your screen.
    With the help line in place you can add points missed by the A-command by Ctrl-clicking at a (missed) ring border near the helpline. That will make the new point snap to the helpline! You can turn on this option by checking "Add persistent HELPline to a new AutoPlace sequence of points" at Settings/Other settings.
  • You can make the AutoPlace help line always start from the nearest point. This option is also set at Settings/Other settings.
  • The standard help line (P, Q) works as before, but if you combine it with Ctrl-Click, the line will snap to the nearest point.
    Note: To remove a help line, click twice on the Q key.

How to split a single point into a pair without loosing the original position.

Diagram 2
1. See that point 72 is selected.
Click "Split a single point" (or press X)
to make 72 into 72:1 (see next picture)
Diagram 3
2. Now click the point where you want 72:2
This way you get 72:1 exactly where your old point 72 was placed.

Corrected errors and small enhancements:

Unexpected interchange of pairs (not a common problem)

Settings menu: "When sorting points, do not swap e.g. 15:1 with 15:2 when 15:2 is more near to 14."

Old versions of CooRecorder have allways sorted also the pairs of a dendro point so that the one nearest to the previous point is placed first and that one with a longer distance to the previous point is placed second (after). That way of sorting sometimes became wrong when a sample was broken (so that you wanted to jump backwards) or when the sample was of oak. When measuring oak you sometimes want to step backwards into a neighbour beam in the wood to continue  measuring the ring sequence from that point. For pine that is not the very typical case.
When you have this option checked, the members of your pair will never be unexpectedly swapped.

mm and microns in Settings for color intensity

Diagram 4
When the dpi value of an open image is known, the frame specifications are now shown not only as pixel values but also as mm or microns.

When dragging an image...

When dragging an image across your screen, B-values and point numbers can now be suppressed to lessen flickering problems. This option can be turned on/off from the Settings menu, see "Settings/Show B- and PointNumbers when dragging with your mouse"

On how to make careful blue intensity measurements
and on how to export your ring images to your own software.

Diagram 5
Note: If you click on a point on the curves (e.g. at 2002) a circle will light up around the corresponding point. It goes away as soon as you release the mouse button.
If you are going to measure blue values, you have good reasons to try set your points carefully so that the "blue channel mining areas" (the area of the ring where blue channel data is collected) are properly layed out as shown in the diagram above. I.e. each ring image collection area/"the data mining area" should overlap only one and the same ring of the tree. If you set the help line perpendicular to your ring borders and see that new points are all placed along the line, you are usually on the way of getting good measurements. For this you might best use the AutoPlace command when working with pine.
Diagram 6
Instead of the AutoPlace command you might instead use the DH tool to set points manually when rings are tortuous and have diffult paths.
Diagram 7
After you click OK, the resulting screen might look as in diagram 5. Please notice the "Use fat lines for rectangles" checkbox in diagram 7.
The result of this command is like diagram 7, but it is also one or more "blue color files", see e.g. Getting the blues from NAM01 - an example

The Calculate Color Intensity (CI) command at the blue lb icon gives you tools both for calculating blue values and for checking where data is collected. (Provided you have checked "Show where data is picked...") This is all illustrated in diagram 5 above with those white rectangles showing where data will be collected. For that we are using a CI Collector which is set up for export of (almost) full ring images.

Data is selected as "Mean of slices" as that method does not overwrite the image itself but gives you all these clear white-framed rectangles. For later really calculating blue data, you might prefer the "Mean of sorted pixels" method, but for showing where the data frames will be placed the "Mean of slices" method gives the best illustration.

Exporting your ring images for separate processing

These are the exported ring images.
This table shows the size of each ring image and where you will find it.

A message box will now pop up telling that the export data has been directed to a .tif file and a .txt file.

The .txt file gives you entry points into the .tif file, i.e. where a ring image is stored (x,y) and how big that ring image is (width, height). E.g. ring number 1 has its top left corner at x=0, y=64 and it consists of 162 columns and 97 rows. You might access its topleft blue pixel value by a call to GetPixel(0, 64).B when using Visual Basic. In the example program (available on request) there is a mechanism to load all the blue values into a matrix from where you can easily retrieve them from your own program.

CDendro:

When using a secondary reference (see Tooltip on Select as reference): also .wid-values of that reference are now shown.

Copy curves to clipboard: The display magnification (1.0 by default) should now be specified through Settings/Screen Magnification...
The Copy curves to clipboard command will not give you the proper curves if your Screen magnification is not properly set up.



Copyright © 2022, Cybis Elektronik & Data AB, www.cybis.se