When you run the BioPharma Finder application, some temporary processing files are saved in your local computer.

If these files cause disk space issues, you can manually trigger data space optimization through the Help menu. This action can also be performed automatically by the application according to a predefined purging policy. In both instances, the temporary processing files are deleted to free up space.

The BioPharma Finder application provides warning messages or performs a forced purge action if the disk space reaches certain configured threshold levels; these levels are defined in the following table.

Threshold levels for forced purge actions in BioPharma Finder

Threshold Level



Disk space warning level percentage

The storage limit at which the application first warns you to start data space optimization from the Help menu.

< 25% of total space available

Force start purge level percentage

The storage limit at which a forced purge starts.

< 10% of total space available

Maximum purge limit percentage

The storage limit at which a forced purge stops.

= 40% of total space available

Minimum space used before starting purge percentage

The storage limit before which the application does not purge.

< 20% of total space is occupied by the BioPharma Finder files

If your computer is running low on disk space but the BioPharma Finder application is not the main reason for this issue, the application provides a warning message and closes. You must first free up space by deleting unnecessary files from other applications or by using tune-up options that are available on your local computer. After that cleanup is completed, you can start the application and perform data space optimization if needed.

The application does not provide a warning message before starting a forced purge. The purging begins in the background and deletes files from the local cache until the free space value is acceptable.

The application sorts and prioritizes BioPharma Finder files during data space optimization and forced purging based on the following parameters: last access time, usage count (how often is the file being used), reference count (how many experiments use the file), and file size.