Generating in sections

[bowmatty]

Hello,

Is it possible for me to generate in sections, i want to create 1000 and then run again and create another 1000 and start from the continuing number. Example, generate 1-1000, and then a separate 1001-2000

Thank you :)

[bolshoytoster]

@bowmatty you can use my fork and just change growEditionSizeTo to whatever you want the full collection to be, i.e. add 1000 to it each time.

[bowmatty]

And will that just continue on..i.e 1000 then next gen will be 1001-2000 etc?

Get Outlook for iOShttps://aka.ms/o0ukef

---

From: bolshoytoster @.> Sent: Wednesday, August 17, 2022 7:12:33 PM To: HashLips/hashlips_art_engine @.> Cc: bowmatty @.>; Mention @.> Subject: Re: [HashLips/hashlips_art_engine] Generating in sections (Issue #1364)

@bowmattyhttps://github.com/bowmatty you can use my forkhttps://github.com/bolshoytoster/hashlips_art_engine and just change growEditionSizeTo to whatever you want the full collection to be, i.e. add 1000 to it each time.

— Reply to this email directly, view it on GitHubhttps://github.com/HashLips/hashlips_art_engine/issues/1364#issuecomment-1217725728, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A2SA3LZE7SLWQDW76KAAZGLVZSUIDANCNFSM56YIE7GA. You are receiving this because you were mentioned.Message ID: @.***>

[bolshoytoster]

@bowmatty yes.

[bowmatty]

Thanks mate, How do i use your fork? sorry noob here

[bolshoytoster]

@bowmatty the same way you use the main hashlips, you can get a zip here.

[bowmatty]

Thanks mate

If i add 1000 to it and then generate, will the next gen continue from 1001-2000? My current fork just deletes and recreate from 1 each time, not continuous if you know what i mean.

[bolshoytoster]

@bowmatty yes.

[bowmatty]

Do you have a screenshot of how the "growEditionSizeTo" should look when generating each 1000? so i can get an idea.

Thanks again

[bolshoytoster]

@bolshoytoster you just set it to whatever you want the collection size to be each time, i.e. 1000, then 2000, then 3000

[bowmatty]

Ok great, ill give that ago. Thanks again

[bowmatty]

I got multiple errors when running this fork..

PS C:\Users\Matt\Downloads\hashlips_art_engine-main> npm run generate npm WARN config global --global, --local are deprecated. Use --location=global instead. npm ERR! code ENOENT npm ERR! syscall open npm ERR! path C:\Users\Matt\Downloads\hashlips_art_engine-main/package.json npm ERR! errno -4058 npm ERR! enoent ENOENT: no such file or directory, open 'C:\Users\Matt\Downloads\hashlips_art_engine-main\package.json' npm ERR! enoent This is related to npm not being able to find a file. npm ERR! enoent

npm ERR! A complete log of this run can be found in: npm ERR! C:\Users\Matt\AppData\Local\npm-cache_logs\2022-08-18T07_51_15_085Z-debug-0.log

[bolshoytoster]

@bowmatty you're in the wrong folder. Run Get-ChildItem -Directory to get the name, then run cd + the name to change into it.

[bowmatty]

Yep i ran the Get-ChildItem -Directory, which name do i need?

[bolshoytoster]

@bowmatty the one you get from running Get-ChildItem -Directory.

[LaughingElephant]

Love this fork. Any suggestions to be able to update the base URI without updating the name? Intent of use is to have different names within the same collection - but need to be able to update the base URI without it also changing the names.

[bolshoytoster]

@LaughingElephant just add a // to the start of line ~43 in utils/update_info.js: https://github.com/bolshoytoster/hashlips_art_engine/blob/708bf21426b11f3592697bde959caadcf11a722a/utils/update_info.js#L43

[LaughingElephant]

@bolshoytoster Easy enough lol, that worked thanks man.

If you figure out how to set each 'growEditionSize' container to its own name in the metadata hit me up. Would be nice to shuffle the different names around.

[elpigeontest]

Hi @bolshoytoster your fork could work for this scenario?

I'm making a collection that use two different base drawings. The traits are the "same", but I can't use the same drawing of the traits because the bases have different sizes. Is there any way for me to generate the collection with some conditionals? Like, If base layer is X, then use these traits, or if base layer is Y then use these other traits?

[bolshoytoster]

@elpigeontest you could have two different layersConfigurations, one with traits x and one with y. My fork doesn't support having different image sizes though.

[elpigeontest]

@elpigeontest you could have two different layersConfigurations, one with traits x and one with y. My fork doesn't support having different image sizes though.

Thank you! The problem is in this way the bases are not shuffle. It made the first half one base and the other half other base.Ex: The first 100 is one base and from 101 to 200 is the other base. Is there a way to shuffle this?

[bolshoytoster]

@elpigeontest yes, in src/config.js you can set shuffleLayerConfigurations to true.

[elpigeontest]

@elpigeontest yes, in src/config.js you can set shuffleLayerConfigurations to true.

Thanks! Works fine!