another comma separated txt file. I know how to import points (function Import coordinates), but I dont know how to connect them by lines if the only information I have about lines is the list of point numbers which should be connected. The txt file with point coordinates looks like:
-18,-36,-1000-18,-34,-19.728-18,-32,-17.603-18,-30,-15.372-18,-28,-13.121
...
And the txt file with line connections looks like:
1,22,33,44,55,6
...
Which means that I want to connect point 1 with point 2, point 2 with point 3 etc...
Both txt files are attached, thank you for the answer...…
reated.
The Appdata Folder is 'on' a windows junction. I run 3 diffrent PC that way and never had an Autosave issue with grasshopper.
Any ideas anybody?
Windows 8.1
Rhino 5SR11
Grasshopper 0.9 Rev 14…
urves in the curve parameter and used Sort list component to rearrange the curves in a new list according to their lengths making the shortest curve item '0' and second shortest curve item '1' etc.
I can imagine there are many approaches to this problem depending on additional factors. Hope that helps, sorry can't make an image.…
picture:
... and on a PC without anything attached to the serial port. When you open the port, start the read component and its timer, do you then get a stream of <empty> values in the log output? (hmmm... I suppose that's only reasonable - but still, you are also seeing this?)
I suppose that, because of the mutually exclusive behavior of both the spider and grasshopper (i.e. only one at a time can access the COM port), we can deduce that we are listening on the correct port.
Am I listening on the correct pin (if such a notion makes sense at all)? If I look back to the spider software, I see that 9 channels are listed and that it's only the measured value on channel 0 that changes when I press the load cell. Channels 1, 2, and 3 report OVERFLOW; 4, 5, 6, and 7 are pretty much constant at 0.000 to 0.005 V; and channel 8 says FFFF. I do not know how things like that work so I do not know if they reflect reading from the 9 pins on the D-sub 9 connector.
As for your BTW question: no, I don't need to record all of the sensor values. I suppose that the Out value on the Read component will always reflect the most current value and that's all that I need to get on with life. In the end, the idea is that we have 4 load cells in the 4 corners of a plate onto which a vertical pipe is fixed. Loads are then put on the top end of the pipe and we'll have to visualize both direction and magnitude of the bending moment that is calculated from the compression - tension readings from the load cells... We've done this on a scaled model and streamed load cell information into MatLab. Now we'll have to use a different datalogger and I was hoping to be able to do the post processing in Rhino.
wim…
=mostaphaRoudsari&fork=hydra_1&id=Remove_Ladybug_and_Honeybee&slide=0&scale=1&offset=0,0
Restart my pc
Reinstall OpenStudio in C:\ProgramFiles
Reinstal Ladybug and Honeybee
still same error message
…
is on the right on my screen while my real hand is already gone to the left.
Do you have a 0 latency answer on your laptop? It may come from my pc.
Thanks again Andy.
…
are not copy with the number that belong to each other, like:
untrimmed surface0 should be 41 pieces
untrimmed surface1 should be 28 pieces
untrimmed surface1 should be 21 pieces
it result like this
exclude the 1st and 2nd pieces,the others all is untrimmed surface 1
and the attachments is the result that i want, I done it one by one.…
combination is nearly 0 (of course with 1 try). You have about 100 (?) dimensions... its just impossible to do it well. Even with billions of random genotypes for 1st generation.
Its like 1:googol (10^100) to succeed. If youll try and run it on your pc, youll probably consume all the energy in universe, and it will take longer time than our universe will exist.
Sorry :(
EDIT : As David wrote in his post - every added dimension results with almost half of "success ratio". So as with one slider you have e.g. 1:2 ratio of success, with 100 sliders you have :
1:633825300114114700748351602688 (2^99)
To somebody more familiar with math -> correct me if Iam wrong :)…
which doesn't exist in the actual problem spec. If galapagos is allowed to change the column position in all possible directions, it is less likely to get stuck in some local optimum.
Let's assume that (all other things being equal) column 20 would yield the best possible answer. The current state of the system though is at column 26, which is pretty good too, just not as good. Galapagos is more likely to 'mutate' the state a little bit instead of a lot, so it'll explore the columns near 26. However 20 isn't near 26 at all, only 25 and 27 are nearby, and maybe 24 and 28. But they'll all worse answers, so after sampling in those directions GP will abandon that as fruitless.
If however you specify the columns using two variables, then the columns near 26 are 20, 25, 27 and 32. That's a far richer space to explore which much better approximates the real problem.…