Search the Community
Showing results for tags 'feature'.
The search index is currently processing. Current results may not be complete.
Found 4 results
Hi, Please find attached a feature definition that you can use for exporting blades into the geomturbo file format. Note that this export will be included in one of the next CAESES releases (menu > feature definitions > tools). If you need it right now: Just put the definition into the feature user directory (e.g. C:\Users\name\AppData\Roaming\friendship\features) to directly access it through the menu in CAESES. Cheers Joerg PS: Check also this related post for importing geomturbo files, as well as our company blog post about this topic. GeomTurboExport.fdf
Hi, if you want to read data from text or csv files it's fairly simple to do it in a feature definition. We use a simple file like this: To start we create a new feature definition: In the "create function" tab, we can use the code templates to create a basic control structure: The variable "FilePath" is not defined and has to be supplied with an argument. In this case I want the object "file" as an argument. So I comment the first line from the feature and create an new argument: The feature code looks like this: You can see that a string is create for each line of the file. So now we have to split this string in order to access the double values. Therefor I use the split command, which has the output of an objectlist. Then I create a point, which accesses each value of that object list: Now we have to store the points for each line inside an extra objectlist.Therefor we create a new list and add the point: Finally we create fore example an bsplinecurve, with the new list of points. Additionally encapsulated the while loop into a persistent section in order to visualize the points for each loop. Otherwise we would just see the last point. Now we create the feature from the feature definition: We set the path to the reference file: This nice dialog only appeared, because we didn't allow expressions for the argument inside the feature definition: The final curve: I hope this helps you to create you own custom file reader. best regards Carsten readTextFile.fdb data.zip
Wow, has it been that long since my last entry? Well, I have a very short one with a big attachment. I always wanted to write something about "best practices" for Feature programming. That "something" became larger and larger and it became pretty clear that it's too large for a "regular" blog post. That's why I decided to create a PDF file, instead. In the end it turns out to be a 37 page booklet instead of an article. I compiled some techniques that I consider to be the most effective for creating Feature definitions with good performance. So, please take a look at "Effective FPL" and let me know what you think about it in the comments. Merry Christmas and a good start into 2016!