We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
On Physics_2B_conservation_law_2D.ipynb tutorial notebook on the section: reg_loss = model.reg(lamb_l1=1., entropy_offset=1e-4, lamb_coef=1.)
reg_loss = model.reg(lamb_l1=1., entropy_offset=1e-4, lamb_coef=1.)
it says MultKAN.reg() got an unexpected keyword argument 'entropy_offset' and if I am remove this statement and retry as
it says MultKAN.reg() missing 3 required positional arguments: 'reg_metric', 'lamb_entropy', and 'lamb_coefdiff'
I dont know how to handle these arguments and what is the best values for this tutorial problem.
The text was updated successfully, but these errors were encountered:
I understand now it means regularization and we can choose between
reg_metric : the regularization metric 'edge_forward_spline_n', 'edge_forward_spline_u', 'edge_forward_sum', 'edge_backward', 'node_backward' lamb_l1 : float l1 penalty strength lamb_entropy : float entropy penalty strength lamb_coef : float coefficient penalty strength lamb_coefdiff : float coefficient smoothness strength I hope that when you are free, you can fix the tutorial.
Sorry, something went wrong.
No branches or pull requests
On Physics_2B_conservation_law_2D.ipynb tutorial notebook on the section:
reg_loss = model.reg(lamb_l1=1., entropy_offset=1e-4, lamb_coef=1.)
it says MultKAN.reg() got an unexpected keyword argument 'entropy_offset' and if I am remove this statement and retry as
it says
MultKAN.reg() missing 3 required positional arguments: 'reg_metric', 'lamb_entropy', and 'lamb_coefdiff'
I dont know how to handle these arguments and what is the best values for this tutorial problem.
The text was updated successfully, but these errors were encountered: