Jump to content


  • Posts

  • Joined

  • Last visited

jb22's Achievements


Member (1/2)



  1. Patrick, thanks for putting my thoughts in a bit more understandle sentences This is exactly what I wanted to ask. For a different project I am using a shared library of a SPICE implementation. In order to run individual simulations in parallel I have to create separate copies of the shared library and load each thread/process with its own library to avoid conflicts. I assume creating multiple copies of the SystemC library might do the trick as well. But I have to figure out the details and test it first to be sure. Cheers, Jens
  2. Hi Sumit, thanks for the clarification. Cheers, Jens
  3. I'd like to catch up on this with another question. This is also SystemC-AMS related, but I think it might fit in this thread. I want to simulate larger modular electrical networks making use of a compute cluster I have available. As I have learned from the previous posts it is not possible to run on multiple cores as SC_THREAD only creates virtual parallelism, but everything will run within one OS thread/process. Using openMP for parallelizing execution, could I call sc_main from a parallel for loop? In other words I'd wrap SystemC code within a regular C++ application and spawn processes on C++ level. Will there be any conflicts between the parallel invocations of the systemc header files and the shared library (e.g. global variables)? Thank you very much Cheers, Jens
  4. Torsten, thanks a lot. I will have a look at the documents and post any relevant feedback to this little project. Until then cheers Jens
  5. Hi, Torsten, thanks for your detailed feedback. I understand that you are rather skeptical about this idea of memristors in SystemC-AMS. And I can follow your argumentation. However, my stubbornness demands trying it out myself to make a better judgement on memristors in SystemC-AMS as well as the overall capabilities. I will follow the advice of sticking to TDF in a first step. Contrary to me, it seems that you are knowing what it takes to implement a memristor in SystemC-AMS. If by any chance you have some material on that (cpp file, short paper, etc.), I would really appreciate further support. @Sumit, Belated, I also liked your post to my question. I hope you can get rid of this shameful "newbie" status as soon as possible cheers Jens
  6. Hi, I am sorry for the late reply. I didn't realize you guys did write something. @dakupoto Yes, your suggestion about putting an ELN module within the TDF framework is the way to go. And with some examples from the User guide and the LRM I just got it running. Thanks for your input. However, I after reading through the documents and trying to understand the concepts of the whole AMS extension I consider your idea of just using TDF. I have to ways to describe the mermistor - either purely mathematically (in TDF then probably) or build by ELN components like resistors and some voltage controlled current sources. @Sumit Thanks for your response. These are some good points you made. You are right that at this point I want to verify how well SystemC-AMS can model a memristor. But this is just a first step of creating a higher level simulation framework that would incorporate memristors. In later steps I would than use SystemC more on the macro level. I am aware of the fact that I am not replacing SPICE with that and that the simulation results will not be as accurate. But this is the purpose of this experiment. Trying to figure out how much accuracy one can trade off for simulation speed and system integration. You mentioned the non-linear solver. Can you give me some more information on that? What are your concerns? Maybe you can point me to some documents I could study. Using Verilog-AMS might be an option. But does it give significant better results for non-linear problems than SystemC-AMS does? Verilog-AMS is supposed to simulate some orders of magnitude faster than SPICE ("On the Simulation Performance of Contemporary AMS Hardware Description Languages"). But this speed improvement has to be based on some generalizations I guess. I would appreciate any further comments from you that would help me better estimate chances and limitations of SystemC-AMS in this context. Thanks a lot (and sorry again for the late reply) Jens
  7. Hi Philipp, sorry for the late reply and thanks for the advice. I was busy with other things and could not spend much time on it. For now I have it running under cygwin - which is only a temporal solution. As soon I got back to the installation issue I will post my solution here. Cheers Jens
  8. Hi All, I am currently working with memristors (non-linear resistors with memory effect) that I am modeling in SPICE. I would like to cross check if a SystemC-AMS implementation would give sufficient results in terms of accuracy. To start with I would like to use simple resistor circuits with a sine voltage for example. This I would than adapt step by step to my final setup. So basically what I am looking for is an example file that has a source, one or two resistors and as less as possible overhead. Can anyone point me to such a source or does anyone have that done and would like to share it? Thanks in Advance Jens
  9. Hi All, I was trying to install systemc-2.3.0 (and 2.2.0 for cross checking) on Ubuntu 12.04. For the best of my knowledge I followed the instructions given in the INSTALL file of the systemc package. However, when doing "make" I am getting the following error: libtool: compile: g++ -DSC_INCLUDE_FX -I. -I../../../../src/sysc/qt -I../../../../src -Wall -m32 -O3 -pthread -c ../../../../src/sysc/qt/qt.c -o libqt_la-qt.o >/dev/null 2>&1 make[3]: execvp: ../../../../src/sysc/qt/config: Permission denied make[3]: *** [configuration] Error 127 make[3]: Leaving directory `/home/icke/systemc-2.3.0/objdir/src/sysc/qt' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/home/icke/systemc-2.3.0/objdir/src/sysc' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/icke/systemc-2.3.0/objdir/src' make: *** [all-recursive] Error 1 I also tried to run "sudo make" as "permission denied" might imply, but it didnt change it. As this happens with both systemc packages (2.2. and 2.3.) this might also be something Ubuntu related, but I can't find any helpful information online. Any suggestions? Thanks in advance Jens
  • Create New...