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

Rocket injector design optimization #165

Merged
merged 12 commits into from
Jul 14, 2021
Merged

Rocket injector design optimization #165

merged 12 commits into from
Jul 14, 2021

Conversation

jonpsy
Copy link
Member

@jonpsy jonpsy commented Jul 3, 2021

No description provided.

@review-notebook-app
Copy link

Check out this pull request on  ReviewNB

See visual diffs & provide feedback on Jupyter Notebooks.


Powered by ReviewNB

Copy link
Member

@zoq zoq left a comment

Choose a reason for hiding this comment

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

Do you need any support with the notebook?

@jonpsy
Copy link
Member Author

jonpsy commented Jul 9, 2021

Ah no, currently working on documenting. There were some talks of interactive images right?

@jonpsy
Copy link
Member Author

jonpsy commented Jul 13, 2021

@zoq @coatless @say4n Could you guys review? I think the first phase is done. Also, suggestions on the writing to make it more captivating is welcome!

@say4n
Copy link
Member

say4n commented Jul 13, 2021

👍 🟢

Hi, it looks good to me, perhaps you could commit with the cell outputs for the notebook?
(I am not sure if there is a policy regrading the same, if there is feel free to ignore this comment!)

Copy link
Member

@zoq zoq left a comment

Choose a reason for hiding this comment

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

Really enjoyed reading the notebook.

rocket_injector_design/rocket-injector-design-cpp.ipynb Outdated Show resolved Hide resolved
rocket_injector_design/rocket-injector-design-cpp.ipynb Outdated Show resolved Hide resolved
"source": [
" **The Achilles heel**\n",
" \n",
"A good injector design makes all the difference between your system performing excellently and it exploding. Unfortunately, the latter was the case for the ambitious project. \n",
Copy link
Member

Choose a reason for hiding this comment

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

The part is great.

Copy link
Member

Choose a reason for hiding this comment

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

Haha, indeed!

rocket_injector_design/rocket-injector-design-cpp.ipynb Outdated Show resolved Hide resolved
@zoq
Copy link
Member

zoq commented Jul 13, 2021

Hi, it looks good to me, perhaps you could commit with the cell outputs for the notebook?
(I am not sure if there is a policy regrading the same, if there is feel free to ignore this comment!)

I think that is a good idea, especially if you just like to read the notebook having the output would be great.

jonpsy and others added 3 commits July 13, 2021 21:09
Co-authored-by: Marcus Edel <marcus.edel@fu-berlin.de>
Co-authored-by: Marcus Edel <marcus.edel@fu-berlin.de>
Co-authored-by: Marcus Edel <marcus.edel@fu-berlin.de>
@jonpsy
Copy link
Member Author

jonpsy commented Jul 13, 2021

My line of reasoning is that if we put all the outputs up front for them it'll kill the suspence. I want them to read the notebook and subsequently execute the cell one by one, allowing it to "slowly reveal' itself.

Atleast, that's what I think.

@say4n
Copy link
Member

say4n commented Jul 13, 2021

I totally agree with that school of thought!

However, do consider that since this is the examples repository, not everyone will clone the repository and run the notebook on their systems to check out what it does. I think it may be a good option to have the output ready to view on the repository itself.

Maybe the visual results might entice someone enough to take the library for a spin! :)

@coatless
Copy link
Contributor

I think @say4n is advocating for only showing the output/graph of the last code cell. The rest are pretty hard to show unless you take the head of the pareto front (e.g first 5.)

@zoq
Copy link
Member

zoq commented Jul 13, 2021

Agreed, I would also just show the output of each cell since it allows someone to follow the notebook without actually running it. That said, in this particular case even if we run the notebook and save the output, we will not see the plot from the last cell, since images displayed with

auto im = xw::image_from_file("scatter.png").finalize();
im

are not embedded in the notebook output itself.

@jonpsy
Copy link
Member Author

jonpsy commented Jul 14, 2021

If everyone's with the motion, then it's fine by me. Do note that the final notebook will have an interactive widget, so there won't be any "visible output". We could, however, display the HEAD of the paretoFront to some avail. So, lets go with the that for now.

@say4n
Copy link
Member

say4n commented Jul 14, 2021

Looks good to me, kudos Sai! 🚀

Copy link
Member

@zoq zoq left a comment

Choose a reason for hiding this comment

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

🚀

Copy link
Contributor

@coatless coatless left a comment

Choose a reason for hiding this comment

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

🚀 🌔

@zoq zoq merged commit 77882cb into mlpack:master Jul 14, 2021
@jonpsy jonpsy deleted the rocket branch July 15, 2021 04:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants