Skip to content

Reltrans: what to keep #5

@bjricketts

Description

@bjricketts

I need to keep track of what is totally necessary in the code for the imaging. I somewhat want to figure out if it's possible to produce time lags per disk patch - if so, this would be a really nice result for a paper, but definitely is very ambitious. I think that it would require considerable re-formatting to retain the imaging as well as the cross-spectrum. Currently, the code essentially makes the cross-spectrum for a single point source (which assumes all the signal is mixed up). Calculating the cross-spectrum per pixel might be quite difficult/pointless if the emission is mostly lagging the central accretion region (corona to disk + reflection processing).

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request
No fields configured for Feature.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions