Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Topics - MichaelTayler

Pages: [1]
Bug reports / Parallel computing using SpinDynamica 2.6.0
« on: March 27, 2013, 01:28:26 PM »
I am having some difficulty using "parallelization" in v. 2.6.0, which I think is due to an incorrect loading of the packages.  I am loading SpinDynamica in the standard way via

Code: [Select]
AppendTo[$Path, (*insert path to 2.6.0 here*) ]

The error messages below arise when running Signal1D, Trajectory and similar routines: (repeated 8 times, once for each of 8 Kernels launched)

Code: [Select]
Get::noopen: Cannot open SpinDynamica`.
Needs::nocont: Context SpinDynamica` was not created when Needs was evaluated.

Any guidance is much appreciated!  It would be very useful for someone to upload an example file for a "working" parallel calculation

General Discussion / Spin dynamics T-shirt
« on: March 06, 2013, 12:55:32 PM »
For those of you who may be interested:

Examples / Ernst angle
« on: February 20, 2013, 10:44:54 AM »
The attached notebook illustrates the "Ernst angle", which is the flip angle that maximizes steady state transverse magnetization for a given recovery delay between successive scans in an NMR experiment.   (Output has been stripped due to strict file upload size on this forum)

The Ernst angle is close to 90 degrees if the delay between scans allows near-complete longitudinal recovery, i.e. is a few times T1.

For a recovery delay that is short compared to T1, the Ernst angle is substantially less than 90 degrees.

Bug reports / $Chronology LeftToRight and RightToLeft
« on: February 14, 2013, 12:27:40 PM »
Just a quick note that while SpinDynamica's current default chronology is LeftToRight, most of the "Illustrative NMR" example files are written with chronology RightToLeft and therefore do not execute correctly.

Bug reports / Needs["Rotations`OrientationalSampling`"] (SD 2.5.5)
« on: February 05, 2013, 12:11:57 PM »
When loading the sub-package OrientationsAndWeights there appears a very helpful message stating the in-built sampling sets that one can use:

Code: [Select]

However, if one executes the above code again, the message disappears and it cannot be recovered (as far as I know) without restarting Mathematica's Kernel. 

While the list of available sampling schemes can still be obtained using

Code: [Select]
it would be nice to make the message with "Needs" permanent.

It appears that there is a bug with ExpressOperator handling ShiftAndPolarizationOperatorBasis in SD 2.55.  The result after evaluating

Code: [Select]
 opI[1, "\[Alpha]"],

gives an operator with norm Sqrt[2], whereas the correct norm is 1.  For the following cases, however, everything works as expected, i.e. the operator norm is preserved:

Code: [Select]
 opI[1, "z"],


Code: [Select]
 opI[1, "\[Alpha]"],

Bug reports / Composite operator basis
« on: January 16, 2013, 09:07:18 AM »
Hi everyone,
This is a post about constructing operator bases, and some problems that I'm experiencing.  I'm using SpinDynamica 2.5.5.

I would like to set an operator basis by multiplying together basis operators of two or more spin systems.

Suppose that I have two systems, {{1,1/2},{2,1/2}} and {{3,1/2}}. 
I'd like to make an operator basis for the whole system {{1,1/2},{2,1/2},{3,1/2}} as follows:


(* the operator bases for {1,2} and {3} are arbitrary, but cannot be ZeemanKetBraOperatorBasis *)



Now, up until this point it appears there are no problems.  I find that executing BasisOperators[] gives an output equal to basisops123.  CheckOperatorBasis[] outputs True.  OperatorQ applied to any of the basis operators also gives True.

However, there are serious problems when using the basis to represent superoperators.  Routines ExpressOperator, OperatorVectorRepresentation or SuperoperatorMatrixRepresentation all fail with some error message about incommensurate basis dimensions when multiplying matrices within SpinDynamica's internal workings.  Any ideas on what is at fault or where a solution may lie?

Pages: [1]