[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

# bug fixes

- To: femm@yahoogroups.com
- Subject: bug fixes
- From: David Meeker <dmeeker@foster-miller.com>
- Date: Mon, 10 Sep 2001 12:59:31 -0400
- Organization: Foster-Miller, Inc.
- References: <9nahkl+hise@eGroups.com>

For those of you who need fixes to the bugs reported over the past week or two, I've put a patch in the files area at http://groups.yahoo.com/group/femm/files/patch.ZIP Just unzip this file into your femm31\bin directory. It contains bug-fixed versions of femme, femmview, and a minor update to the manual that fixes some typos and includes some minor new scripting commands I added.

slindsay@atsautomation.com wrote:

> If I run this code in a scripting loop,
> the value passed into FEMM appears to
> get truncated to an integer value.

For some reason, I cast the modified values as integers in the implentation modifypointprop--this was a mistake that gives the truncation that you have noted. I have removed casting to integer so that point properties can now be correctly updated with noninteger values. Just to be thorough, I looked through the other modify property routines as well and didn't see any other instances of this bug. The fix is included in the patched version.

Alberto Perez wrote:

> Hello:

> I have a problem with femmview, I define a circuit in
> femme with a current that have a real part and a
> imaginary part, but when I use circuit properties with
> femview, in the window only a real part of current.
> Can it affect results? What am I doing incorrectly?

> Thank you

> Alberto Pérez

You aren't doing anything incorrectly--there was a bug in the program where it read in the current for each circuit property, so that it never read in the imaginary part of the current constraint defined for each circuit. This doesn't affect the field results (indeed, when you do a direct integration of the current in a circuit, you get the right value), but it would mess up the impedance results that are reported in the View|Circuit Props window of the postprocessor for circuits where the specified current has an imaginary component. The fix was to change totalamps_re in line 650 of femmviewdoc.cpp to totalamps_im, so that the imaginary part of the current gets read. This fix is included in the patched version.

Carl Kopin wrote:

> Robin,
> The postprocessor window hide outcome depends on the argument you use:
> - using the "-window_hide" argument will cause the window to appear for a split second;
> - using the "-windowhide" argument will cause a tiny application window
> with an "x" only to appear for a split second.

> I prefer consistency in commands/arguments naming convention: by using
> the underscore to separate words in commands/arguments no one has to
> guess where one word ends and the next begins.
> Carl

I've changed it so that both -window_hide and -windowhide do exactly the same thing. What should happen with the patched version is that an entry for femmview appears on the taskbar, but no window is opened for femmview. Try it and see what you think.

jim271@hotmail.com wrote:

> I have the version of FEMM dated Aug 21, '01.
> I can't seem to get the pause() command to work in the preprocessor.
> It gives an error message every time. Is there a trick to this? It
> sure would be handy for debugging.

Although you have found a work-around using the _ALERT command, I've added a pause() command to the preprocessor (it was a really easy thing to do). I've also added a function called messagebox, that works just like the _ALERT command (has the syntax: messagebox("message")) but pops up an information icon rather than a critical stop icon in the message box. This command has also been added to the documentation. Yes, you can use message_box interchangeably...

lkloesel@cello.qnet.com wrote:

> In order to get showdensityplot() to change to current density |J|, I
> had to use quotation marks for jmag.
> example:
>
> showdensityplot(1,0,0,0,"jmag")
>
> Then in order to get the correct magnitude; I had to multiply by the
> power of 12
>
> jmagnitude=50e+12
> showdensityplot(1,0,jmagnitude,0,"jmag")
>
> I suspect the C++ lines in luadoc.cpp, lua_showdensity :
>
> i f (btnState>3) {
> m_lb1*=1.e-6;
> m_ub1*=1.e-6;
> }
>
> may be the problem, but that's as far as I can go with what I know.

Thanks for catching this--the fix is just as you say. I have included a fix for this bug in the patch as well.

Anyhow, thanks for everyone to contributing these bug reports--it's a big help, and I really appreciate it.

Dave.

    begin:vcard
    n:Meeker;David
    tel;fax:781-890-3489
    tel;work:781-684-4070
    x-mozilla-html:TRUE
    url:http://members.aol.com/_ht_a/dcm3c
    org:Foster-Miller, Inc.;Electrical and Electronic Systems Group
    version:2.1
    email;internet:dmeeker@foster-miller.com
    title:Senior Engineer
    adr;quoted-printable:;;350 Second Avenue=0D=0A;Waltham;MA;02451-1196;USA
    fn:David Meeker, Ph.D.
    end:vcard

- References:
  - FEMM scripting bug?
    - From: slindsay@atsautomation.com

- Prev by Date: Re: [femm] Inductance - more confusion
- Next by Date: mutual inductance
- Previous by thread: FEMM scripting bug?
- Next by thread: mutual inductance
- Index(es):
  - Date
  - Thread