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

Moving utilize builds and large datasets from wiki to primer #37

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

Conversation

EdwardChaplinArchilizer
Copy link
Contributor

Purpose

Moving How to Utilize Dynamo Builds & Efficiently Working With Large Data Sets In Dynamo from the Dynamo Wiki to the Dynamo Primer.

Key additions:

Guides on utilising Dynamo Builds and Efficiently Working with Large Data Sets In Dynamo.

The proposed location for these guides is under a new FAQ section Appendix - Frequently Asked Questions:
image

Declarations

Check these if you believe they are true

  • The codebase is in a better state after this PR
  • Is documented according to the standards
  • The level of testing this PR includes is appropriate
  • User facing strings, if any, are extracted into *.resx files
  • All tests pass using the self-service CI.
  • Snapshot of UI changes, if any.
  • Changes to the API follow Semantic Versioning and are documented in the API Changes document.
  • This PR modifies some build requirements and the readme is updated
  • This PR contains no files larger than 50 MB

Release Notes

An FAQ section with guides on utilising Dynamo Builds and Efficiently Working with Large Data Sets In Dynamo.

Reviewers

@dnenov
@achintyabhat
@QilongTang

Informed
@Amoursol

##### 7zip used for unzipping the package [here](https://www.7-zip.org/download.html)


##### Microsoft Visual C++ 2015 Redistributable [link](https://aka.ms/vs/17/release/vc_redist.x64.exe)
Copy link
Contributor

Choose a reason for hiding this comment

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

@EdwardChaplinArchilizer Would you add the link for 2019 as well or see if it's also on this page?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I have updated the text for these to say 2015-2024, which from a bit of research I've found is what the link is for. Here is a screenshot of that link one you click the .exe :
image


![](images/a-7/dynamo-builds-3.png)

##### Installing Microsoft Visual C++ 2015 Redistributable
Copy link
Contributor

Choose a reason for hiding this comment

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

not sure if the 2019 requirements are similar, maybe worth mentioning too

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I have updated the text for these to say 2015-2024, which is what the link is for. I think this makes it easier to understand that this link isn't just for a single year version.

Here's a ss from the microsoft website describing the link:
image

Geometry nodes in Dynamo are always tessellated*. This leaves you with two options to work with untessellated geometry: Python nodes and ZeroTouch nodes. As long as you don't return a geometry object out of your Python or ZeroTouch node, the geometry will not be tessellated. For instance, if your graph has several point nodes, connected to several line nodes, connected to several loft nodes, connected to several thicken nodes, the geometry will be tessellated at each step. Instead, you can bundle this logic into a Python or ZeroTouch node, and only return the final object out of the node.

More information about using ZeroTouch nodes can be found in the [Developing for Dynamo](11\_developer\_primer/3\_developing\_for\_dynamo/README.md) section of this Primer.

Copy link
Contributor

Choose a reason for hiding this comment

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

@aparajit-pratap @mjkkirschner Can you review if this section is still correct?

Copy link
Member

Choose a reason for hiding this comment

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

@QilongTang to clarify, the linked content or the geometry generation bit?

Copy link
Member

Choose a reason for hiding this comment

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

I feel like working with large data sets should be it's own gigantic ever evolving section ;) not crammed into an faq.

@mjkkirschner
Copy link
Member

how far back are we going here?
I think things have changed WRT at least directX and needing to set performance mode.

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.

3 participants