I have created BouncingBall FMU using OpenModelica-V1.12. I am able to Launch the FMU using Python (OMSimulator-V2.0). It works fine.
When I create the FMU using OpenModelica-V1.13 and above, unable to load the FMU in Python. Application crashes and it shows the error 'This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information'
Size of the FMU created using OpenModelica-V1.12: 16.2 MB,
Size of the FMU created using OpenModelica-V1.12 : 1.27 MB
Related
Today when we've tried running our notebooks defined in synapse, we've received constantly error: 'LIBRARY_MANAGEMENT_FAILED'. We are using approach from: https://learn.microsoft.com/en-us/azure/synapse-analytics/spark/apache-spark-manage-python-packages#storage-account to manage custom libraries, and it was working fine up until this point. Additionally, we've tried separate method of providing spark pool with custom library and tried to use workspace packages, but after 10 minutes of loading custom package, it timesouts with failure.
When we are removing python folder completely from storage, sparkpools run notebooks normally.
Yesterday everything was working properly. The problem also could not be in custom library, because it does not work even with empty python folder.
There were issues on Microsoft side, which were resolved and it started working next day.
I am using libtorch, c++ frontend, downloaded from the main page of https://pytorch.org/ and trying to profile layer by layer.
I've learn that in python i can use torch.autograd.profiler.profile. And i've read some website, including https://github.com/pytorch/pytorch/pull/16580/files#diff-81d29c29bbf9fb05edfa7fd70d189374 and https://caffe2.ai/doxygen-c/html/structtorch_1_1autograd_1_1profiler_1_1_record_profile.html
But when i use CLion to construct my code, use torch::autograd::profiler::RecordProfile , it report an error that
no member named 'profiler' in namespace 'torch::autograd
I turned to https://pytorch.org/cppdocs/api/library_root.html, and cannot find something about profiler, so how should i do to use the profiler in my project?
I can't get debugging to work.
I'm using the 2.1.0 version of REDHAWK and I'm trying to create custom components.
I can get release version to run and to work.
Here's what I do, I have created a very basic custom component that takes input, multiplies it by two and pushes it to the output stream, super simple. Now I try to run this component in debug mode in sandbox, instant crash. The only this I can see is the last entry of the callstack, which is
boost::shared_ptr<rh_logger::Logger>::operator->() at shared_ptr.hpp:653
If I choose to run my component without debugging, everything works. It even does the multiplication.
I have no idea what goes on, apparently this smart pointer class does a assert check to validate the pointer that it returns and ends up crashing because it's zero. Being the -> operator, this seems quite dangerous. SIGSEGV is the error being throw, I wonder if BOOST_ASSERT causes that on failure?
Operating system is CentOS 7 64 bit and it's running on regular desktop intel processor, can't remember which.
I installed REDHAWK by downloading the repository as instructed in 2.2 part of the REDHAWK manual.
The new component was created with the REDHAWK IDE (eclipse based), I selected C++ as the Program language. It seems to be a shared library and when I run it, a process called ComponentHost is started.
I'm trying to start the component in the sandbox via right-clicking the component in the Project menu and selecting Debug as - Component in the Sandbox. Running the component in the Release mode this way works.
I'm able to debug a component via the Python sandbox, so just a couple of variables to help narrow it down, with my test system in []:
Which operating system? [CentOS 7]
REDHAWK installed from source or RPM? [RPM]
Is this a new C++ shared library-based component (entry point type is "SharedLibrary") or executable ("Executable")? [both]
How are you launching the component? Via the Python sandbox, with with "debugger='gdb'" as an argument to launch? Any other launch arguments?
Another possible debugging approach is to launch the component normally, then attach GDB from another terminal window.
First, find the component process:
If it's a shared library:
ps -o pid,comm -C ComponentHost
If it's an executable (where "" is the component executable's name):
ps -o pid,cmd -C <name>
Hopefully, it's clear which process is your target component. If you're running multiple shared library components from the same sandbox, they will all be part of the same ComponentHost instance.
Then, attach to the process with GDB:
gdb -p <pid>
This is essentially how the sandbox attaches GDB; however, running it independently allows you to set the flow up to your liking first before attaching the debugger.
We have a windows client that our QA team wrote coded UI tests for. I'm trying to get OpenCover to work so we can see how much of the app their tests are really hitting. They wrote their tests using a custom framework on top of the MSTest framework.
Their framework uses ApplicationUnderTest.Launch to start the application as different users to test security settings. I can capture coverage of the test dlls but the application it self.
I've forced the app to build in 32bit, made sure all pdbs are present in the folders and included the pdb directory in the targetdir as well.
Has anyone else seen this issue? I also tried replacing my batch file with a wrapper exe and got coverage for that but not the main application. Everything is running as the user they are starting the application as who is also an admin on the machine.
The command I'm running is:
C:\Users\kkindt.CORP\AppData\Local\Apps\OpenCover\OpenCover.Console.exe -register "-target:C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\CommonExtensions\Microsoft\TestWindow\vstest.console.exe" -output:C:\CodeCoverage\CollectionResults\CodedUICover.xml "-targetargs:C:\CodeCoverage\Tests\EllisWinAppTest.dll /Platform:x86 /Framework:framework40 /Tests:LaunchEllisTest"
I strongly suspect it is due to how you are launching the application under test
OpenCover is a .NET profiler and for .NET application to be launched with a profiler attached requires some environment variables to be available to the new process. I suspect that ApplicationUnderTest.Launch does not propagate all the current environment variables and so the profiler does not start and therefore does not report coverage.
To get this to work you should look into using the ApplicationUnderTest.Launch overload that uses a ProcessStartInfo and then you need to propagate the following environment variables
Cor_Profiler
Cor_Enable_Profiling
OpenCover_Profiler_Key
OpenCover_Profiler_Namespace
OpenCover_Profiler_Threshold
OpenCover_Profiler_TraceByTest (if available)
The Cor_* are required by the runtime to launch a profiler and the OpenCover_* entries are to allow the profiler and the host to find each other - a list of these environment variables are available on github
I have heard a lot about Node . Recently Microsoft released a driver for accessing SQL Server through Node. I would like to do similarly create a driver to access a data source we have. The data source can be accessed using their DLLs.
For e.g. I can write a c# program and access the data.
How do I create a driver to access our data source so Node can use it ?
You'd write driver code in C or C++ as described in the C/C++ Addons section of node's documentation. It would have to compile to native code, not managed .NET code.