Try making a child model. You open this child model for each tile, therefore reading it one by one and not all at the same time.

@bakkermans Thanks for the reply so would this involve using something like the WorkspaceRunner transformer?

That's right. You make the location of every ascii grid file as an attribute in the parent model. Next, you call the child model (actual processing) with a WorkspaceRunner. For each feature in the parent model (i.e. a location), the child model will run once.

In addition to what @bakkermans is mentioning: Use the "Directory and File Path" Reader to loop through a directory and use the attribute windows_path to fire up the WorkSpaceRunner for each file you have in your directory.

That will allow you to use this workspace each time you have new files in your directory.

@bakkermans so is that any different than running in batch mode (Run > Batch Deploy)

The big difference is that WorkspaceRunner allows several jobs to run simultaneously, whereas batch deploy won't. I used to be a huge fan of Batch Deploy, but I never use it now. WorkspaceRunner is more efficient and more predictable.

The other big advantage to the workspace runner scenario is you have complete control over your parameters. The batch deploy can get very interesting when your have multiple readers.

@erik_jan Thanks for your reply. so i assume you mean setting up a reader (using the "open advanced browser" option selecting a folder + sub folders)

From here how do you expose the windows_path attribute?

Hi @jamiefinney. If your C;\\temp would contain the ascii files this would be the settings for the reader. The windows_path attribute will be exposed automatically.

One more screenshot:

@erik_jan Awesome thanks just trying that now. Looks like it will process my data much quicker now.