octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Sci-cosim toolbox approval for source forge


From: Romanov Alexey
Subject: Re: Sci-cosim toolbox approval for source forge
Date: Sat, 05 Dec 2015 21:34:20 +0300

05.12.2015, 19:45, "Doug Stewart" <address@hidden>:
> On Sat, Dec 5, 2015 at 8:30 AM, Romanov Alexey <address@hidden> wrote:
>> Thanks for help. I've created wiki page with installation guide 
>> http://wiki.octave.org/Sci_cosim.
>> Can you have a look, if there is something else I should add?
>>
>> Alexey Romanov
>
> Alexey, on this list email system we all put our answers at the bottom of the 
> email. please also do this.
>
> Thank you for this nice pkg and all the hard work you have done.
> The wiki looks good.
> the next step is to explain to an octave user, that has never run Scilab, how 
> to modify an existing demo
> and/or make a new demo in scilab.
>
> I think we should build up a library of demos, that an octave user would 
> want, so they have a starting point to build on.
>
> I am in controls so I will make one with a PID loop and a plant that has a 
> delay in it.
>
> Would you like to explain how to edit an existing file in Scilabl?
>  ( how to initialize all variables in the work-space so that the file can be 
> modified.)
>
> Doug
>
>> 04.12.2015, 19:16, "Doug Stewart" <address@hidden>:
>>
>>> On Fri, Dec 4, 2015 at 9:19 AM, Romanov Alexey <address@hidden> wrote:
>>>> 04.12.2015, 16:02, "Doug Stewart" <address@hidden>:
>>>>
>>>>> On Fri, Dec 4, 2015 at 7:22 AM, Doug Stewart <address@hidden> wrote:
>>>>>> On Fri, Dec 4, 2015 at 1:49 AM, Romanov Alexey <address@hidden> wrote:
>>>>>>> 04.12.2015, 02:13, "Doug Stewart" <address@hidden>:
>>>>>>>
>>>>>>>> On Thu, Dec 3, 2015 at 4:29 PM, Romanov Alexey <address@hidden> wrote:
>>>>>>>>> have you installed Toolbox backdoor in Scilab? It can be installed 
>>>>>>>>> with atoms manager (technical category)
>>>>>>>>> After installation scilab should  print in console, that backdoor 
>>>>>>>>> toolbox had started
>>>>>>>>> Please contact me if it  won't  help
>>>>>>>>>
>>>>>>>>> Alexey Romanov
>>>>>>>>
>>>>>>>> How do you install toolbox backdoor in Scilab?
>>>>>>>> I need to know all the steps to make this work.
>>>>>>>>
>>>>>>>> --
>>>>>>>> DAS
>>>>>>
>>>>>> On Fri, Dec 4, 2015 at 1:49 AM, Romanov Alexey <address@hidden> wrote:
>>>>>>> 1)Start Scilab
>>>>>>> 2)Press MainMenu->Applications->Module manager ATOMS
>>>>>>> 3)In the list choose Technical
>>>>>>> 4)Then choose Backdoor
>>>>>>> 5)Mark autoload tick in the bottom-left
>>>>>>> 6)Press Install
>>>>>>> 7)Restart Scilab
>>>>>>> 8)After restart it will print something like
>>>>>>> BackDoor: listening to connections on TCP port 28020
>>>>>>>
>>>>>>> Now you can start Octave and connect to Scilab with sci_connect function
>>>>>>>
>>>>>>> Alexey Romanov
>>>>>>
>>>>>> Thank you this was very helpful.
>>>>>>
>>>>>> I am on Ubuntu 15.10 and I found that item 5) could not be done in that 
>>>>>> order.
>>>>>> It was done automatically for me when I did 6)
>>>>>>
>>>>>> So now it makes a connection :-)
>>>>>>
>>>>>> I next tried the example that was in your pkg and it ran to the point of 
>>>>>> opening the .mat file.
>>>>>> Here it gave an error message:
>>>>>>
>>>>>> error: load: unable to determine file format of 'sci_vars_transfer.mat'
>>>>>>
>>>>>> With a little bit of debugging I found the the .mat file was empty.
>>>>>>
>>>>>> So at line 35 in sci_getvar.m you have:
>>>>>>    
>>>>>> cmd=sprintf('\\savematfile(''sci_vars_transfer.mat'',%s,''-v7'');\n',arglist);
>>>>>>     send(sci_sim_client,cmd);
>>>>>>
>>>>>> This results in an empty .mat file.
>>>>>>
>>>>>> What can I do to further help you to get this working.
>>>>>>
>>>>>> I have used scilab before and have some files that do transmission line 
>>>>>> reflection demos
>>>>>> that I want to get going from Octave.
>>>>>>
>>>>>> Doug
>>>>>>
>>>>>> DAS
>>>>>
>>>>> I see now that I am trying to run a file in Scilab, that doesn't exist.
>>>>>
>>>>> Could you make a complete demo that works please.
>>>>>
>>>>> --
>>>>> DAS
>>> WE bottom post so I moved your comment down ere
>>>
>>> Your problem is that your are trying to run script directly from octave 
>>> package problem.
>>>
>>> To run demo you should be in the same folder with sci_ap_model.xcos. The 
>>> Scilab should be started, and your user should have rights to use sockets 
>>> and to write in current folder.
>>>
>>> This is the same as with Simulink you should be in the same folder with 
>>> .mdl file.
>>>
>>> The second problem is that Octave package manager doesn't copy .xcos file 
>>> from package during installation.
>>>
>>> So for the easiest quick start extract.  sci_sim_example.m and  
>>> sci_ap_model.xcos from package archive to one folder. And then run  
>>> sci_sim_example.m from this folder.
>>>
>>> This script will init some variables in Octave then transfer them to Scilab 
>>> workspace, then run simulation in xcos, and the return simulation results 
>>> back to Octave.
>>>
>>> Is there any better method to share examples with package in Octave, then 
>>> just include it in the main source?
>>>
>>> Alexey Romanov
>>>
>>> OK with your help I now have your demo working.
>>>
>>> We need a good wiki page to explain all this. Can you do that at
>>> http://wiki.octave.org/
>>>
>>> I noticed a typo in sci_sim_example.m
>>> on line 20 you say
>>>   sci_setvar('k','stp','Tau','Tf'); %Transferring variables to MATLAB
>>> but it should be
>>>   sci_setvar('k','stp','Tau','Tf'); %Transferring variables to Scilab
>>>
>>> --
>>> DAS
>
> --
> DAS

Hi, 
I've added "usage cases" section on the wiki page. Octave users has never run 
Scilab do not need any knowledge, except how to use Xcos. And the best way to 
study it, is too read Xcos manuals. The most of functions from Scilab toolboxes 
also can be used without any examples, just after studying corresponding help 
pages.

So from my point of view it's better to modify help pages, then create more 
demos. But anyway I can add your demo to the repository, when you finish it. 



reply via email to

[Prev in Thread] Current Thread [Next in Thread]