03-14-2020, 03:11 PM
I did not mean to tell that, but I expressed myself badly. I was trying to say that in the GUI the format for custom parameter values is: the values separated by commas. Like this: pi/2, pi, 3*pi/2, 2*pi
But there is the other method to feed the inputs to the plugin: The plugin can be told to read an input file. In that method one can write in the file
To use this method one has to:
1. Create a file where the inputs are. (A small Python file. The format is explained in doc.pdf)
2. In the GUI click "Read inputs from a file" to Yes.
3. In the next entry choose the file where the inputs are.
Sorry about this confusion. I have been making this plugin so long that my solutions have become quite obvious to me, and it is hard to explain everything to somebody else clearly enough. Another thing where there is much to learn.
But I believe that I can quite easily make the plugin accept what you were trying to put in the GUI. Coming soon.
I would like to say a couple of words about why I decided to have these two ways to feed the inputs to the plugin: (1) typing everything in the fields in the GUI, or (2) creating a small Python file where the inputs are.
Method (1) is easy and good for a quick work. But if the functions x(t) and y(t) are complicated, this is tedious.
Method (2) allows much more complicated parametric curves, even such that cannot (in practice) be written in the form f(t)=(x(t),y(t)). And if it is complicated, it is much more comfortable to write it in a file, editing, changing, and saving at will.
But there is the other method to feed the inputs to the plugin: The plugin can be told to read an input file. In that method one can write in the file
Code:
custom_params = [k*pi/2 for k in range(4*N)]To use this method one has to:
1. Create a file where the inputs are. (A small Python file. The format is explained in doc.pdf)
2. In the GUI click "Read inputs from a file" to Yes.
3. In the next entry choose the file where the inputs are.
Sorry about this confusion. I have been making this plugin so long that my solutions have become quite obvious to me, and it is hard to explain everything to somebody else clearly enough. Another thing where there is much to learn.
But I believe that I can quite easily make the plugin accept what you were trying to put in the GUI. Coming soon.
I would like to say a couple of words about why I decided to have these two ways to feed the inputs to the plugin: (1) typing everything in the fields in the GUI, or (2) creating a small Python file where the inputs are.
Method (1) is easy and good for a quick work. But if the functions x(t) and y(t) are complicated, this is tedious.
Method (2) allows much more complicated parametric curves, even such that cannot (in practice) be written in the form f(t)=(x(t),y(t)). And if it is complicated, it is much more comfortable to write it in a file, editing, changing, and saving at will.