Uploaded image for project: 'IGB'
  1. IGB
  2. IGBF-3229

Complete gene description transfer

    Details

    • Type: Task
    • Status: Closed (View Workflow)
    • Priority: Blocker
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
      None

      Description

      Follow up on IGBF-3145 (linked):

      • Modify the output file format to not wrap any of the fields with quotation marks.
      • Modify the code chunk to no longer print out an entire data frame to the final knitted document
      • Ensure that the file can "knit" without error
      • Create output file in a subdirectory named "output" or whatever.
      • Add knitted output (e.g., .html file, but nothing else) to repository, same location as corresponding .Rmd file.
      • Ensure that IGB can open the file (investigate command-line options for IGB to speed up development and automate testing)

        Attachments

          Issue Links

            Activity

            Hide
            ann.loraine Ann Loraine added a comment - - edited

            Mapping file contains what look like redundancies and inconsistencies.
            Modifying the Markdown to investigate.

            Show
            ann.loraine Ann Loraine added a comment - - edited Mapping file contains what look like redundancies and inconsistencies. Modifying the Markdown to investigate.
            Hide
            ann.loraine Ann Loraine added a comment -

            Opened the new BED-detail file in IGB and found a problem.

            One of the genes Solyc01G001683 has multiple gene models, only two of which got a description and all the rest still are "NA". Investigating.

            Show
            ann.loraine Ann Loraine added a comment - Opened the new BED-detail file in IGB and found a problem. One of the genes Solyc01G001683 has multiple gene models, only two of which got a description and all the rest still are "NA". Investigating.
            Hide
            ann.loraine Ann Loraine added a comment -

            Fixed it. Was using a conventional assignment operator inside a function that was getting used in an "sapply" call. Changed it to "<<-" to ensure that the assignment would affect the enclosing frame and therefore persist after the function returned.

            Viewed the file in IGB and it seemed OK. Did not check the functional assignments however.

            Show
            ann.loraine Ann Loraine added a comment - Fixed it. Was using a conventional assignment operator inside a function that was getting used in an "sapply" call. Changed it to "<<-" to ensure that the assignment would affect the enclosing frame and therefore persist after the function returned. Viewed the file in IGB and it seemed OK. Did not check the functional assignments however.

              People

              • Assignee:
                ann.loraine Ann Loraine
                Reporter:
                ann.loraine Ann Loraine
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: