Frequently asked questions about Atlas maps.
Map creation latency once Nomic has received your embeddings.
|Number of datums/embeddings||Map availability latency (s)|
|10,001 - 99,999||10-40|
|100,000 - 499,999||40-180|
|500,000 - 999,999||180-600|
|1,000,000 - 9,999,999||600+|
Who can see my maps?
When you create a map, you can toggle it as private or public. Private maps are only accessible by authenticated individuals in your Nomic organization. Public maps are accessible by anyone with a link.
How do I login from the client?
You can login to your Atlas account from the python client by getting an API key. If you are logged into the Atlas
dashboard in your web browser you can find it here.
Either login in a command shell by running
nomic login or in Python file with:
Making maps under an organization
If you are added to a Nomic organization by someone (such as your employer), you can create projects under them
by specifying an
organization_name in the
map_embedding method of the AtlasClient. By default, projects are
made under your own account.
Working with Dates and Timestamps
Atlas will consider metadata as timestamps when they are passed as Python
datetime objects. Under the hood,
these are converted into timestamps compatible with the Apache Arrow standard. Remember, you can directly pass
through pandas Dataframe objects and Arrow tables to the
How do I make maps of a dataset I have already uploaded?
You need to make a new index on the project you have uploaded your data to. See How does Atlas work? for details.
Nomic utilizes the
loguru module for logging. We recognize that logging can sometimes be annoying.
You can disable or change the logging level by including the following snippet at the top of any script.