Activity for JointTrack Auto
-
Alexander Breen posted a comment on discussion General Discussion
Hey Paris, it's been a while but since i've just been given a new computer i wanted to have a look at this again. unfortunately even with Windows 10 64-bit Enterprise i still get the same error. could you provide the MSVCR120.dll so i can slot it in to place?
-
JointTrack Auto released /JointTrack Auto 3.3.0 Beta Zip/JTA330BetaRelease.zip
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Paris Flood posted a comment on discussion General Discussion
Hmm, I suppose the latest version will require a Windows 10 machine as this was the OS that it was built on. Hopefully you can get ahold of a machine with Windows 10! I know at one point Microsoft was offering a free upgrade. Best of luck! Paris
-
In the versions where the region selection tool is not diasbled the edited version of the edge-detected image will indeed be sent to the optimizer (as far as I know there are no bugs with this). If it seems like the optimizer is not taking in the correctly edited version definitely let me know - unfortunatley I can't double check this currently as I don't have access to a Windows machine today, but I'll see if I can get ahold of one in the coming days. However Version 3 is certainly much faster if...
-
In the versions where the region selection tool is not diasbled the edited version of the edge-detected image will indeed be sent to the optimizer (as far as I know there are no bugs with this). If it seems like the optimizer is not taking in the correctly edited version definitely let me know - unfortunatley I can't double check this currently as I don't have access to a Windows machine today, but I'll see if I can get ahold of one in the coming days. However Version 3 is certainly much faster if...
-
In the versions where the region selection tool is not diasbled the edited version of the edge-detected image will indeed be sent to the optimizer (as far as I know there are no bugs with this). If it seems like the optimizer is not taking in the correctly edited version definitely let me know - unfortunatley I can't double check this currently as I don't have access to a Windows machine today, but I'll see if I can get ahold of one in the coming days. However Version 3 is certainly much faster if...
-
Currently using windows 7 Enterprise. many thanks Alex
-
Stephanie posted a comment on discussion General Discussion
Hi Paris, Thank you very much for the reply. The region selection tool having been left out of this version of the program makes me wonder if I am correct in thinking that it has an effect on what is sent to the optimizer. Is this tool for viewing only, or does it improve registration to remove any residual noise with it? Thanks again for your time and assistance. Best, Stephanie
-
Hmm, which version of Windows are you using? If you're using 10 and stilll having this problem I could include the missing dll to install with the next update. All the best, Paris
-
Hi guys, Version 3+ marks a rewrite of the original program and unfortunately the region selection tool was never transferred over. I kept the icon in as a placeholder in case there was interest (seems like there is!). I'm not too active with this project anymore, but I'll certainly let the next generation of caretakers know - shouldn't be too hard to put back in. All the best, Paris
-
Hi guys, Versions 3+ marks a rewrite of the original program and unfortunately the region selection tool was never transferred over. I kept the icon in as a placeholder in case there was interest (seems like there is!). I'm not too active with this project anymore, but I'll certainly let the next generation of caretakers know - shouldn't be too hard to put back in. All the best, Paris
-
Hello, I am having the same problem. Any ideas for a fix? Many thanks in advance. Best, Stephanie
-
Cesar posted a comment on discussion General Discussion
Hello, Is this a known bug or is there something wrong with my installation. Regards, Cesar Flores
-
Hello and thank you for acces to this program. Unfortunately After Updating to the latest release I encounter a System Error when attempting to open the program. The message reads " The program cant start because MSVCR120.dll is missing from your computer. Try reinstalling the program to fix this porblem" However resinstalling the program does not resolve this issue, are you able to help? Many thanks Alex
-
-
-
-
Hi Ilan, If you click Help>About does it say which card is detected and the corresponding compute capability (you will need at least 5.0)? The "Error: Render Railure" also appears when the CAD model loaded is binary and not ASCII (a quick way to check this is to open up the STL file in Notepad and check if the text is readable (ASCII) or indecipherable symbols (binary)). As of the current version JTA will only work with ASCII files, however I will definitely add binary files in a forthcoming update...
-
Hi Ilan, If you click Help>About does it say which card is detected and the corresponding compute capability (you will need at least 5.0). The "Error: Render Railure" also appears when the CAD model loaded is binary and not ASCII (a quick way to check this is to open up the STL file in Notepad and check if the text is readable (ASCII) or indeciphrable symbols (binary)). As of the current version JTA will only work with ASCII files, however I will definitely add binary files in a forthcoming update...
-
-
-
-
Ilan posted a comment on discussion General Discussion
Hello, I am getting an error on two different Windows computers with CUDA enabled. When clicking "optimize" we get the message "All frames optimized!", followed by error message: "Error: Render Failure" which is spitted out 3 times. After that, any time we click "optimize" again it gives error message: "CUDA Initialization Error!." I'm hoping you could shed some light into these issues. I'm looking forward to getting around this and also getting my hands on the source code to hack it a bit. Than...
-
So I suppose there are really four systems at play here: 1). Camera A's coordinate system (axes and origin) in mm 2). Camera A's coordinate system (axes and origin) in pixels (these pixels are specified by Camera A's pixel scale) 3). Camera B's coordinate system (axes and origin) inmm 4). Camera B's coordinate system (axes and origin) in pixels (these pixels are specified by Camera B's pixel scale). Note that these pixels are not necessary the same size as the pixels in #2. So the location of Camera...
-
So I suppose there are really four systems at play here: 1). Camera A's coordinate system (axes and origin) in mm 2). Camera A's coordinate system (axes and origins) in pixels (these pixels are specified by Camera A's pixel scale) 3). Camera B's coordinate system (axes and origins) inmm 4). Camera B's coordinate system (axes and origins) in pixels (these pixels are specified by Camera B's pixel scale). Note that these pixels are not necessary the same size as the pixels in #2. So the location of...
-
Bardiya Akhbari posted a comment on discussion General Discussion
Thank you so much Paris and Dr. Banks. My main confusion is that the translation between the second camera and the first camera has to be calculated in pixel unit. I can find the location of the second camera's origin in the first camera system in millimeter. Should I just divide those numbers by the scaling term of physical units per pixel? I tried this once (detailed version below), but the model was not visible in the second camera image. What I did in detail (Please correct me if I'm wrong):...
-
Scott A. Banks posted a comment on discussion General Discussion
Bardiya, If Paris does not respond quickly, I can walk you through it. The old files specified each projections' relationship to the world coordinate system. The new one references everything to the first view. So you just need to calculate the relative transformation matrix between the second and first systems. If that is something you are not familiar with, I am happy to guide you through it. Scott Sent from my iPhone On Jun 7, 2017, at 12:25, Bardiya Akhbari bardiyaak@users.sf.net<mailto:bardiyaak@users.sf.net>...
-
The current biplane calibration has all the info needed to create a new formatted doc like Paris describes, or for Paris to tweak his inputs to use the old format. I have attached an ‘old’ cal file. Format is: Header (always JT_CALIB_INT_EXT) Principal distance in physical units horizontal offset of principal point from center of image in physical units vertical offset of prin point … scaling term of physical units per pixel (usually mm/pixel) Vector location (x,y,z) of x-ray spot in global coordinates...
-
That would be great. Thank you so much.
-
I'll check with the creators of JointTrack_Biplane, and see what the necessary conversions are. If possible I'll update JTA to accept JointTrack_Biplane calibration files, but either way I'll post back here in the coming days and keep you in the loop!
-
I'll check with the creators of JointTrack, and see what the necessary conversions are. If possible I'll update JTA to accept JointTrack_Biplane calibration files, but either way I'll post back here in the coming days and keep you in the loop!
-
Thank you so much. I have the calibration files for the old JointTrack_Biplane (beta version), and it seems those files cannot be used directly for this new version (I think that one uses the world coordinate system instead of camera 1 coordinate system for kinematics). Do you have any code or recommended algorithm to convert those files to the new format? Appreciate your help and guidance.
-
Hi Bardiya, I've written a brief attachment (with some badly drawn diagrams) to try and help you out! All kinematics will indeed be in Camera A's coordinate system. A quick warning, the source code currently up is from a much older version of JointTrack Auto. I'll try and put the newest code up in the coming weeks after I've cleaned it up a bit.
-
Hi Bardiya, I've written a brief attachment with some badly drawn diagrams to try and help you out! All kinematics will indeed be in Camera A's coordinate system. A quick warning, the source code currently up is from a much older version of JointTrack Auto. I'll try and put the newest code up in the coming weeks after I've cleaned it up a bit.
-
Can you elaborate on the calibration format for the biplane version (or, guide me to the method name)? My main point of confusion is in the following sentence: "The first camera is set at the origin, therefore the next three numbers are the x, y, and z distances (respectively) in pixel values representing the vector from the location of the first camera to the second." The distance in mm can be calculted between the origins easily, do you mean dividing this number by the ratio of mm/pixel? Is this...
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
1 >
