@sharonrlin_gitlab This is in work as markummitchell/engauge-digitizer#315. You can try out a pre-release for 64 bit Windows at https://ci.appveyor.com/project/markummitchell/engauge-digitizer/branch/master/job/c9dlm24t20ulviur/artifacts
I'm having a problem with 11.1 and had to fall back to an older copy. What was happening was the image I was digitizing would move up/down slightly at the end of the curve. It was as if I clicked on the up/down arrows on the right side. I've zoomed in until my image is larger than the screen as there is white space and I wanted my image to digitize as large as possible. When this happened, the Y coordinates would be off by the amount the image shifted.
Would it be possible to have a magnifying glass around the region to make your selection more accurate when you are trying to follow a curve?
Okay, I'm back. What I've noticed and can't pin point how it happens is that if you have a JPG that you are scanning and the image file is larger than the display window, the image will shift up and down sometimes without hitting the arrow keys or rolling the mouse wheel. I can't figure out what triggers it but it causes the digitization to be incorrect.
fix
The problem to using Fit is that it changes the ratio of length to width and I haven't had time to test to see if that alters the digitized output. If it would fit to either hight or width and keep the same ratio that would be nice. I'll try to get more time to test it. Another thought might be to have the ability to lock the image from panning up or down along with the mouse wheel just in case.
Mark just in case you don't have anything else to do. Have you considered creating an option to store the X&Y values in the buffer so you can simply paste them directly into an Excel file rather than having to create a temporary Excel file, paste them, and them copy the columns to the destination file? I typically create one Excel file with all of the digitized data for one group of equipment rather than individual worksheets for each and to be able to just select a starting cell and have the program populate the cells would be neat.
@oopman2002 I searched the code and the only thing that should cause scrolling is when zooming in or out - in which case the window scrolls to try to keep the cursor position in the center of the window. Are you running any zoom utility? If not, I will probably need more information, like are you at the left or right edge when the image jumps up or down? Is a point selected?
@oopman2002 Regarding zooming, if you increase/decrease the zoom factors, using Control+MouseScroll, then you should get 1:1 aspect ratio
@markummitchell Mark, you helped me in the past when I needed a way to export the images from our 4000 Engauge files. We try to train an AI system with our digitized output and now have the images. We do have all the digitized points in the plot coordinates as well but would need the point position in "image-coordinates" - basically in pixel position from one of the image corners. Do you see a way to get that with not too much effort on your end? I assume that information is available somewhere before you do the coordinate system transformation with the identified axes points. A way to export those coordinates for each digitized point in our 4000+ files would be amazing. (We can script somthing in Python too, if you can maybe point us to where we should start looking).
@wilthan Issue #325 was created to track this. You can try out a new python script at https://github.com/markummitchell/engauge-digitizer/blob/master/contrib/python/DumpGraphAndScreenCoordinates.py. If you are comfortable with python, you can modify that script. Another option might be a script to read the DIG file and any CSV files created from it, and convert the points in the CSV files to create new CSV files. In any case, good luck with your AI system.
Regarding Android, I just created issue #359 so this can be tracked. I will look into this in the next 24 hours to answer your question, although the actual release would take longer to set up.
@Denise It looks like building x86 and 32-bit arm versions would be easy since the Qt libraries support those immediately when installed. Building a 64-bit arm version would be much harder since Qt would have to be rebuilt from source for 64 bits. That rebuild can be hard because Qt has many dependencies for processing different image types, and the libraries for that also have dependencies. Of course, you are free to copy the code and do whatever you like (according to the GPLv2 license), but I would try to support your effort as much as I can. Do you just need a graphical executable?
Hi @markummitchell
I would like to have the calculation in a library. I have an image and need the data points (x,y pairs). Is Qt for that necessary i.e. is it possible to extract the calculation in a library. Do there currently exist any APIs or is it even possible in your architecture?
I would like to have the calculation in a library. I have an image and need the data points (x,y pairs). Is Qt for that necessary i.e. is it possible to extract the calculation in a library. Do there currently exist any APIs or is it even possible in your architecture?
https://courses.cs.washington.edu/courses/csep576/11sp/pdf/Transformations.pdf has a brilliant discussion on the math involved. Qt is not required, although it can help to have a nice vector library. The Qt library has many dependencies and can take a long time to install (sometimes) because of those dependencies.
Mark have you considered saving the location of the image file to be digitized and then when you export data start in the location of the image file rather than the location of the Engauge system files? It's not a big deal but I'd assume that most people want to save their files where (or close to) the input image is.
Hi, here is an example of a signal
-File / Import (Advanced) / cardiogram.jpg
-Coordinate System count=3
-Ok
-View / Background / Show Original Image
-(With '1' appearing in the Coordinate System toolbar)
-Settings / Segment Fill / PointSeparation=5
-Select Digitize Axis (3 red points)
-Enter 3 axis points for one curve
-Select Digitize Segment (green line)
-Click on the first curve in various places
-(Repeat previous step with '2' appearing in the Coordinate System toolbar)
-(Repeat previous step with '3' appearing in the Coordinate System toolbar)
-File / Save
-(With '1' appearing in the Coordinate System Toolbar)
-File / Export / <filename1>
-(Repeat previous step with '2' appearing in the Coordinate System toolbar)
-(Repeat previous step with '3' appearing in the Coordinate System toolbar)
@ethnotools Sorry for the delay, I missed your original message. As a GPL open source project, no money has been accepted to obtain the software. As a software developer, I received receive one contract from NASA at the urging of a large aerospace corporation to upgrade the Qt software license which was not free at that point, and make some custom software enhancements.
Mark, probably a silly question but I'm trying to digitize a semi-log plot but the log option for the y-axis doesn't seem to stick. Under Settings > Coordinate... I can choose y-axis log but it I go back to that option is reverts to linear. Same graph image. Thanks, Looks like a very useful program.
