In the DDSCAT+ user guide it is specified that the effective radius a_{eff} = (3V/4*pi)^{1/3} where V is the volume represented by an array of N dipoles with lattice spacing d, then V = Nd^{3}

For a rectangular prism of 17732 dipoles and dipole spacing of d = 0.5nm then, the volume is V = 2216.5 nm^{3}. The effective radius would then be a_{eff }= 8.088nm.

However, in actual use with a rectangular prism shaped array of 17732 dipoles and 0.5nm dipole spacing the effective radius given by the software is a_{eff} = 32.353nm. This would be the effective radius were d = 2nm used for the spacing rather than d = 0.5nm as is specified in the same file as the given effective radius.

This is also true for the same shape with a dipole density of 3 per nanometer. The given dipole spacing and effective radius seem to not match up. Now the number of dipoles is N = 62040 and the file says d = 0.33nm but the given a_{eff} = 73.674nm which would be true were d = 3nm.

It seems to me that the program uses a certain dipole spacing, but when calculating the effective radius it uses the reciprocal of that spacing. Am I incorrect, or missing something?

0 Like 0 Dislike

Prashant K Jain@ onYou are right about the definition, effective radius = (3/4pi*Volume in cu. nm)^0.3333

Effective radius does not depend on dipole distance as you will see from the formula above.

Effective radius is a fixed property of the nanostructure of given dimensions, it does not care what dipole density you use. If you increase dipole distance, you simply pack less dipoles within the structure. If you decrease dipole distance, you pack more within the same structure. The volume stays fixed and so does the effective radius. In essence, you choose the dimensions of your structure and that is what sets the effective radius.

Therefore, you can specify the dimensions of the object (in Blender) and then in DDAConvert you specify the dipole density. That will automatically set the number of dipoles. As long as you use the same dimesions for the object, the effective radius ought not to change. Can you try this and let me know whether you still have trouble? This is a critical issue and so I want to make sure all our users are able to set the effective radius reliably.

Reply Report abuse

Please login to answer the question.