The Design Automation API allows you to run ‘headless’ versions of Autodesk desktop products in the cloud, into which you can load your add-ins (with the UI stripped out) in order to perform batch automation tasks. There are two endpoint that incur a consumption cost: Currently supported products are Inventor, Revit, 3DS Max and AutoCAD. These APIs set a task running on the Forge server. No other Design Automation endpoint incurs a charge, but they all require a Forge subscription (or Trial).īecause this API allows you to run your own add-in ‘in the cloud’, a single API call could result in a task that lasts 1 second or 1 hour. ![]() Therefore, the consumption for this API is charged on the amount of processor time on the server that your task takes – this is the time from when a task starts uploading files to when is has finished downloading your results. 4 CCs per hour of processing time for AutoCAD.6 CC per hour of processing time for Revit, Inventor and 3DS Max.Ī good way to make an initial estimate of the cost of using this API is to time how long the same operation takes with the same add-in running on a desktop copy of Revit, Inventor, 3DS Max or AutoCAD. ![]() ![]() I recommend you also ready this excellent blog post by Adam Nagy and Augusto Goncalves that provides additional information to help you estimate your Design Automation API costs. There is one endpoint that incurs a consumption cost: The Reality Capture API is a photogrammetry API - it allows you to convert a set of photos of an object into a 3D mesh. No other Reality Capture API incurs a charge, but all require a Forge subscription (or Trial). The consumption cost for this API is 3.5 CCs per gigapixel processed, so you can easily calculate the cost of calling this API from knowing how many photos and at what resolution you plan to process. There is no consumption charge for any endpoint other than those described above. However, some of them require that you purchase a Forge subscription (or add Forge to your EBA contract) in order to use them. In order to call any Forge API, you first need to authenticate your application so that the Forge service knows you are a legitimate user. In the case of 3-legged authentication, this also allows a BIM 360 Docs, Fusion 360 or Fusion Team user to grant your application permission to access their data. You can override using the #> `.groups` argument. ![]() Mods %>% summarise (rmse = sqrt ( mean ( ( pred - data $ mpg ) ^ 2 ) ) ) #> `summarise()` has grouped output by 'cyl'.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |