facebookresearch / facebookresearch/fairo

Understand, document and clean up memory

Open
#351 2 comments 0 reactions 1 assignee Assigned to @kavyasrinet View on GitHub
refactor
Dominant language
Jupyter Notebook
Stars
929
Forks
123
PR merge metrics
No merged PRs in 30d

Description

## Type of Issue

Select the type of issue:
- [ ] Bug report (to report a bug)
- [ ] Feature request (to request an additional feature)
- [x] Tracker (I am just using this as a tracker)
- [ ] Refactor request
- [ ] Documentation Ask

## Checklist

Use this checklist if you are using this issue as a tracker:

- [ ] How to use basic_search, more examples of keywords
- [ ] Clean up in for example mc_memory_nodes -> explain attributes of tables in a doc perhaps. Things like : NODE_TYPE,
- [ ] Consistent naming for things like : ref_type
- [ ] Mention in the doc that BlockObjects and InstSegNodes are under the same table ReferenceObjects
- [ ] Should we get rid of BlockObjects for MC?
- [ ] Right now we have basic_search as well as get_filters and get_filters_from_lf used throughout - we should stick with one consistent way of querying memory for a filters subdict for our use cases.
- [ ] Document what possible ways and APIs there are to read / write / query memory
- [ ]
- [ ]
- [ ] Task 2
- [ ] Task 3 ...

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.