You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @mostaphaRoudsari, Do you have any idea why the stdin is invoked midway in Andy's rfluxmtx example ? rfluxmtx -n 8 -I+ -ab 12 -ad 10000 -lw 1e-4 < points.txt - skies/sky.rad materials/testroom.mat objects/testroom.rad > DC.dmx
I am trying to figure out ways to add the control parameters for sender and receiver and found it odd that the stdin is employed earlier in the process.
PS: I think it's still early days to escalate this question to the mailing list as I think I might understand the working more if I figure out a solution here than getting a readymade answer elsewhere.
The text was updated successfully, but these errors were encountered:
While staying on the issue, how are we creating points files (rays). I know that you have an implementation inside GH/HB which does it. Will be relying on the gui of GH/Dynamo to generate pts files ?
The part about ground in the first half of the string above is unlikely to change. The second part, ie. the sky portion will change based on the kind of sky that we choose. Andy's example uses Tregenza sky and there for h=r1, however we could use further subdivisions and change the sky conifgurations.
To sum up, I think we could probably implement a @staticmethod type thing for generating skies.. the function could be something like
I am still testing out a few things on my side. I will keep this discussion going ....
To add to this ...
Linking (annual or point-in-time) Sky Radiation Data to First Phase
I think we might not have much leeway in setting the h= value for the sky as well as this would most likely get decided by the -m property of Gendaymtx and Genskyvec. From the sky definition above, the ground patch is created in Rfluxmtx by #@rfluxmtx h=u u=Y which links to the the 0 in (0 + 145) or (0 +2305) sky patches. #@rfluxmtx h=r1 u=Y will decide whether the patches are 145 or 2305.
Hi @mostaphaRoudsari, Do you have any idea why the stdin is invoked midway in Andy's rfluxmtx example ?
rfluxmtx -n 8 -I+ -ab 12 -ad 10000 -lw 1e-4 < points.txt - skies/sky.rad materials/testroom.mat objects/testroom.rad > DC.dmx
instead of
rfluxmtx -n 8 -I+ -ab 12 -ad 10000 -lw 1e-4 - skies/sky.rad materials/testroom.mat objects/testroom.rad < points.txt > DC.dmx
I am trying to figure out ways to add the control parameters for sender and receiver and found it odd that the stdin is employed earlier in the process.
PS: I think it's still early days to escalate this question to the mailing list as I think I might understand the working more if I figure out a solution here than getting a readymade answer elsewhere.
The text was updated successfully, but these errors were encountered: