you are after an array aliases statement, which has examples floating about. you want something like L[1..3] aliases geom.d_r, geom.h_r, geom.d_r in this case. it's also possible willbe, willbethesame are in order, depending on what structure constraints you want to enforce on geom.
Ben On Sun, Dec 12, 2010 at 5:10 PM, John Pye <[email protected]> wrote: > Hi Ben > > I think I asked you something similar to this in the past, in relation > to 'block connections', but now I have a slightly different issue. > > Just now, I was working with a colleague on some modelling for a heat > transfer problem. We have a model that looks a bit like this: > > MODEL submodel(geom WILL_BE geometry_data); > > L[1..3] IS_A distance; > > L[1], geom.d_r ARE_THE_SAME; > L[2], geom.h_r ARE_THE_SAME; > L[3], L[1] ARE_THE_SAME; > > L_char IS_A distance; > > L_char = SUM[L[i] * .... | i IN [1..3]]; > > END submodel; > > However, the above code does not work, because it allegedly modifies the > 'geom' parameters in some disallowed way. As I recall, it is not > permitted to merge parameters of a model: that's what's at issue here, > right? > > Is there any way to allow us to link array elements to parameters in a > submodel, as specified above? OR is there a more elegant way of > achieving something comparable? > > The only thing I could think of was (a) to manually write L1, L2, L3 and > eliminate the array syntax or (b) to use '=' to create a local copy of > the variable, unmerged. > > Cheers > JP > > ------------------------------------------------------------------------------ Lotusphere 2011 Register now for Lotusphere 2011 and learn how to connect the dots, take your collaborative environment to the next level, and enter the era of Social Business. http://p.sf.net/sfu/lotusphere-d2d _______________________________________________ Ascend-sim-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ascend-sim-users
