View brass snapshot
This article describes the 'View brass snapshot' feature.
It’s important to understand that cases change every time you shoot it and every time you work on it. For example, brass properties will change every time a case is run through a full length sizing die. It may or may not impact it’s performance and it will certainly effect its life span. Maybe some of the cases are starting to split and you’d like to know (a) what batch it is, to restock or (b) how many times they’ve been fired to roughly know the lifespan of this specific brand for future reference. This is normal, however we need to keep track of this data.
With that in mind, the batch of brass you have documented may no longer be an accurate representation of that batch. For example, the ‘times fired’ property will need to be updated, maybe case length, trim, etc. At the same time this batch of brass has to remain in its current form to be an accurate representation of the load recipe. This means that case data needs to be kept the same and updated at the same time.
Reloading Studio solves this challange by providing two features to brass management features.
Option 1: brass snapshot.
This is automated feature and does not require user interaction.
In the cartridge build screen you will see a ‘brass snapshot’ button.
This will open a window with a copy of your case data used for this specific batch.
A copy of this data has been made behind the scenes and assigned to a specific batch of cartridges. This data will not change even when you update the original case data in the component screen. This is done intentionally to maintain accurate records of your exact cartridge specification for every batch.
Don’t do this unless you really know what you are doing and why you are doing it.
Please note that the only time brass snapshot values will change is when you manually and explicitly change brass selection in an existing batch.
There may be a reason you need to do this, perhaps correcting an error and the application does not prevent you from doing this for that exact reason. However, this should not happen in 99% of all use cases.
Option 2: cloning, archiving and creating a new batch of brass.
This option is not mutually exclusive to ‘option 1’, i.e. a ‘brass snapshot’ will always be made, regardless of other actions. This specific option is entirely up to you and your preference to data management.
In the above screenshot you will notice that there are two similar batches of brass, in fact they are identical with one exception - batch name. Where batch name if prefixed with '-Clone-20181206221745690' to make a unique new batch.
- Batch 'PPU-44-001': original, archived.
- Batch 'PPU-44-001-Clone-20181206221745690': new, cloned.
Once a batch of brass was used, a user can decide to (a) clone this batch into a new batch, to continue working on it. For example, update ‘times fire’. And (b) archive the original batch. This way you have a copy of original data, locked from editing. And a new batch that you can keep maintaining, cloning and archiving as you use that batch of brass. Using this process of brass management is entirely up to you and just a matter of preference.