I'd like to ask you to consider, please, what you're hoping to do; and what you're hoping to get from posting your problem. I'd like to help you to think about this.

As Corion points out, the module you cite does not exist, at least not on CPAN. You might want to try searching CPAN for CSV-related modules. There are quite a few that will parse a CSV file into a reasonable Perlish structure. It's up to you to pick one you like.

Parsing the CSV file is one, separate issue; doing stuff with that data is another. It's kinda scary to see you speaking about both issues in one breath; they're unrelated. Suggest if you need help picking out a CSV module, ask for that; if you need help munging the data once it's in a Perlish structure, ask for that; if you need help with both issues, write two distinct nodes.

Next, let me talk about the way you talk about your problem set. It's not unusual; indeed, it's quite the common approach. It's not even un-engineer-like: We want to abstract away from details and generalize from specific cases. But in your attempt to present the general, abstract problem you make it difficult to see. We don't know exactly what you mean by some of your words, such as "beam" (at least I'm sure I don't). You might do much better by presenting actual sample data, e.g.:

my $in_A = [ [ 0, 1, 2, 3 ], [ 9, 8, 4, 1 ], ]; my $in_B = [ ... ]; my $out = [ .... ];

... then, at least on the first cut, your whole question boils down to: How do I get from in to out? You can use as many input variables as you need to define the problem; and you should show the exact output you would like to get.

It's not really useful for you to try to post your entire data set. As Corion says, a few lines is probably plenty. Looking at a large data set and cutting it down to a small example is a skill worth developing.

I'm tempted to give more advice but I won't. I'd like to hope what I've given already will be helpful... and I'd very much like to see you work on your question with these things in mind before much more is thrown at you. Many Monks will read your post and instantly think of extremely clever solutions... to other problems; and they will present them in great detail. I'd like to know what your problem is.

Feste: Misprison in the highest degree. Lady, cucullus non facit monachum. That's as much to say as, I wear not motley in my brain....

In reply to Re: parsing with Workflow::csv_File by Xiong
in thread parsing with Workflow::csv_File by devoted_to_Perl

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.