= Description =

## Please read this page. Lines prefixed with ## such as this one are comments,
## you can remove them (except for those after the "Plan" section.)
## Please follow the instructions given in those comments and the text.
## After creating the bug page, please subscribe to it! We may have questions
## that only you can answer, and if you get email when your bug changes it'll
## be much faster to get it fixed since you can answer the questions!

Describe the bug...

== Steps to reproduce ==
## Describe the steps needed to reproduce the bug. If we can't reproduce it, we  probably can't fix it.
 1. do this...

== Example ==
##Add screenshot, magpar error message

##URL: 

##{{attachment:screenshot.png}}

== Details ==

## magpar output, magpar input files (as attachments)
## Please fill in the details here:

|| '''magpar version''' || original distribution or patched/modified version? ||
|| '''OS and version''' || e.g: RedHat EL 5, CentOS 5, Debian Linux 5.0 Lenny ||
|| '''Compiler name and version''' || e.g. GNU gcc 4.3.3, Intel icc 11 ||
|| '''Machine/hardware/CPU type''' || Intel Core2Duo, AMD Opteron 250 ||
|| '''Library versions''' || e.g. PETSc 2.3.3, Sundials 2.3.0 ||

## refer to/explain attached files (attach after completing this bug report):
## [[attachment:allopt.txt]]
## [[attachment:model.inp]]
## [[attachment:model.krn]]
## [[attachment:stdouterr.txt]]

== Workaround ==
## How to deal with the bug until it is fixed


= Discussion =


= Plan =
## This part is for magpar developers:

 * Priority: 
 * Assigned to:
 * Status: 

= Attachments =
<<AttachInfo>>
<<AttachList>>

----
## Category MagparBugConfirmed - if the bug has been confirmed by a 3rd party and bug report is complete
## Category MagparBugFixed - after the bug is fixed/a patch available
CategoryMagparBug