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

Request branch2 #22

Open
wants to merge 6 commits into
base: master
Choose a base branch
from
Open

Conversation

efekhari27
Copy link

@efekhari27 efekhari27 commented May 13, 2020

Here is the remote ReliabilityProblem functionality allowing us to build a otbenchmark ReliabilityProblem using limit state functions from the BBRC server. The useless commit have been squashed as requested. I saw that you are working on a way to build the BBRC distribution table without pandas, i'm sure it can improve this development.

@vchabri @JEBROUN pour information :)

@mbaudin47
Copy link
Collaborator

mbaudin47 commented May 15, 2020

Please translate the comment into english so as to make the repo as open as possible. Please gather the unnecessary commits created for Circle CI into a single one with "squash" with git rebase. This will clarify the PR leaving only the consistent commits for review.

circleci

circleci2

circleci3

circleci4

circleci5

circleci6
requested BBRC correction

notebook circleci issue

notebook circleci issue second try

minor changes
@efekhari27
Copy link
Author

Hi Michaël !

Here is the remote ReliabilityProblem functionality allowing us to build a otbenchmark ReliabilityProblem using limit state functions from the BBRC server. The useless commit have been squashed as requested. I saw that you are working on a way to build the BBRC distribution table without pandas, i'm sure it can improve this development.

Best
Elias

notebook metadata environnement name
@mbaudin47
Copy link
Collaborator

  • The code is excellent. The dependency to pandas is dropped and the code is as simple as can be and efficient.
  • Please fix the small conflict on the _init.py file.
  • The docstring of the RequestedBBRCProblem class formats poorly in Spyder:

image

You can reproduce it with your own Spyder with Control + I. Please insert a blank line before each section, e.g. before "Parameters".

  • Same for the docstring of BBRCDistribution.
  • The unit tests are missing for the two new classes BBRCDistribution and RequestedBBRCProblem. Please create them into the tests directory. This will allow to check the results (this is not the purpose of the NB examples).

That should be the last step before integration.

Copy link
Collaborator

@mbaudin47 mbaudin47 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good job! Significant changes are required, but these are rather easy to implement.

"source": [
"# Test de la classe RequestedBBRCProblem\n",
"\n",
"L'objectif de cet exemple est de présenter l'utilisation de la classe RequestedBBRCProblem"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please translate it into english.

"algoProb = ot.ProbabilitySimulationAlgorithm(event)\n",
"algoProb.setMaximumOuterSampling(10)\n",
"algoProb.setMaximumCoefficientOfVariation(0.01)\n",
"algoProb.run()"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please insert a comment that explains that your intent in selecting a low value of the maximumOuterSampling : it is chosen to make a fast example, but a more realistic parameter value (e.g. 1000) should be chosen in practice. This will clarify your motivations in the example. Please insert the code to print the estimated probability, because it is the concrete goal of the example but add a comment that explains that, because of the low value of the maximumOuterSampling, the estimate is not very accurate.

requirements.txt Outdated
@@ -2,6 +2,7 @@ numpy==1.16.*
matplotlib==2.*
scipy==1.*
openturns>=1.14
pandas
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The pandas dependency is not required anymore. Please remove it.

@@ -13,22 +13,21 @@

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixing the style of the unit tests is good. However, I guess that a separate PR would have made this review clearer. In this PR, it hides the fact that there is no unit test for the new classes, letting the reader think that there are unit tests, while there are not. Please avoid this for future PRs. Anyway, keep them as is for this one to smooth the process.

@mbaudin47
Copy link
Collaborator

I you need help to finalize the PR: I would be a pleasure to fix it, although I think that you would better finalize it for yourself.

Add distribution file in otbenchmark rep.

Add distribution file in otbenchmark rep. 2

Add distribution file in otbenchmark rep. 3
Copy link
Collaborator

@mbaudin47 mbaudin47 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems perfect to me.

@mbaudin47
Copy link
Collaborator

mbaudin47 commented Jun 8, 2020

@efekhari27: Please solve the conflict: this seems to be the very last required step for integration.


types = ["i4", "i4", "i4", "i4", "U15", "f8", "f8", "f8", "f8", "f8", "f8"]
bbrc_dist_table = np.genfromtxt(
"otbenchmark/distributions/probabilistic_models.csv",
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This line is problematic, because the csv file may not be available on the user's side. This makes the CI fail. Moreover, the file may not be installed on user's computer after setup.py or installed when the module is installed with pip.

@mbaudin47
Copy link
Collaborator

I will get this PR on a new branch and try to make so that it gets in the package.

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

Successfully merging this pull request may close these issues.

2 participants