caseyflex

Yeah I don’t even know if this is a tolerance issue. In the backend we simply assume the mesh is exactly watertight, understanding that if it is not, this may...

I think the relevant tolerance would be tol.merge https://github.com/mikedh/trimesh/blob/main/trimesh/constants.py But we need to be a bit careful with it as it identifies vertices. The default agrees with solidworks. To be...

> How would `sim_data["field_monitor"].plot("Ex")` differ from `sim_data["field_monitor"].Ex.plot()` and `sim_data.plot_field("field_monitor", "Ex")` (assuming the latter is fixed)? function I was thinking they would all work the same way. EDIT: The problem with...

> > One question @caseyflex : do we really need to worry about zero area at all? If the area is too small, it can be just left out. >...

Yeah, no reshuffling is done, this seems to be the desired behavior. There might be some situations we could detect and warn about, but I'm not exactly sure about it.

We could discuss how to handle this elegantly. In the case of a handful of media, could just split up the 2D medium. In the case of many or custom...

I think this issue can be closed. Thanks for addressing it! On Fri, Mar 1, 2024 at 6:43 PM dmarek-flex ***@***.***> wrote: > @tylerflex @caseyflex > I think this issue...

> Thanks! I've merged your webapi PR and redeployed the service - give it a try now! > > However, what exactly was happening before? In principle if the webapi...

@momchil-flex I unified the treatment a bit between the solvers. It looked like the non-FDTD solver status loop was just a subset of the FDTD solver status loop. The unified...

Thanks @tomflexcompute . Cost estimation and removing the URL are covered in this PR (and python-webapi PR): https://github.com/flexcompute/tidy3d/pull/1634 Progress bar is a nice suggestion, I can look into it. You...