Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dutycycle symmetry #100

Open
justatry2 opened this issue Jan 23, 2023 · 3 comments
Open

Dutycycle symmetry #100

justatry2 opened this issue Jan 23, 2023 · 3 comments

Comments

@justatry2
Copy link

Testing 3C94 material with triangular waves under MagNet AI showed that losses are not symmetric in duty cycle. Why?

@minjiechen
Copy link
Collaborator

minjiechen commented Jan 30, 2023

The model is fully data driven and we try to avoid putting prior-human knowledge in developing the neural network model. Asymmetries exist in our experimental data, excitation waveform, measurement accuracy, for different duty ratios. As a result, we cannot guarantee full symmetry in the training data, and the model picks up the asymmetry.

One can develop neural network models that will produce "pure" symmetry data by reasonable hypothesis, but that is beyond our purpose. A data driven model cannot ensure full "symmetry" in experiments and in training, and the material may have intrinsic "asymmetry" due to memory effect (existing theory cannot completely rule out this possibility).

These asymmetry is more likely to happen for low core loss data, and low core loss materials. This is a fact comes from measurement raw data and the model inherits it.

@justatry2
Copy link
Author

justatry2 commented Jan 30, 2023 via email

@minjiechen
Copy link
Collaborator

Yes agreed! A model that can leverage both the strengths of data driven models and physical understanding would perform the best. We leave it to the community to find the best way to combine them.

For now, we will keep our model 100% data driven to perhaps highlight / warn the weakness of a pure data driven model - the biases / inaccuracy in data will directly transfer to biases / inaccuracy in models.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants