# Library The Library contains all of the loaded Nodes, including the ten default categories Nodes that come with the installation as well as any additionally loaded Custom Nodes or Packages. The Nodes in the Library are organized hierarchically within libraries, categories, and, where appropriate, subcategories. ![](/files/MkhpjRlcNfbcGmF8lP7p) * Basic Nodes: Comes with default installation. * Custom Nodes: Store your frequently used routines or special graph as Custom Nodes. You can also share your Custom Nodes with the community * Nodes from the Package Manager: Collection of published Custom Nodes. We will go through the [hierarchy of Nodes](#library-hierarchy-for-categories) categories, show how you can [search quickly from the library](#search-by-hierarchy) and learn about some of the [frequently used Nodes](#frequently-used-nodes) among them. ### Library Hierarchy for Categories Browsing through these categories is the fastest way to understand the hierarchy of what we can add to our Workspace and the best way to discover new Nodes you haven't used before. Browse the Library by clicking through the menus to expand each category and its subcategory {% hint style="info" %} Geometry are great menus to begin exploring as they contain the largest quantity of Nodes. {% endhint %} ![](/files/P8Wuru59fVVnbSJzDjAS) > 1. Library > 2. Category > 3. Subcategory > 4. Node These further categorize the Nodes among same subcategory based on whether the Nodes **Create** data, execute an **Action**, or **Query** data. * ![](/files/7LdmajPCoiJJWknICj6j) **Create**: Create or construct a geometry from scratch. E.g a circle. * ![](/files/SoNK9HIpRnaqGHaSjShX) **Action**: Perform an action on an object. E.g scaling a circle. * ![](/files/8SrdXPtCzCd9FsaUid7D) **Query**: Get a property of an object that already exists. E.g get the radius of a circle. Hover your mouse over a Node to reveal more detailed information beyond its name and icon. This offers us a quick way to understand what the Node does, what it will require for inputs, and what it will give as an output. ![](/files/BHEvDnMbAlpO6gHfqem2) > 1. Description - plain language description of the Node > 2. Icon - larger version of the icon in the Library Menu > 3. Input(s) - name, data type, and data structure > 4. Output(s) - data type and structure ### Quick search in Library If you know with relative specificity which Node you want to add to your Workspace, type in the **Search** field to look up all matching Nodes. Choose by clicking on the Node you wish to add or hit Enter to add highlighted nodes to the center of the Workspace. ![](/files/i96rXQz80xy87k6iA4nl) #### Search by hierarchy Beyond using keywords to try to find Nodes, we can type the hierarchy separated with a period in the Search Field or with Code Blocks (which use the *Dynamo textual language*). The hierarchy of each library is reflected in the Name of Nodes added to the Workspace. Typing in different portions of the Node's place in the Library hierarchy in the `library.category.nodeName` format returns different results * `library.category.nodeName` ![](/files/AacB3ZuCq9cS0iclIjzq) * `category.nodeName` ![](/files/LeN6JoiA5G23hfmyMSj3) * `nodeName` or `keyword` ![](/files/8AdeXOlhpcZ3eTiAVMHi) Typically the Name of the Node in the Workspace will be rendered in the `category.nodeName` format, with some notable exceptions particularly in the Input and View Categories. Beware of similarly named Nodes and note the category difference: * Nodes from most libraries will include the category format ![](/files/04VqU1gq1xuyiW3OpAV6) * `Point.ByCoordinates` and `UV.ByCoordinates` have the same Name but come from different categories ![](/files/Lva37pRiIlE9pobGzc30) * Notable exceptions include Built-in Functions, Core.Input, Core.View, and Operators ![](/files/VqYxB0R8iwiQXat1kCqM) ### Frequently Used Nodes With hundreds of Nodes included in the basic installation of Dynamo, which ones are essential for developing our Visual Programs? Let's focus on those that let us define our program's parameters (**Input**), see the results of a Node's action (**Watch**), and define inputs or functionality by way of a shortcut (**Code Block**). #### Input Nodes Input Nodes are the primary means for the User of our Visual Program - be that yourself or someone else - to interface with the key parameters. Here are some available from the Core Library: | Node | | Node | | | -------------- | -------------------------------- | -------------- | -------------------------------- | | Boolean | ![](/files/2PRBfP7EVmwMfXp2XVkE) | Number | ![](/files/XdSG2jIY6bElGF8G40k8) | | String | ![](/files/tz9brsuKSOSXSKFzQycB) | Number Slider | ![](/files/3RcMtnnC8SSV0LKnrYdn) | | Directory Path | ![](/files/nVHdrKM6qC4msKKSI9BO) | Integer Slider | ![](/files/8rT5HtWakKdjpWxDM0su) | | File Path | ![](/files/hhPs6fREKZCLN80d7ynr) | | | #### Watch & Watch3D The Watch Nodes are essential to managing the data that is flowing through your Visual Program. You can view the result of a Node through the **Node data preview** by hovering your mouse over the node. ![](/files/pTDYj3blaK0027Nv52C0) It will be useful to keep it revealed in a **Watch** Node ![](/files/a10OLNoc3W4hCA12Qjza) Or see the geometry results through a **Watch3D** Node. ![](/files/0F5oeynm7g0PzpsyX7rp) Both of these are found in the View Category in the Core Library. {% hint style="info" %} Tip: Occasionally the 3D Preview can be distracting when your Visual Program contains a lot of Nodes. Consider unchecking the Showing Background Preview option in the Settings Menu and using a Watch3D Node to preview your geometry. {% endhint %} #### Code Block Code Block Nodes can be used to define a block of code with lines separated by semi-colons. This can be as simple as `X/Y`. We can also use Code Blocks as a shortcut to defining a Number Input or call to another Node's functionality. The syntax to do so follows the Naming Convention of the Dynamo textual language, [DesignScript](/8_coding_in_dynamo/8-1_code-blocks-and-design-script/2-design-script-syntax.md). Here is a simple demonstration (with instructions) for using Code Block in your script. ![](/files/uaTIPxzAGTHqKT3QWuIp) 1. Double-click to create a Code Block Node 2. Type `Circle.ByCenterPointRadius(x,y);` 3. Click on Workspace to clear the selection should add `x` and `y` inputs automatically. 4. Create a Point.ByCoordinates Node and a Number Slider then connect them to the inputs of the Code Block. 5. The result of the executing the Visual Program is shown as the circle in the 3D Preview --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://primer2.dynamobim.org/3_user_interface/2-library.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.