![]() According to §2 (6) and (7) LBO the building has 3 full floors. The main building is 4-storey and extends from the first floor over 1st and 2nd floor to the partly developed, partly not developed attic. ![]() Classification as an lodging facility does not apply. Under building law, it is a special building with an accommodation use. The new building is planned as a free-standing four-story building without a basement. Planning documents are available for this. The new building will be a four-story accommodation building with no basement and 81 hotel units, almost identical in construction to the new accommodation building (Building 24) already completed opposite. In the new building, the identified shortage of accommodation will be compensated with the "hotel standard". Instead, it will be dismantled and replaced by a new building. The existing accommodation building will not be refurbished for economic reasons. It is located in the northern part of the property. Here you have a partial answer to the following question, as the tags of copied entities will be contained in your return variable.Technical planning according to HOAI Part 4, Section 2, § 55 Technical equipment plant group 1-3, work phase 5-9 (commissioning in stages)īuilding 14, which is to be converted, is located on the Oberst-Herrmann-Kaserne (former Rettberg-Kaserne) property in Eutin. Therefore you might not want to use the same kind of variable name, since in order to get the tag you'll have to use s2 instead of simply s2. Keep in mind that copy will return a variable of the same kind (list of tuples), i.e. ![]() NB: when copying only one entity, I think either the inner parentheses or the brackets are superfluous, and otherwise you have to provide a list of tuples of the form. It's the same thing with transformations such as rotate, symmetrize etc. Regarding your error with copy, you have to specify the dimension of the entity to be copied, and not just the tag (check the documentation, which refers to dimTag). But I found this discussion in the Gmsh mailing list archive, which may be helpful. It's probably too late, but you never know. Is there a better way to do this than what I am trying to do with the dilation? In the end, what I want to accomplish is the following: draw a spline through a list of points, create a scaled copy of this spline, draw lines between the start and end points, and create a plane surface bounded by the two splines and lines. Assuming I was able to accomplish the same with the API, how do I then refer to the three new points that the scaled spline goes through, for example, if I wanted to draw a line between the start point of the original spline and that of the scaled spline? Am I missing something here? I have tried, for example, to call () before attempting to call copy(), but this had no effect.įinally, when I use the dilate transformation in the Gmsh GUI using Modules - Geometry - Elementary entities - Transform - Scale, checking the Apply scaling on copy option in the dialog, on the example spline from above, I indeed get a scaled version of the curve as expected, including the three points. The error code, 1, seems to indicate that the tag of the original spline ( s1) cannot be found when copy() is called. I get ValueError: ('gmshModelGeoCopy returned non-zero error code: ', 1). Secondly, when I try to make a copy of a spline like in this example: p1 = (-1, 0.5, 0, 0.1) But is there any way to get the full Gmsh script out of the API? I assume this has something to do with the _unrolled part. This extension does the trick mostly, but it seems that any meshing operations (such as marking curves as transfinite) or transformations (such as dilate) are not written to the output file when using gmsh.write('test.geo_unrolled'). geo_unrolled extension is supported for the gmsh.write() function, but not just. ![]() I looked through the source code of the Gmsh API and found that the. There are a few issues I am running into:įirst of all, I would like to be able to write Gmsh script files (. I am trying to write a script that will automatically mesh geometries for CFD analysis using the Gmsh Python API.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |