bugs: Refs relevant to hardware capabilities, and further things to look at.
[libale.git] / bugs / issue-7631a924622738a4fe08bd25581ee1e42029b684.yaml
blobaa14ab80c0aea805591bce17f91906a60c43e3e3
1 --- !ditz.rubyforge.org,2008-03-06/issue 
2 title: Consider whether invariants and thresholding should be part of rendering, or part of image logic
3 desc: ""
4 type: :task
5 component: libale
6 release: 
7 reporter: David Hilvert <dhilvert@auricle.dyndns.org>
8 status: :unstarted
9 disposition: 
10 creation_time: 2009-02-18 16:10:03.414617 Z
11 references: []
13 id: 7631a924622738a4fe08bd25581ee1e42029b684
14 log_events: 
15 - - 2009-02-18 16:10:04.111466 Z
16   - David Hilvert <dhilvert@auricle.dyndns.org>
17   - created
18   - ""
19 - - 2009-02-19 14:02:03.318524 Z
20   - David Hilvert <dhilvert@auricle.dyndns.org>
21   - commented
22   - |-
23     Reviewing ALE code, there appears to be no obvious impediment in common use of
24     image_weighted_median, image_weighted_simple, or image_weighted_avg to prevent
25     invariant calculation code from being placed within renderer logic, leaving
26     image logic absent such code.  Thresholding code seems likely to prove
27     similarly unproblematic for inclusion within the renderer complex.
28 git_branch: