Anonymous | Login | Signup for a new account | 2021-01-27 20:20 UTC | ![]() |
Main | My View | View Issues | Roadmap | Repositories |
View Issue Details [ Jump to Notes ] | [ Print ] | ||||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||||
0000850 | EMStudio | General | public | 2013-06-02 01:45 | 2013-06-02 01:45 | ||||||
Reporter | Fred | ||||||||||
Assigned To | malcom2073 | ||||||||||
Priority | normal | Severity | minor | Reproducibility | N/A | ||||||
Status | assigned | Resolution | open | ||||||||
Platform | All | OS | All | OS Version | All | ||||||
Product Version | 0.0.1-SNAPSHOT | ||||||||||
Target Version | 0.0.1 | Fixed in Version | |||||||||
Summary | 0000850: Wholesale duplication of scaling data in JSON | ||||||||||
Description | I just noticed that each table has the scaling for the axis specified. I wonder if it's better to not supply it and pull it from the variable used to index that axis. It may be beneficial to retain the ability to define it in the case where the variable is not available? If so, it should be validated against the variable used for tracing. In future all possible variables will be defined in the file for sure, so it will definitely be there to reference (as opposed to copy). For now, that's not true, as the data stream format is defined in a different way. | ||||||||||
Tags | No tags attached. | ||||||||||
Issue Type | Improvement | ||||||||||
Attached Files | |||||||||||
Copyright © 2000 - 2011 MantisBT Group |