-
Notifications
You must be signed in to change notification settings - Fork 248
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
[SIAPP]Reverting P norm PR #12633
[SIAPP]Reverting P norm PR #12633
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have minor comments. Could you take a look at them?
applications/SystemIdentificationApplication/tests/test_damage_response.py
Outdated
Show resolved
Hide resolved
applications/SystemIdentificationApplication/tests/test_damage_response.py
Outdated
Show resolved
Hide resolved
applications/SystemIdentificationApplication/tests/test_damage_response.py
Outdated
Show resolved
Hide resolved
...ns/SystemIdentificationApplication/custom_sensors/measurement_residual_response_function.cpp
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Igarizza, Could you check my suggestions?
...ns/SystemIdentificationApplication/custom_sensors/measurement_residual_response_function.cpp
Outdated
Show resolved
Hide resolved
...ns/SystemIdentificationApplication/custom_sensors/measurement_residual_response_function.cpp
Outdated
Show resolved
Hide resolved
...ns/SystemIdentificationApplication/custom_sensors/measurement_residual_response_function.cpp
Outdated
Show resolved
Hide resolved
const double current_sensor_error = sensor_value - p_sensor->GetValue(SENSOR_MEASURED_VALUE); | ||
p_sensor->SetValue(SENSOR_ERROR, current_sensor_error); | ||
sum_B_p += ( std::pow( 0.5 * pow(current_sensor_error, 2) * p_sensor->GetWeight(), mPCoefficient ) ); | ||
value += p_sensor->GetWeight() * std::pow(sensor_value - p_sensor->GetValue(SENSOR_MEASURED_VALUE), 2) * 0.5; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why do you need the value
here? is it used anywhere?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
testing p=1 and old code
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
removed
// Main authors: Suneth Warnakulasuriya, | ||
// Ihar Antonau |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You can put your name also here :)
applications/SystemIdentificationApplication/tests/responses/auxiliary_files/sensor_data.json
Outdated
Show resolved
Hide resolved
"weight" : 1.0, | ||
"variable_data": {} | ||
}"""), | ||
Kratos.Parameters("""{ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are the sensors duplicated?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, with different coord.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@sunethwarna Thanks
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work. @Igarizza @sunethwarna
📝 Description
Due to some bug in the P norm gradient calculation in the parallel execution, I have reverted the code of the measurement_response back to the origin. I will debug and fix it later. This is the temporal solution.
🆕 Changelog
Please summarize the changes in one list to generate the changelog:
E.g.