Support.Tulipp.eu

The sample period is now in seconds, so if you want 1 second you should put a 1 in the box.

Export feature added. You find it in the "File" menu.

Good, that looks like ok, and due to I running the Linux system in the board now, so the elf and bitstream don't upload by the LynSyn board that loading by boot file in the board. The collected power data directly from the sensor, maybe, the function data can't be collected now? However, you can ad...

Thanks. I'll probably do this before the end of the week.

I have added this feature request to the github issue tracker:
https://github.com/tulipp-eu/sthem/issues/10

Further status about the development of this feature will be given there.

I wanted a suggestion for how you want the data file formatted. One example could be like this:

=== test.csv start here ===
Time;Power;Function name
0.0001;6.2;main()
0.0003;7.2;main()
0.0012;5.5;otherFunction()
=== test.csv end here ===

Would this be OK?

Hi The data is stored in an sqlite database file (profile.db3). You can use the sqlitebrowser to access the data. However, I should probably make an export function that exports to a csv file. If you provide me with a description (or example) of how you would like to have the data exported, I will m...

If you do not want to recompile everything, it should be sufficient to just delete the profile.db3 file within the ~/.tulipp/<project_name>/ directory.

This should of course not happen. Is there any chance that you have tried the analysis tool several versions ago? If so, there could be a problem with your measurement database having the wrong schema. If that is the case, please enter the following command:

$ rm -rf ~/.tulipp

Then try again.

Strange. Seems like your c++ compiler does not accept c++11. I have now added the c++11 flag to the Makefile, hopefully that will fix it.

I am finally back from christmas vacation.

You should not need to use absolute paths, this sounds like a bug. I did fix something similar before christmas, but if you pulled the latest version from git shortly before you posted, you should have the new version.

I will look into it.