Activity for Richard C
-
Richard C committed [4f1d27] on qucsator
qucs-core.cbp: Updated code::blocks project file to add CMake build files
-
Updated mextrsolver to use qucs namespace
-
removed generated files
-
put much of code into qucs namespace with wide-ranging changes to support this
-
Merge branch 'master' of ssh://git.code.sf.net/p/qucs/git
-
Merge branch 'master' of ssh://git.code.sf.net/p/qucs/git
-
Merge branch 'master' of ssh://git.code.sf.net/p/qucs/git
-
qucs_interface.h: removed unistd.h include
-
Removed config.h include from interface headers
-
qucs-core/bootstrap.sh: actually call adms bootstrap, not autogen_lin
-
converter/Makefile.am: Updated to use libtool libraries
-
qucs-core/Makefile.am: changed autogen.sh to bootstrap.sh
-
Modifications to create qucs-core shared library
-
Added bootstrap script for adms, and call it in qucs-core bootstrap if present
-
Made into custom makefile project
-
moved autogen.sh to bootstrap.sh, and updated release.sh to reflect this. Also updated README file for qucs
-
Github is where xfemm's latest source code is stored and developed. https://github.com/Reoptimize-Systems/xfemm We use Git for development, and Github is a kind of web interface for Git. PR is short for Pull Request. Probably explaining what a pull request is is beyond the scope of this forum. At the very least, however, using the 'Issues' tab for the project to describe the problem and track it would be useful and requires no prior knowledge of git or github.
-
Even better if you can submit a PR on Github!
-
If you open a github issue it is a bit more likely to get addressed. Unfortunately there doesn't seem to be many mac users (or at least enough who complain).
-
have you run mfemm_setup?
-
-
-
Thanks, could you please submit an issue on github with an example failing script please.
-
Speaking as a long time contributor to Qucs, and the person who essentially once revived it from death with the help of others, I don't find him to be "abusing the forum" just for mentioning some alternative software. I recall a time when we actually cared about windows users and made sure there was a build, now there's barely a build available for Linux, so I don't think we can complain if people mention alternatives that they can actually use. Sadly I don't have time to help maintain Qucs any more,...
-
Actually, to be more accurate, please try with the 1.9 release. There's issues with the other releases which were never resolved.
-
Please try with the latest release. The github master is not guaranteed to work, and is WIP.
-
exactly what version are you using?
-
removed some more code for clarity
-
removed all code and added note annoncing move to github
-
main.cpp: replaced Q3 cleanDirPaths with cleanPaths
-
renamed some settings dialog code variables for clarity and added widget to display new path list setting
-
circulator.cpp: whitespace change, no logic changes
-
chnages to introduce new subcircuit search path
-
removed debugging output code
-
Added Code::Blocks makefile project file for convenience
-
changes to allow adding and removing search path entries through application settings dialog
-
qucs.cpp: fixed Go Into Subcircuit
-
qucssettingsdialog.cpp: fixed bug with empty row insertions in search path table
-
Added functionality to 'Add with Subfolders' button
-
changed string to make qucs editor to 'qucs', qucs also now used if setting is empty
-
added autogen.sh to code::blocks project file
-
fixed saved path settings load failure
-
Merge branch 'master' of ssh://git.code.sf.net/p/qucs/git
-
moved autogen.sh to bootstrap.sh, and updated release.sh to reflect this. Also updated README file for qucs
-
put much of code into qucs namespace with wide-ranging changes to support this
-
qucssettingsdialog.cpp: fixed search path button locations
-
You might need to rebuild from sources, are you on windows or linux?
-
There are issues with this version, hence the official download still being 1.9, I reccomend sticking with that for now.
-
I applied Christian's fix on Github with this commit: https://github.com/REOptimize-Systems/xfemm/commit/1335a7921937608d44b205dd108bee8c71919d57 Any further disuccion would be best done on github
-
Christian thanks for this, I will take a look at the patch. Incidentally, I just moved the code to github here: https://github.com/REOptimize-Systems/xfemm Feel free infuture to fork the github repo and send me a pull request. I'll try applying your patch when I get a chance.
-
Sorry, I was interrupted, there are issues with the development sources, Try the latest official download (in fact I'd reccommend version 1.9 for now).
-
Try the official
-
I was listening, if it helps, but unfortunately too busy to help at the moment, and have experience, or access to a mac. At some point I can see if I can merge your changes with the main code.
-
This is very interesting! Any idea when you might be able to make it public? Would really like to play around with this.
-
Hi, you can use the loadSTLMesh of the nemoh.body class for this. Theoretically this should work, but in practice I have had Nemoh throw errors with meshes imported this way.
-
I'm not the FEMM project, xfemm works differently, but I'll help you anyway. The problem is that Octave is trying to communicate with FEMM using activex, which doesn't work on Linux. You need to use the filelink method instead. You need to start femm with the --filelink option (see manual, and possibly edit openfemm to make sure it doesn't try to use the activex server. It shouldn't be trying to use the activex server, it should only do this on Windows, but it seems like it is trying to. If you want...
-
With QUCSStudio? No sorry, perhaps contact the author, the Qucs devs have no contact with anyone involved in QUCSStudio. If you want to achieve something though we can probbably explain how to do it in Qucs instead. I suggest starting a new discussion asking how to do whatever you want to do but in Qucs. We can point you to tutorials and examples for Qucs.
-
QUCSStudio is a completely differrent program from Qucs, it was forked many years ago. As such, we can't help with it, sorry.
-
QUCSStudio is a completely differrent program from Qucs, it was forked many years ago. As such, we can't help with it, sorry.
-
If I use the same .fem file in both FEMM and xfemm (the one created by writefemfile in xfemm) I get identical results from FEMM and xfemm, see the attached script. Does this also work for you? I noticed in the xfemm script you provided that you left the problem depth at 0, but in the .fem file you provided it is 1. Could there be other discrepancies?
-
Thanks, I will investigate, I forgot to ask which version of xfemm you are using? Recently (with version 2.0) there were big changes, this may have introduced a bug, You might like to try xfemm 1.9 instead, which I have made the default download again.
-
Can you share the actual problem files or xfemm scripts?
-
There's not a special mfemm mesh plotting routine yet. Before solving the best you can do is to use loadmesh_mfemm to load the mesh into a matlab structure. You would do this after running fmesher, and before running fsolver (or if you run fmesher with keepmesh set to true). You can then plot it using matlab's triplot function. after solving, using fpproc you can use getvertices and getelements then use matlab's triplot to plot it. It would look something like the following (which I've done off the...
-
If you want to know how to load Qucs data and manipulate it in Octave or Python, then naturally you must have some knowledge of these systems. I'm not sure why you would think otherwise? The tutorial is totally accurate. It explans how to use qucs (actually qucsator, the solver which Qucs uses to solve circuits by default), from the command line to generate data, using its native input format which is a netlist (text based) type file. Normally Qucs generates this netlist file from the schematic file...
-
loglog is a built in Octave function.
-
sydney, with all due respect, the problem here is that you don't know how to use Octave, not that the tutorial has a problem.
-
Unfortunately this file is not very well documented, the help for loadQucsDataSet is pretty useless. However, data is an array of Octave Structures. each one contains the data for one variable. If you have run it in octave, why noe just try running data to see what fields there are. I can't rememeber offhand, but I think each structure in the array will have a 'time' and 'data' field or something like that.
-
On my linux machine it gets installed in /opt/share/qucs/octave/loadQucsDataSet.m I dont knoe where it will go in windows, if thats your OS. EDIT, actually I mean /usr/local/share/qucs/octave/loadQucsDataSet.m
-
On my linux machine it gets installed in /opt/share/qucs/octave/loadQucsDataSet.m I dont knoe where it will go in windows, if thats your OS.
-
I thought it would be rather obvious that loadQucsDataSet is an Octave file shipped with Qucs, and not a stndard Octave function. If the tutorial has a problem, it is that the location of this file is not explained.
-
http://dd6um.darc.de/QucsStudio/faq.html See last item. Qucs is free software. If anyone wants to fork it, they can. That is the beauty of the GPL. As for why, if you want to know more than what's in his FAQ, you'll have to direct these questions to the author.
-
QucsStudio was forked from Qucs by one of the original Qucs authors many years ago. There is no mixing between Qucs and QucsStudio, it's a completely different project, with a closed source solver too.
-
Home
-
You can use subcircuit parmeters to pass the same values into all three components. You could set up the parameters for one transistor then just copy and paste. Have you seen: http://web.mit.edu/qucs_v0.0.19/docs/en/subcircuit.html It describes how to use subcircuit parameters. Chapter 16.4 of the pdf linked to below also has more information on subcircuit parameters (the workbook also has info on many other things about qucs): https://qucs.github.io/docs/tutorial/workbook.pdf Hope this is helpf...
-
You can use subcircuit parmeters to pass the same values into all three components. You could set up the parameters for one transistor then just copy and paste. Have you seen: http://web.mit.edu/qucs_v0.0.19/docs/en/subcircuit.html It describes how to use subcircuit parameters. Chapter 16.4 of the pdf linked to below also has more information on subcircuit parameters (and may other things about qucs): https://qucs.github.io/docs/tutorial/workbook.pdf
-
You can use subcircuit parmeters to pass the same values into all three components. You could set up the parameters for one transistor then just copy and paste. Have you seen: http://web.mit.edu/qucs_v0.0.19/docs/en/subcircuit.html It describes how to use subcircuit parameters. Chapter 16.4 of this pdf has more information on subcircuit parameters (and may other things about qucs): https://qucs.github.io/docs/tutorial/workbook.pdf
-
It's a .sch file, Qucs file format, you open it with Qucs.
-
You can raise a ticket with sourceforge here: https://sourceforge.net/p/forge/documentation/Request%20an%20Enhancement/ to request an enhancement with the sourceforge site.
-
Ths is a question for the sourceforge developers.
-
I'm afraid we can't help with QucsStudio. It's a fork of Qucs from a very very long time ago, and we have nothing to do with it.
-
If you're using xfemm in Octave, you can use the plotting methods of the fpproc class to show the results in a figure. Have a look at the exmple tutorial where a plot is done at the end. There are plotBField method which I guess is what you want.
-
Yes, I'm afraid the only place to switch the number of cores is in the Qucs source code, by modifying the solver to be parallelized. The small speedup you see is probably just some lower level system library like BLAS which has some parallelization.
-
Looks good, I've now merged, very useful to start adding some. One point about the...
-
Pull request are probably easiest, but it would be good to put this work on a new...
-
Home
-
Hi Johannes, ok, I just thought I'd check you'd seen that post. So, the heat flow...
-
Hi johannes, Regarding problem.h and hproblem.h, you are right, these could both...
-
Hello, mfemm_setup does two things, compiles the mex functions, and also adds the...
-
Hello, mfemm_setup does two things, compiles the mex functions, and also adds the...
-
Hi Alejandro, could you give a little more information? The problem solves fine on...
-
Sorry for taking a long time to reply. I wouldn't have any special requirements,...
-
Klaus, regarding lua scripting. to reimplement this on the command line would require...
-
I can help guide anyone who wants to help implement the other solvers. I'll start...
-
I can help guide anyone who wants to help implement the other solvers. I'll start...
-
oh, and if you take a look at the README.txt and INSTALLATION.txt files provided...
-
Morning Klaus, glad you solved your issue, yes, you must omit the '.fem' for fsolver...
-
I'd like to, but I've no specific plans, it's quite low on the list unfortunately....
-
Hi Stephane, The problem is the overlapping segments, xfemm is less forgiving than...
1 >