You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"Having a fixed frequency is not realistic in many cases. So I think there should be a time trace in every log. "
The way I have been circumventing that for now was just having the first variable be time stamps. So at least when manipulation stuff in MATLAB, you can use that trace as oppose to the fixed interval( nothing changes on clmcplot though). But it would be nice to have it actually integrated. The tricky part will be making it backwards compatible if possible
The text was updated successfully, but these errors were encountered:
"Having a fixed frequency is not realistic in many cases. So I think there should be a time trace in every log. "
The way I have been circumventing that for now was just having the first variable be time stamps. So at least when manipulation stuff in MATLAB, you can use that trace as oppose to the fixed interval( nothing changes on clmcplot though). But it would be nice to have it actually integrated. The tricky part will be making it backwards compatible if possible
The text was updated successfully, but these errors were encountered: