-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
how to use "landmark" get a particular electrode or lead location? #44
Comments
I want to import files into map3d. How to generate pts, fac, geom, lmarks files? |
@dcwhite |
This is the right place, but I am not the maintainer of this repo. You could try @bryanworthen or @rsmacleod, or users @bzenger or @jab0707 (just going by who is the most active on the issue list). |
Hi there. Thank you for using map3d, and I apologize for the delay. Your question can mean a few different things. If I answer the wrong question, please feel free to let me know.
A little more detail:
25feb97_sock.lmarks shows an example of an artery-style landmark as well as single-point landmarks. In either case, map3d does not currently support adding nodes to a geometry from within the software. The points must be added to the files in question. It does support editing a node's position once it is in map3d by moving it around (See 8.2.3 for Picking controls, Picking ->Edit Node Mode or Edit Landmark Point Mode; 8.2.2 for keyboard controls once in the edit mode). Let me know if this didn't quite give you what you need, or it I can answer any more questions. |
Oh, if your question is specifically about how to get 64 nodes into the chest area of tank_leads_192, then you would need to know which points to use as a frame of reference. Some ways to know which node inside of map3d corresponds to which point in the .fac file are:
|
Thank you for your reply! |
I want to use map3d to add electrode points and make triangles to the 771 tank geometry.
I learned from the software manual that landmark can do it, but I don't know how to implement it?
The text was updated successfully, but these errors were encountered: