#Boundingbox
Du får sende boundingbox med røyksignaler så fikser jeg WMS- eller featuretiles på papir i konvolutt.
November 13, 2026 at 2:30 PM
CVAT Annotation Tools Review | Watch in English Dubbed | For Work from Home | Remote Jobs

👉 YouTube: youtube.com/shorts/4KCcn...

Subscribe & Watch Your Favourite AI Data Annotation Channel.

#CVAT #AIDataAnnotation #DataLabelling #AnnotationExpert #Polygon #Polyline #Boundingbox #Tag #Tracking
September 21, 2026 at 3:53 PM
oh hey that's pretty!!!
Mapper has received some updates btw!!! i looked back at it and found strength to finally add some stuff that i wanted... but first the global variables had to go, cause i felt bad for using them
#C #programming #github #Mapper
November 9, 2024 at 9:37 AM
wild to me that people really used to write code like this (Go4 Design Patterns, p. 166)
November 22, 2023 at 2:00 PM
Een mooie hack die ik daarbij toepaste was dat het PS file loog over z’n BoundingBox, zodat ik bij grafieken de y-as met de linker marge kon uitlijnen. (Ok, had ook anders gekund, maar met meer stappen)
August 22, 2023 at 3:23 PM
If you want to get started in package development in #JuliaLang and help fix a super easy bug in our SDM package, head over to GitHub! I'll walk you through the process.
Calling boundingbox on a set of occurrences should ignore the occurrences with no coordinates · Issue #409 · PoisotLab/SpeciesDistributionToolkit.jl
Currently, calculating the boundingbox for a set of occurrences returns a tuple with missing elements, if some occurrences do not have coordinates — this happens when GBIF requests don't use the ha...
github.com
March 17, 2025 at 3:09 PM
pivotpointのboundingboxとそれぞれの原点の違いが理解不能な末に生まれたテトラポットくん.ありがとう…君のお陰で3時間の激闘を経てやっと理解できたよ….
August 25, 2025 at 6:12 PM
%!PS-Adobe-3.0
%%Title: Error
%%Creator: PostScript Printer
%%Pages: 1
%%BoundingBox: 0 0 612 792
%%EndComments

PostScript Error
Type: undefined

Offending Command: /foo

Operand Stack:
0 1 2 3 (Hallo Welt)

Execution Stack:
0 1 2 3 (Hallo Welt)
--nostringval--
exec
Dictionary Stack:
November 30, 2025 at 7:55 PM
BoundingBox from Nesting Study component's with wrong values
Hi, I'd attached a design which contains a set of components, and a Manufacturing Model which is the result of a Nesting Study. I noticed the BoundingBox's height of two occurrences in the model (manufacturing model's main occurrence and "cta" occurrence) are not correct. This is the information I gather: 1. From the GUI -> Manufacture workspace -> editing the "Sheet.47" manufacturing model: 1.1 From Properties of the root component in the manufacturing model: It says the height is 23.075", when it is 1.625". Also notice the Center of Mass's height is 0.8124" which is the correct value. 1.2 From Properties of the "cta:1" occurrence/component: Same inconsistency than in the above imagen. All other occurrences/components are 1.625" height, which are correct. 2. Information from the data model: Look at the highlighted values in the boundingBox properties, which are not consistent with the model. All other values from preciseBoundingBox and orientedMinimumBoundingBox are correct. Even the other boundingBox reported from the boundingBox2 method with every type of boundingBoxEntityTypes are correct. Just to notice that "cta:1" occurrence contains only one BRepBody. I used the following script to generate the above information: def cms_array_to_inchs(lst: list[float], places: int = 8, decs: int = 4) -> list[str]: return([f'{x / 2.54:{places}.{decs}f}' for x in lst]) def bb_to_str(bb: adsk.core.BoundingBox3D) -> str: if bb: return(f'{cms_array_to_inchs(bb.minPoint.asArray())}~{cms_array_to_inchs(bb.maxPoint.asArray())}') else: return("") def obb_to_str(obb: adsk.core.OrientedBoundingBox3D) -> str: if obb: dims: list[float] = [obb.length, obb.width, obb.height] return(f'{cms_array_to_inchs(dims)} (len, wid, hei)') else: return("") TIT_LEN: int = 75 bbets: dict[str, int] = { "AllEntities": adsk.fusion.BoundingBoxEntityTypes.AllEntitiesBoundingBoxEntityType, "Contruction": adsk.fusion.BoundingBoxEntityTypes.ConstructionBoundingBoxEntityType, "MeshBody": adsk.fusion.BoundingBoxEntityTypes.MeshBodyBoundingBoxEntityType, "Sketch": adsk.fusion.BoundingBoxEntityTypes.SketchBoundingBoxEntityType, "SolidBrepBody": adsk.fusion.BoundingBoxEntityTypes.SolidBRepBodyBoundingBoxEntityType, "SurfaceBody": adsk.fusion.BoundingBoxEntityTypes.SurfaceBodyBoundingBoxEntityType } def print_dimensions() -> None: manuf_model: adsk.cam.ManufacturingModel = cam.manufacturingModels[0] app.log(f'1. Manufacturing Model "{manuf_model.name = }":') app.log(f' {"manuf_model.occurrence.boundingBox:":{TIT_LEN}} {bb_to_str(manuf_model.occurrence.boundingBox)}') app.log(f' {"manuf_model.occurrence.preciseBoundingBox:":{TIT_LEN}} {bb_to_str(manuf_model.occurrence.preciseBoundingBox)}') app.log(f' {"manuf_model.occurrence.orientedMinimumBoundingBox:":{TIT_LEN}} {obb_to_str(manuf_model.occurrence.orientedMinimumBoundingBox)}') for name, bbet in bbets.items(): app.log(f' {f"manuf_model.occurrence.boundingBox2({name}BoundingBoxEntityType):":{TIT_LEN}} {bb_to_str(manuf_model.occurrence.boundingBox2(bbet))}') app.log('2. Occurrences in manuf_models:') for occu in manuf_model.occurrence.component.occurrences: app.log(f'--------> {occu.name = :15}') app.log(f' {"occu.boundingBox":{TIT_LEN}} {bb_to_str(occu.boundingBox)}') app.log(f' {"occu.preciseBoundingBox":{TIT_LEN}} {bb_to_str(occu.preciseBoundingBox)}') app.log(f' {"occu.orientedMinimumBoundingBox":{TIT_LEN}} {obb_to_str(occu.orientedMinimumBoundingBox)}') for name, bbet in bbets.items(): app.log(f' {f"occu.boundingBox2({name}BoundingBoxEntityType):":{TIT_LEN}} {bb_to_str(occu.boundingBox2(bbet))}') app.log(" ") I notice this same error in a more complex design project, when the inconsistencies were even replicated to the boundingBox properties in edges and vertices in the data model. I believe this is a bug in the product. Please your help on the diagnostic of this error. Regards, Jorge Jaramillo
forums.autodesk.com
October 23, 2025 at 1:33 AM
BoundingBox from Nesting Study component's with wrong values
Hi, I'd attached a design which contains a set of components, and a Manufacturing Model which is the result of a Nesting Study. I noticed the BoundingBox's height of two occurrences in the model (manufacturing model's main occurrence and "cta" occurrence) are not correct. This is the information I gather: 1. From the GUI -> Manufacture workspace -> editing the "Sheet.47" manufacturing model: 1.1 From Properties of the root component in the manufacturing model: It says the height is 23.075", when it is 1.625". Also notice the Center of Mass's height is 0.8124" which is the correct value. 1.2 From Properties of the "cta:1" occurrence/component: Same inconsistency than in the above imagen. All other occurrences/components are 1.625" height, which are correct. 2. Information from the data model: Look at the highlighted values in the boundingBox properties, which are not consistent with the model. All other values from preciseBoundingBox and orientedMinimumBoundingBox are correct. Even the other boundingBox reported from the boundingBox2 method with every type of boundingBoxEntityTypes are correct. Just to notice that "cta:1" occurrence contains only one BRepBody. I used the following script to generate the above information: def cms_array_to_inchs(lst: list[float], places: int = 8, decs: int = 4) -> list[str]: return([f'{x / 2.54:{places}.{decs}f}' for x in lst]) def bb_to_str(bb: adsk.core.BoundingBox3D) -> str: if bb: return(f'{cms_array_to_inchs(bb.minPoint.asArray())}~{cms_array_to_inchs(bb.maxPoint.asArray())}') else: return("") def obb_to_str(obb: adsk.core.OrientedBoundingBox3D) -> str: if obb: dims: list[float] = [obb.length, obb.width, obb.height] return(f'{cms_array_to_inchs(dims)} (len, wid, hei)') else: return("") TIT_LEN: int = 75 bbets: dict[str, int] = { "AllEntities": adsk.fusion.BoundingBoxEntityTypes.AllEntitiesBoundingBoxEntityType, "Contruction": adsk.fusion.BoundingBoxEntityTypes.ConstructionBoundingBoxEntityType, "MeshBody": adsk.fusion.BoundingBoxEntityTypes.MeshBodyBoundingBoxEntityType, "Sketch": adsk.fusion.BoundingBoxEntityTypes.SketchBoundingBoxEntityType, "SolidBrepBody": adsk.fusion.BoundingBoxEntityTypes.SolidBRepBodyBoundingBoxEntityType, "SurfaceBody": adsk.fusion.BoundingBoxEntityTypes.SurfaceBodyBoundingBoxEntityType } def print_dimensions() -> None: manuf_model: adsk.cam.ManufacturingModel = cam.manufacturingModels[0] app.log(f'1. Manufacturing Model "{manuf_model.name = }":') app.log(f' {"manuf_model.occurrence.boundingBox:":{TIT_LEN}} {bb_to_str(manuf_model.occurrence.boundingBox)}') app.log(f' {"manuf_model.occurrence.preciseBoundingBox:":{TIT_LEN}} {bb_to_str(manuf_model.occurrence.preciseBoundingBox)}') app.log(f' {"manuf_model.occurrence.orientedMinimumBoundingBox:":{TIT_LEN}} {obb_to_str(manuf_model.occurrence.orientedMinimumBoundingBox)}') for name, bbet in bbets.items(): app.log(f' {f"manuf_model.occurrence.boundingBox2({name}BoundingBoxEntityType):":{TIT_LEN}} {bb_to_str(manuf_model.occurrence.boundingBox2(bbet))}') app.log('2. Occurrences in manuf_models:') for occu in manuf_model.occurrence.component.occurrences: app.log(f'--------> {occu.name = :15}') app.log(f' {"occu.boundingBox":{TIT_LEN}} {bb_to_str(occu.boundingBox)}') app.log(f' {"occu.preciseBoundingBox":{TIT_LEN}} {bb_to_str(occu.preciseBoundingBox)}') app.log(f' {"occu.orientedMinimumBoundingBox":{TIT_LEN}} {obb_to_str(occu.orientedMinimumBoundingBox)}') for name, bbet in bbets.items(): app.log(f' {f"occu.boundingBox2({name}BoundingBoxEntityType):":{TIT_LEN}} {bb_to_str(occu.boundingBox2(bbet))}') app.log(" ") I notice this same error in a more complex design project, when the inconsistencies were even replicated to the boundingBox properties in edges and vertices in the data model. I believe this is a bug in the product. Please your help on the diagnostic of this error. Regards, Jorge Jaramillo
forums.autodesk.com
October 22, 2025 at 11:34 PM
Ooh I see! That makes sense, thank you.
When I have a break today I will take a closer look at the other physics simulations, on my way to uni I was reading the boundingbox c:
November 6, 2024 at 2:00 AM
Most of the time things are Ok with moving the BoundingBox to the header and then using ps2pdf... most of the time.
July 22, 2025 at 7:21 PM
as long as you can move the BoundingBox to the start of the encapsulated postscript file (i have a 27 year old python script that does this for me).
July 22, 2025 at 7:19 PM
駐車、ひいては後退運転、車体の形でブレるので、車体のBoundingBoxと駐車場のinnerBoxに合わせてハンドルを切る、切れるのは前輪、後輪側は押される、という制約が体に入るかどうかなところがある。
September 23, 2025 at 11:57 PM
- No recortes los elementos, ve poniendo capas una encima de otra (como si fuese AE o PSD) para poder expandir o ajustar bordes de forma controlada.
- Cuida tu BoundingBox, mejor en los Merge, pero también con Crop y CopyBBox.
- En cuanto puedas usa el nodo Remove (en modo Keep) para quitar canales.
December 4, 2024 at 9:03 AM
Al volume del boundingbox!
January 31, 2026 at 8:12 AM