I think that representative data, along with a description of the result and purpose of the code would work. (Or, if not, that should be enough for us to ask intelligent questions.)
-- Raul On Fri, Nov 18, 2011 at 12:45 PM, Daniel Lyons <[email protected]>wrote: > Raul, > > On Fri, Nov 18, 2011 at 12:02:47PM -0500, Raul Miller wrote: > > I have been trying to think up a useful response here, but I just do not > > know enough from this description to make good choices. > > Well, I appreciate the attempt. :) I don't know enough to know what > information would be necessary to make good choices. > > > Typically, I build up the expressions that I find useful first and then > > come up with names for them later. Sometimes I re-arrange things that > work > > so that they are easier for me to describe.\ > > Fair enough. I expect that with time, one develops an intuition for > where to begin. > > > And, yes, it's easy to transform between different array representations. > > But there's a lot of representations and a lot of transformations > between > > them and a lot of ways of using each representation, so it's hard to give > > specific advice. (As a general rule though, I try to arrange things so > > that they are simple.) > > > > And, yes, putting each "column" in its own variable can be a good > approach. > > I'll continue with this approach and see what I come up with. > > Thanks again, > > -- > Daniel Lyons > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm > ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
