<commit_before>Samples Guidelines
===

Scale: at the scale they were produced
* Note that the default box is 100 x 100 x 100
* If you model is to be embedded with other models then it should display well in that box
* Supply guidance on what scale - other than 1:1 you would like the viewer to use

Origin
* At the bottom lower left corner of the project is nice
	* Especially if the model is an 
* At the bottom center of the project is nice

Rotation
* use the model's grid
* Supply guidance if not North/Siuth


## Copyrights
* For project design
* For project model


## License

* Creative Commonns for designs preferred

* MIT License for code preferred

## Description

### Built to what codes and regs

### Provenance



## BIM Considerations

### Link to ontology or categorization schema

### links to spec

### Links to dates

### Links to codes



## Other preferences

### like series of models that have a theme
	* five is a nice number

### like university class projects
<commit_msg>samples guidelines<commit_after>Samples Guidelines
===

The following are guidelines for producing sample files to use and enjoy wirthe the vA3C Viewer

## Data formats

Generally, sample files should follow that latest Three.js JSON format as published on the [Three.js Wiki]( https://github.com/mrdoob/three.js/wiki )

Samples files should be tested using the [Three.js Editor]( http://mrdoob.github.io/three.js/editor/ ).

If the sample loads and displays correctly in the Three.js Editor and the vA3C viewer then it's good to go.

## Model Parameters

Scale: at the scale they were produced  

* Note that the default box is 100 x 100 x 100
* If you model is to be embedded with other models then it should display well in that box
* Supply guidance on what scale - other than 1:1 you would like the viewer to use

Origin

* At the bottom lower left corner of the project is nice
	* Especially if the model is to b inserted into another model
* At the bottom center of the project is nice

Rotation

* Use the model's grid
* Supply guidance if not North/Siuth


## Copyrights
* For project design: Name and contact information for the architect or designer. 
* For project models: Name and contactac informaton for the modeler.

## License

* If not out of copyright, Creative Commons licence preferred

* MIT License for code preferred

## Description

A paragraph or two decsribing the special aspects or principles of the project in a text file would be nice

* Built to what codes and regs
* Provenance / references to precedants
* Where published

## BIM Considerations

### Link to ontology or categorization schema

### links to spec

### Links to dates

### Links to codes



## Other preferences

### like series of models that have a theme
	* five is a nice number

### like university class projects

{'fraction_non_alphanumeric': 0.05543710021321962, 'fraction_numerical': 0.008528784648187633, 'mean_word_length': 3.8956521739130436, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 1, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '7428841', 'n_tokens_mistral': 770, 'n_tokens_neox': 715, 'n_words': 422}