Primordial IES vs ultra-modern IES

[laat0003]

Hi,

As a collector of fine works (read hoarder), a colleague of mine was running IES using an exe from 2018 without any issue. Using the current version of IES triggers an instruction file error (see below). Looks like the whitespace isn't being stripped. I'm curious as to why this might be the case. The newer version is noticeably faster and consequently preferred but unsure how best to avoid triggering this outcome.

Thanks in advance.

[jtwhite79]

What type of instruction if being used? If it is a strict fixed read with square brackets, then what you're seeing was the expected behavior based my interpretation of the instruction set. But I recently heard from @doherty1234 that trailing whitespace is acceptable in fixed read, so this Will be acceptable again in the next release.

If you aren't using fixed read instructions, then please post the instruction file and corresponding output file so I can have a look!

[laat0003]

Cheers for that. He is using fixed read which causes leading whitespace for some reads. More detail below.

I'll see if he can change to an alternative read.

[jtwhite79]

Ok, In this case the easy fix is to switch to "semi-fixed" by replacing the square brackets with round brackets...

[laat0003]

Cool. Thanks. We did try that but still had some issues with leading numbers getting dropped on some observations because the output files are painful. So we ended up going with whitespace delimiters instead and that seems to have solved it.