Project

General

Profile

Bug #4441

reporting fails to output figure

Added by Oliver Soong about 10 years ago. Updated about 10 years ago.

Status:
Resolved
Priority:
Normal
Category:
reporting
Target version:
Start date:
10/06/2009
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
4441

Description

In the Bovine TB TPC workflow (tpc01-buffalo-tb.xml), I can't seem to get any figures to show in the reporting. The workflow executes properly and displays the figures in ImageJ, so they are created and a token is passed on the port. The example report consists of a trivial title and the port .tpc01-buffalo-tb.Average Rainfall Plot.Average Rainfall Plotter.graphicsFileName. After running the workflow, the Report Viewer is blank (beige background, not white), there is no CPU activity from Java, and there is only minor disk activity (not sure from what).

This is on XP-64. Other workflows of similar scope seem to function as expected.

History

#1 Updated by Oliver Soong about 10 years ago

This problem also occurs on linux.

#2 Updated by ben leinfelder about 10 years ago

is there anything on the console that indicates an error/exception with the FOP rendering?

#3 Updated by ben leinfelder about 10 years ago

what are the R package dependencies i need?
"sp"
"rgdal"
etc?

#4 Updated by ben leinfelder about 10 years ago

i'm finding that reporting classes do not seem to be invoked when running this workflow.
have to track it down further, but I'm not convinced it has anything to do with images per se.

#5 Updated by ben leinfelder about 10 years ago

Will this workflow ever run on OS X?

#6 Updated by ben leinfelder about 10 years ago

I removed the ProvenanceRecorder and ReportingListener entries from the MOML of the bovine workflow. Then I opened the workflow in the WRP suite, made sure reports were generated and then saved the workflow again (with the included ProvenanceRecorder and ReportingListeners added again).
I did notice that the old workflow had the ReportingListener before the ProvenanceRecorder and that I was seeing a null pointer exception when trying to get the PR in the RL initialization. So it may be that the order of these elements in the workflow XML actually matters quite a bit. I'm not sure if this order will be preserved or if it completely arbitrary. Would be nice if we could be certain that the PR will always be before the RL.

#7 Updated by Redmine Admin over 6 years ago

Original Bugzilla ID was 4441

Also available in: Atom PDF