-
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 define a system with particular spin postions to be read via file #210
Comments
Hi , I am sorry for the urgency, but please could anyone help me through above issue . Thanks |
Hi @Shobhn, thank you for your message and apologies for the wait. The majority of the team is at the conference. Could you please send us the file? |
yes sure! And thank you very much for the urgent reply :) |
Hi @Shobhn, as you do not have magnetisation values for every single point in the region I have written a short example about how you might convert this to a
Please remember that the |
Hi @samjrholt , Thank you, and the team, very much for the quick response and for this answer, I really appreciate your help. The code above helped me lot. Thanks again! :) |
Hi team, Thanks again for your help earlier ! :) I have one more query regarding this issue, so I have more data files with different positions and spins, I wanted to ask that what should be the approach while defining the cell and the mesh so that the region can be discretised correctly with all spins at the centre of each cell. I have attached a file here for example : [DL_sat_0.txt](url) It would be great if some one can help me through this. Thanks Again! |
Hi,
So I have 6 column data file in format of (x,y,z,Sx,Sy,Sz) representing each spin positions and directions in a lattice. I want to create a MFM image simulation for this artificial spin ice lattice. Could anybody please explain me how to read these positions and spin directions to define a system in Ubermag. I am confused about how to put spins in these specific positions after defining the region.
Any Help is really appreciated. Thanks
The text was updated successfully, but these errors were encountered: