Hello
LOWLANCE HDS Gen2 Touch
10 knots speed
100m water depth
Record number of bytes the best
100 200 400 800 1200 1600 2000 2400 2800 3200bytes?
Please tell me

3200

Thank you
I am also currently 3200
The run out of memory
Even in a narrow range
Windows7 32bit memory4G
Please tell me

Hi,
The quality you record in will have very little effect on the memory that is used by ReefMaster (almost none, except when using the sonar viewer).

How big is the map that is running out of memory? 32bit Windows limits you to 2GB when generating the map, so the realistic maximum is about 10km square, although that depends on other factors also. Try splitting your map into smaller regions if you keep getting problems, or send you workspace (.rmdb file) to This email address is being protected from spambots. You need JavaScript enabled to view it. and we can take a look to see if there are any obvious issues.

thanks,
Matt

Thank you
I sent test data now
Please check

Hi,
Nothing has been received - could you please check that it has been sent to the address This email address is being protected from spambots. You need JavaScript enabled to view it..
Also, if the file is very large ( > 10MB) then it would be better to upload the file to a service such as Google Drive and just send the link.

thanks,
Matt

Thank you
File transmission service
I sent data
Please check

Hi,
Thanks for the workspace file - that looks like a very interesting area!

I generated the full map without problems on a 64 bit machine with 12GB of RAM, and the memory peaked out at nearly 6GB when generating in vector mode with hardness.
There is no getting away from the fact that map generation does take a huge amount of resources, and for some maps on some systems, it is not going to be possible to create the whole map at once. ReefMaster does not impose limits on the size of map that can be specified, as we have no reliable way in advance of knowing how much memory will be required, so they only way to found out what the limits are on a particular system is though trial and error.

That said, there are a number of things you can do to limit the resources that RM uses:

• Use Raster mode, not vector mode. Generating the iso-areas can be a time and memory consuming task, and is only required if you are need vector areas for map export.
• Increase the Max Interpolation to limit the number of empty areas in the map. Large numbers of small empty areas can slow down the contouring process significantly.
• Lower the number of contours that are generated by increasing the Major Contour Interval and de-selecting Generate Minor Contours.
• Don't create the hardness layer for the full map. Instead, just create hardness for smaller individual areas of interest and save these hardness areas to a user map.
• If you still run out of memory, then you have to create smaller maps. Limit them to 5km across, and combine the output in a user map or just create several different maps.

By applying the points above, I was able to generate the full map area of 12x6km with a peak memory use of about 1.2GB, which should be fine on your system. I was not able to generate the full area of hardness in one go, however.

Please give that a try, and let me know how you get on.

Matt

Thank you
I will check

Great read, used those tips to get better out of what I had already. thx guys