Ticket #273 (new defect)

Opened 3 years ago

Last modified 2 years ago

Palmer Drought Index is broken

Reported by: mshopsin Owned by: mchandler
Priority: blocker Milestone: EdGCM SomeDay
Component: GCM Version: Model 1.0.8
Keywords: Cc:
OS:

Description

The Palmer Drought Index has been broken in model II since we started with it. Jeff found that the problem was that TG was not set to TG1 in a critical spot. Fixing this should produce an approximation of the Palmer Drought Index according to David.

Change History

Changed 3 years ago by mankoff

Related to Length Of Growing Season #295

Changed 3 years ago by mankoff

Not just related to #295... These variables are identical. Diff results in 0.

Changed 3 years ago by mshopsin

  • status changed from new to assigned

Changed 3 years ago by mchandler

  • priority changed from normal to highest
  • severity changed from normal to blocker

Changed 2 years ago by mshopsin

  • milestone changed from EdGCM 3.0 to EdGCM 3.1

Changed 2 years ago by mshopsin

  • version changed from Model 1.0.7 to Model 1.0.8

Changed 2 years ago by mankoff

deleted spam.

Not a fix, but temporary work-around. It looks like in most cases all these spam entries are in some aisan language. As a result following SQL allows you to remove them easily 

delete from ticket_change where lower( author ) = upper( author );

http://projects.edgewall.com/trac/ticket/454

Changed 2 years ago by mshopsin

The Palmer Drought Index = Length of the Growing Season in the 1.0.7 version of the model. This isn't the right behavior, but David brought up problems with the diagnostic overall in Model II anyway.

Changed 2 years ago by mankoff

  • owner changed from mshopsin to mchandler
  • status changed from assigned to new

Actually, Palmer is not equal to LOGS in the model. Palmer is 0 in model outputs and only equals LOGS sometime after postprocessing (during Sum, Pd, or netCDF phase).

Suggested solution: Remove Palmer from netCDF so users do not see it. Users who see it in PRT files will see zero.

Note: See TracTickets for help on using tickets.