Open joshjob42 opened 2 years ago
Quandary always sets the first and last two B-spline coefficients to zero, such that the resulting control pulses always start and end at zero at time t=0 and final time t=T.
The ordering of the coefficients for the Bspline amplitudes in Quandary is the following: For each oscillator, iterate over splines first, then each iterates over carrier waves, then each contains two elements (real and imaginary part). Therefore, in your case where you have two oscillators (row 1-60 and 61-120 respectively), each with 10 splines and 3 carrier waves, Quandary will set the first and last 12 parameters to zero for each oscillators: row 1-12, 48-60 (for oscillators 1) as well as 61-72, 108-120 (for oscillators 2) will be set to zero. The number 12 corresponds to 2 splines each with 3 carrier waves and each with a real and imaginary part (12=2splines3carrier2).
As far as I know, Juqbox also does set the first and last two spline coefficients to zero, for the same reason. So I suspect that the reordering you did is not entirely correct.
Given the following .cfg and pcof description (just an example of seemingly a general feature) quandary seems to be eliminating or setting to zero a set of the parameters. Seemingly no matter what settings I use, some of the parameters are ignored. I'm trying to translate some pulses from Juqbox to quandary as in #8 , but keep running into this odd behavior.
params.dat:
The params.dat in the output data folder:
In general it looks quandary for this system is doing something like setting blocks of 12 coefficients to 0 or including/importing them as is with the pattern [0,1,1,1,0,0,1,1,1,0] (derived from other tests with full parameter vectors). I've tried many different permutations of potential maps from Juqbox to quandary, and varied things like maximum amplitudes, etc., but this problem repeats.
Any help or insight here would be hugely appreciated.